Hi, two ways come to my mind:
1) On a normal Debian system, the fsck check at boot time is skipped,
when the file /fastboot is present. It gets deleted at each boot-up.
So, take down your broken hard drive, boot, run `touch /fastboot`, power
down, put your broken hard drive back in and boot. Don't forget to run
`touch /fastboot` if you need to reboot, but still have the broken
drive.
2) `man fstab` says:
The sixth field, (fs_passno), is used by the fsck(8) program to
deter- mine the order in which filesystem checks are done at
reboot time. [...] If the sixth field is not present or zero, a
value of zero is returned and fsck will assume that the
filesystem does not need to be checked.
So, edit your /etc/fstab file and change the last field on all
filesystems on the bad drive to 0 (should be 2 right now).
HTH,
Viktor
Rob Dupuis wrote:
> > -----Original Message-----
> > From: news [mailto:[EMAIL PROTECTED] Behalf Of Monique Y. Herman
> > Sent: 09 October 2003 22:04
> > To: [EMAIL PROTECTED]
> > Subject: Re: fsck hangs my machine unpredictably
> >
> >
> > On Thu, 09 Oct 2003 at 19:15 GMT, Rob Dupuis penned:
> > > Hi All.
> > >
> > > My one of my hard drives has a whole load of errors on it. When the
> > > machine boots fsck is run, and when it gets to some percentage (eg
> > > 69.9%) and then I get an msg that says 'Duplicate or bad block in
> > > use.' It then proceeds to start a pass for duplicate and bad blocks,
> > > and it finds a *lot* of bad/duplicate inodes. Unfortunately, before
> > > this pass can complete, the machine hangs (ie the pass stalls and num
> > > lock etc on the keyboard stops responding) and I have to hard reset to
> > > bring it back up.
> > >
> > > On one occasion, I the fsck on bootup did complete, but when I ran a
> > > fsck -p to try to fix the errors, this hung the machine in a similar
> > > way to above. The other (3) times it always hung on the boot fsck
> > > pass and at a different inode each time.
> > >
> > > I'm a bit of a linux newbie, so any help on ways forward would be
> > > greatly appreciated.
> > >
> > > Thanks, Rob
> > >
> >
> > Um, you do realize that if the hard drive is causing fsck to blow
> > chunks, it's because the hard drive is defective and needs to be
> > replaced, right?
> >
> > --
> > monique
> >
>
> Yeah, I thought that was probably the case. Is there any way I can boot the
> machine and skip fsck running automatically, try to mount the drive and
> salvage some of the data to another drive? (I should point out my system
> drive is fine so I can boot OK if I unplug the defective drive, its my 180G
> data drive thats screwed.)
>
> Rob
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
Vor dem Absturz kommt die Party!
signature.asc
Description: Digital signature
