RE: [suse-ia64] Problem with fsck on boot
Apologies for top-posting I'm presently stuck on outlook remote mail :(. The file system is ext3. I used hda3 from an older boot disk (which cannot actually install a working system for my machine). dumpe2fs and tune2fs look like what I need for a workaround. The next check appears to be due in 500 mounts or the 20th November according to dumpe2fs. This seems a little longer than it ought to be but explains why it took me so long to discover the problem. There is definitely a genuine problem somewhere as fsck should not be hanging in the first place. I'm not entirely sure where in boot process fsck is called. Perhaps it is reliant on a kernel module that isn't available until later? I have not tried running fsck with the system running as I am mindful if the warning that it could damage the file system. As its the root filesystem I can only unmount with umount -l (lazy). Is it safe to run fsck after a lazy unmount? Regards, Bruce. -----Original Message----- From: Rafa Grimán [mailto:*] Sent: Fri 9/22/2006 12:19 PM To: suse-ia64@suse.com Subject: Re: [suse-ia64] Problem with fsck on boot Hi :) El Jueves, 21 de Septiembre de 2006 15:52, Glen Christensen escribió:
shutdown -f now
will prevent fsck from running upon reboot
-Glen Christensen
"Bruce Adams" <Bruce.Adams@tns-global.com> 09/21/06 7:26 AM >>>
Hi, Apologies if this is not the correct list (the general list appears to be jammed with spam). I'm running a 64bit Suse 10 install dual booting with W*ndows XP on a dell with a SATA hard- drive. After a long time of successful running I rebooted to a forced fsck check which hung the machine (with no output from fsck at all).
I was only able to recover by booting in recovery mode and running fsck. Fsck found no errors but simply updated the last check time so that the check at boot time was no longer required. I think the problem may be SATA related. From the boot disk I ran fsck /dev/hda3 to correct the problem but this filesystem is /dev/sda5 when booting normally.
SATA drives are /dev/sd, why did you use /dev/hda3? Is the drive configured as PATA?
Firstly, Is there a way to bypass the fsck check (perhaps using a boot option) when it occurs? Alternatively is there a way to disable it completely and run the check manually. My installation is all on one partition (excluding swap) which presumably means creating a ram disk containing fsck, unmounting the root file system and re- mounting it following the check. I'm not sure how best to achieve this. Any ideas? Regards, Bruce.
What filesystem do you have on your drive? If it's ext2/3, you can use tune2fs. Rafa -- "Even paranoids have enemies." Rafa Grimán Systems Engineer Silicon Graphics Spain Santa Engracia, 120 - Planta Baja 28003 Madrid Spain Tel: +34 91 3984200 Tel: +34 91 3984201 Móvil: +34 628 117 940 http://www.sgi.com OpenWengo: rgriman Skype: rgriman
Hi :) El Viernes, 22 de Septiembre de 2006 17:54, Bruce Adams escribió:
Apologies for top-posting I'm presently stuck on outlook remote mail :(.
The file system is ext3. I used hda3 from an older boot disk (which cannot actually install a working system for my machine).
dumpe2fs and tune2fs look like what I need for a workaround. The next check appears to be due in 500 mounts or the 20th November according to dumpe2fs. This seems a little longer than it ought to be but explains why it took me so long to discover the problem.
There is definitely a genuine problem somewhere as fsck should not be hanging in the first place. I'm not entirely sure where in boot process fsck is called. Perhaps it is reliant on a kernel module that isn't available until later?
What about /etc/fstab? The sixth (last) column will launch an fsck when time comes (500 mounts/20th November in your case) if the last column is set to 1. If you don't want to run fsck, just set it to 0 (zero).
I have not tried running fsck with the system running as I am mindful if the warning that it could damage the file system. As its the root filesystem I can only unmount with umount -l (lazy). Is it safe to run fsck after a lazy unmount?
HTH Rafa
-----Original Message----- From: Rafa Grim�n [mailto:*] Sent: Fri 9/22/2006 12:19 PM To: suse-ia64@suse.com Subject: Re: [suse-ia64] Problem with fsck on boot
Hi :)
El Jueves, 21 de Septiembre de 2006 15:52, Glen Christensen escribi�:
shutdown -f now
will prevent fsck from running upon reboot
-Glen Christensen
"Bruce Adams" <Bruce.Adams@tns-global.com> 09/21/06 7:26 AM >>>
Hi, Apologies if this is not the correct list (the general list appears to be jammed with spam). I'm running a 64bit Suse 10 install dual booting with W*ndows XP on a dell with a SATA hard- drive. After a long time of successful running I rebooted to a forced fsck check which hung the machine (with no output from fsck at all).
I was only able to recover by booting in recovery mode and running fsck. Fsck found no errors but simply updated the last check time so that the check at boot time was no longer required. I think the problem may be SATA related. From the boot disk I ran fsck /dev/hda3 to correct the problem but this filesystem is /dev/sda5 when booting normally.
SATA drives are /dev/sd, why did you use /dev/hda3? Is the drive configured as PATA?
Firstly, Is there a way to bypass the fsck check (perhaps using a boot option) when it occurs? Alternatively is there a way to disable it completely and run the check manually. My installation is all on one partition (excluding swap) which presumably means creating a ram disk containing fsck, unmounting the root file system and re- mounting it following the check. I'm not sure how best to achieve this. Any ideas? Regards, Bruce.
What filesystem do you have on your drive? If it's ext2/3, you can use tune2fs.
Rafa
-- "Even paranoids have enemies." Rafa Grimán Systems Engineer Silicon Graphics Spain Santa Engracia, 120 - Planta Baja 28003 Madrid Spain Tel: +34 91 3984200 Tel: +34 91 3984201 Móvil: +34 628 117 940 http://www.sgi.com OpenWengo: rgriman Skype: rgriman
participants (2)
-
Bruce Adams -
Rafa Grimán