RE: Problem with fsck on boot
"Bruce Adams" <[email protected]> Fri, 22 Sep 2006 16:54:24 +0100
| Newsgroups | gmane.linux.suse.ia64 |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
------_=_NextPart_001_01C6DE5F.606F6CC1
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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).=20
Is it safe to run fsck after a lazy unmount?
Regards,
Bruce.
-----Original Message-----
From: Rafa Grim=E1n [mailto:*]
Sent: Fri 9/22/2006 12:19 PM
To: [email protected]
Subject: Re: [suse-ia64] Problem with fsck on boot
=20
Hi :)
El Jueves, 21 de Septiembre de 2006 15:52, Glen Christensen escribi=F3:
> shutdown -f now
>
> will prevent fsck from running upon reboot
>
> -Glen Christensen
>
> >>> "Bruce Adams" <[email protected]> 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=20
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=20
tune2fs.
Rafa
--=20
"Even paranoids have enemies."
Rafa Grim=E1n
Systems Engineer
Silicon Graphics Spain
Santa Engracia, 120 - Planta Baja
28003 Madrid
Spain
Tel: +34 91 3984200
Tel: +34 91 3984201
M=F3vil: +34 628 117 940
http://www.sgi.com
OpenWengo: rgriman
Skype: rgriman
------_=_NextPart_001_01C6DE5F.606F6CC1
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE>RE: [suse-ia64] Problem with fsck on boot</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=3D2>Apologies for top-posting I'm presently stuck on =
outlook remote mail :(.<BR>
<BR>
The file system is ext3.<BR>
I used hda3 from an older boot disk (which cannot actually install a =
working system for my machine).<BR>
<BR>
dumpe2fs and tune2fs look like what I need for a workaround.<BR>
The next check appears to be due in 500 mounts or the 20th November =
according to dumpe2fs.<BR>
This seems a little longer than it ought to be but explains why it took =
me so long to discover the problem.<BR>
<BR>
There is definitely a genuine problem somewhere as fsck should not be =
hanging in the first place.<BR>
I'm not entirely sure where in boot process fsck is called. Perhaps it =
is reliant on a kernel module that<BR>
isn't available until later?<BR>
<BR>
I have not tried running fsck with the system running as I am mindful if =
the<BR>
warning that it could damage the file system.<BR>
As its the root filesystem I can only unmount with umount -l (lazy).<BR>
Is it safe to run fsck after a lazy unmount?<BR>
<BR>
Regards,<BR>
Bruce.<BR>
<BR>
-----Original Message-----<BR>
From: Rafa Grim=E1n [<A HREF=3D"mailto:*">mailto:*</A>]<BR>
Sent: Fri 9/22/2006 12:19 PM<BR>
To: [email protected]<BR>
Subject: Re: [suse-ia64] Problem with fsck on boot<BR>
<BR>
Hi :)<BR>
<BR>
El Jueves, 21 de Septiembre de 2006 15:52, Glen Christensen =
escribi=F3:<BR>
> shutdown -f now<BR>
><BR>
> will prevent fsck from running upon reboot<BR>
><BR>
> -Glen Christensen<BR>
><BR>
> >>> "Bruce Adams" =
<[email protected]> 09/21/06 7:26 AM >>><BR>
><BR>
> Hi,<BR>
> Apologies if this is not the correct list (the =
general list appears to<BR>
> be jammed with spam). I'm running a 64bit Suse 10 install dual =
booting with<BR>
> W*ndows XP on a dell with a SATA hard- drive. After a long time =
of<BR>
> successful running I rebooted to a forced fsck check which hung the =
machine<BR>
> (with no output from fsck at all).<BR>
><BR>
> I was only able to recover by booting in recovery mode and running =
fsck.<BR>
> Fsck found no errors but simply updated the last check time so that =
the<BR>
> check at boot time was no longer required.<BR>
> I think the problem may be SATA related. From the boot disk I ran =
fsck<BR>
> /dev/hda3 to correct the problem but this filesystem is /dev/sda5 =
when<BR>
> booting normally.<BR>
<BR>
<BR>
SATA drives are /dev/sd, why did you use /dev/hda3? Is the drive =
configured as<BR>
PATA?<BR>
<BR>
<BR>
> Firstly, Is there a way to bypass the fsck check (perhaps using a =
boot<BR>
> option) when it occurs? Alternatively is there a way to disable =
it<BR>
> completely and run the check manually. My installation is all on =
one<BR>
> partition (excluding swap) which presumably means creating a ram =
disk<BR>
> containing fsck, unmounting the root file system and re- mounting =
it<BR>
> following the check. I'm not sure how best to achieve this. Any =
ideas?<BR>
> &nb=
sp; &nbs=
p;  =
; Regards,<BR>
> &nb=
sp; &nbs=
p;  =
; Bruce.<BR>
<BR>
<BR>
What filesystem do you have on your drive? If it's ext2/3, you can =
use<BR>
tune2fs.<BR>
<BR>
Rafa<BR>
<BR>
<BR>
--<BR>
"Even paranoids have enemies."<BR>
<BR>
Rafa Grim=E1n<BR>
Systems Engineer<BR>
<BR>
Silicon Graphics Spain<BR>
Santa Engracia, 120 - Planta Baja<BR>
28003 Madrid<BR>
Spain<BR>
<BR>
Tel: +34 91 3984200<BR>
Tel: +34 91 3984201<BR>
M=F3vil: +34 628 117 940<BR>
<BR>
<A HREF=3D"http://www.sgi.com">http://www.sgi.com</A><BR>
<BR>
OpenWengo: rgriman<BR>
Skype: rgriman<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C6DE5F.606F6CC1--