Problem with fsck on boot
"Bruce Adams" <[email protected]> Thu, 21 Sep 2006 14:26:54 +0100
| Newsgroups | gmane.linux.suse.ia64 |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
------_=_NextPart_001_01C6DD81.9AAE8C70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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.=20
After a long time of successful running I rebooted to a forced fsck =
check=20
which hung the machine (with no output from fsck at all).=20
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=20
to correct the problem but this filesystem is /dev/sda5 when booting =
normally.
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.
------_=_NextPart_001_01C6DD81.9AAE8C70
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>Problem with fsck on boot</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=3D2>Hi,<BR>
Apologies if this is not the correct list (the general list =
appears to be jammed with spam).<BR>
I'm running a 64bit Suse 10 install dual booting with W*ndows XP on a =
dell with a SATA hard-drive.<BR>
After a long time of successful running I rebooted to a forced fsck =
check<BR>
which hung the machine (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 =
check at boot time<BR>
was no longer required.<BR>
I think the problem may be SATA related. From the boot disk I ran fsck =
/dev/hda3<BR>
to correct the problem but this filesystem is /dev/sda5 when booting =
normally.<BR>
<BR>
Firstly, Is there a way to bypass the fsck check (perhaps using a boot =
option) when it occurs?<BR>
Alternatively is there a way to disable it completely and run the check =
manually.<BR>
My installation is all on one partition (excluding swap) which =
presumably means creating<BR>
a ram disk containing fsck, unmounting the root file system and =
re-mounting it following the<BR>
check. I'm not sure how best to achieve this. Any ideas?<BR>
&=
nbsp; &n=
bsp; &nb=
sp; Regards,<BR>
&=
nbsp; &n=
bsp; &nb=
sp; Bruce.<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C6DD81.9AAE8C70--