Well, I noticed this by accident while trying to use dash for the rc.d scripts. I messed up and forgot to link it to /bin, and as such, the system failed to boot properly and would not respond. I rebooted (forcefully), but this messed up the filesystem. I booted the sw64 install DVD and tried to mount it, and it would not mount.
I tried to run fsck on it, but it said that fsck.jfs in NOT available. Eventually I booted my old slamd64 12.1 DVD and it had fsck.jfs. Any reason why this rather useful program was removed ? Or is it a bug, or is my DVD messed up? I guess I should just keep around another live CD, I do keep knoppix, but it boots so slow and I don't understand it at all, it's so hard to do anything with it.
My computer got hung up restarting after an update yesterday so I switched it off and back on, which led to the error message "No init found. Try passing init= bootrag", looking that up I found a thread that recommended running fsck to fix the errors.
I first went to disk utility and did the check filesystem and repair button but that just had a pop-up that said "File system is NOT clean." So I went and tried fsck on the drive which gave me the error message "fsck.ext4: Device or resource busy while trying to open /dev/sda1 Filesystem mounted or opened exclusively by another program?"
Figuring this may have been caused by the disk utility I restarted and tried fsck again without opening any other program, and I still get the same error message. What is causing this? Swap? What can I do to get fsck running to fix the original problem?
loading /usr/bin/teclafsck failed. please repair manually and reboot. the root file system is currently mounted read-only. to remount it read-write do:bash# mount -n -0 remount,rw /attention: only control-d will reboot the system in this maintence mode shutdown or reboot will not work.
I have a server that said a volume was dirty and to check it at reboot, so someone did a shutdown -rF now. Only problem is the other volumes are HUGE and it will take forever, which I cant have happen. The volume with the trouble is non-critical so I could take it offline and check it that way if i can get this to boot quickly. How can I do that if its going to auto check every volume on reboot now?
Today I did an update on my Debian 6.0.0 installation, which included a kernel update. I also did an Nvidia driver update, afterward. All well, until upon a third boot up an fsck check was forced (34 mounts). Some odd behavior ensued. At about 19% it exited the check, printed what appeared to be a load of inode numbers with error messages, and "froze" with the caps lock and num lock lights on the keyboard flashing.I did a couple of grub recovery modes, each which advanced a little further, and all is well again. However, it concerned me. Where in var/log do I find the file of that particular fsck activity?
RHEL 5.4. I'm facing the following error after rebooting the server: /dev/VolGroup01/u04: UNEXPECTED INCONSISTENCY Run fsck Manually" *** An error occurred during the file system check. *** Dropping you to a shell: the system wil reboot *** when you leave the shell. give the root password for maintenance:
-Previously I performed a lvreduce command on a LV, after the lvreduce, I reboot the server. -After login as root I run: e2fsck -f /dev/VolGroup01/u04
But, it shows: The filesystem size (according to the superblock) is 5218304 blocks The physical size of the device is 1310720 blocks ... either the superblock or the partition table is likely to be corrupt abort<y>? no pass 1: cheking inodes, blocks, and sizes error reading block 1310722 (invalid argument) while doing inode scan inore error <y>? y
-Additionally, trying to lvdisplay, it shows: Locking type -1 initialization failed I have no important data on that LV, but I can not boot the server properly.
I want the filesystem of my external drive to be checked periodically after a numer of mounts. I put 2 in the sixth colums of fstab for this partition
Code: /dev/sdb1/mnt/hdext3rw,dev,sync,user,noauto,exec,suid02 and I use the tune2fs to set the maximum mount count to 32. Code: tune2fs -c 32 /dev/sdb
now the mount count is 34 and the date of the last check is not recent, so apparently the auto fsck has not been performed. Probably because this partition is not mounted at start-up but I usually mount it manually.
I wanted to know how can I make fsck automatically fix HDD errors when it needs to check HDD during boot up and do not ask user for it . I found some of fsck related scripts in /etc/init/ and /etc/init.d/ but I don't know what to do with them.
I have a server with Debian on it that I regularly reboot after upgrades. Sometimes (on schedule) fsck will check a disk when the computer is booting. With the exception of sitting in front of the console to observe the fsck, how can I determine the difference between a problematic halt and an fsck (besides waiting out the fsck, hoping it is an fsck)?When I send the computer down to reboot, I will usually have a terminal window open pinging the computer so I know when it has come back up. My first thoughts drifted to fantasizing about hacking fsck to respond to pings with some special magic byte so you could tell via ping that a computer was fsck-ing, but I'm thinking there have got to be easier ways..
I have two ext3 lv's of 4GB and 10GB in my hda8 partition, and they are automounted by /dev/mapper/ in my /etc/mtab files in each of the four distros (Suse9.3, OpenSuse10.2, kubuntu7.04 and Debian Lenny 5.0.3). Since ext3 is a journalled fs I feel I ought to fsck their integrity every 3 months or so, however I don't know
a) whether they must be unmounted before running fsck, b) whether I should use a live CD such as knoppix to run the fsck command, and c) whether I can and/or should run fsck /dev/hda8, or whether I should somehow fsck each lv seperately?
I have pc/os linux 2009 installed and I recently got the following message while trying to boot up my system:
*checking root file system...fsck 1.41.4 (27-Jan-2009) dev/sda1 contains a file system with errors, check forced. /dev/sda1:Inodes that were part of a corrupted orphan linked list found. /dev/sda1:Unexpected inconsistency;run fsck manually. (i.e., without -a or -p options) fsck died with exit status 4
*An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode.
*The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. after performing system maintenance press Control-D to terminate the maintenance shell and restart the system.
Give root password for maintenance:
The problem is, when I enter my password I get an incorrect password prompt. How can I change my password so that a manual fsck can start? Why did this message error message appear in the first place?
I just downloaded OpenSuse 11.1 64 bit live cd from it's official site.I have live usb creater in my xp box , with the help of which I successfully created live USB for fedora 11 earlier. Now the problem is whenever I try to create live usb using Opensuse live ISO image after extracting all files to usb , it gets failed.The same thing is happening with OpenSolaris 11 live cd iso image. Does this mean that live usb creater I have, was only foe Fedora distros?
I have debian testing installed on my system. I have a separate home partition which i shared with Pardus2009 which i installed later on a different partition.
Now pardus boots fine without errors, but debian says "filesystem check failed" because last mount time of / is in future. it gives a maintenance shell and after a manual fsck corrects this problem, debian reboots fine, but then says theres a problem with the /home partition (but this can be ignored)
I Tarred and GZipped most of the data on one 1Tb partition and stuck the archives on a second 1Tb partition on a separate disk. I then proceeded to format the first partition with NTFS (from Linux.) The only problem is that I completely forgot that I had a CD drive and formatted sdc1 instead of sdd1! I began doing a full NTFS format and after a minute or two I cancelled it and decided to do a quick format. I then realized my mistake. I managed to find a copy of the superblock and began trying to recover the disk. fsck -t ext3 recognized the partition as NTFS but I luckily didn't have fsck.ntfs installed so it didn't touch it. I managed to get it working with fsck.ext3 (with -b,-B and -y) fsck.ext3 didn't mind that it was an NTFS partition.
Roughly how long will this take? It's running from Knoppix within a virtual machine to a USB hard drive which is 100% full. Days? Being that for a few minutes I attempted a full format am I going to end up with a bunch of corrupted archives? If I do end up with file corruption can anyone recommend a way of recovering the data / sorting it out? Is it likely to be just a few old files that are corrupt (It's my understanding that filesystems like to keep files in the same area on the disk to minimize the amount of head travel.) This might just be wishful thinking but as the filesystem fills up will ext3 put the newer files towards the end of the disk? If so then I'm hoping that a full NTFS format starts at the beginning of the disk.
My ubuntu stops when mounting system hdd. The screen display the following messages :
mountall:/etc/fstab: No such file or directory fsck from util-linux-ng 2.16 WARNING: couldn't open /etc/fstab: No such file or directory init: mountall main process (545) terminated with status 1 General error mounting filesystems. A maintenance shell will now be started. CONTROL-D will terminate this shell and re-try. udevd: can not read '/etc/udev/rules.d/z80_user.rules. Ubuntu: clean, 474879/24231936 files/28016581/96898047 blocks root@i7:~# exit_
I suspect the disk manager pysdm that i had just installed today and it had crash during the previous session. The /etc/fstab file does not exist anymore and i cant rename the fstab.bak because the disk is read-only even for my root user
I have my drives set to run fsck on boot up. This is the default setting for Fedora but if there is a problem it prompts me to run fsck manually. Is there a way to have Fedora just run fsck and fix any errors it finds on boot up?w in Debian distros you can put FSCKFIX=yes in the /etc/default/rcS file to do this. But I can't find the equivalent on Fedora.