Mailinglist Archive: opensuse (3964 mails)

[Jerome Lyles <susemail@xxxxxxxxxxxxx>]

On Monday 08 November 2004 11:29 am, Anders Johansson wrote:
> On Monday 08 November 2004 22:10, Jerome Lyles wrote:
> > On Monday 08 November 2004 03:34 am, Anders Johansson wrote:
> > > On Sunday 07 November 2004 22:23, Jerome Lyles wrote:
> > > > So...what's happening here?  I did some more digging and found the
> > > > source of the problem behavior in /etc/init.d/boot.rootfsck.
> > > >
> > > > And this is the heart of the problem:
> > > >
> > > > if test -n "$ROOTFS_BLKDEV" -a "$ROOTFS_BLKDEV" != "/" -a -b
> > > > "$ROOTFS_BLKDEV"
> > > >
> > > If you run "fsck -T -N" in the rescue system, what is the output?
> >
> > Rescue:~# fsck -T -N /dev/hda2
> > [/sbin/fsck.reiserfs(1) -- /dev/hda2] fsck.reiserfs /dev/hda2
>
> ok, I'd be greatly interested in what the error code from reiserfsck is
> that it complains about then. Could you edit /etc/init.d/boot.rootfsck and
> in the section where it prints that error message, change the first empty
> echo to
>
> echo $FSCK_RETURN
>
> then reboot, let it fail and tell us what the error code is that gets
> printed. According to the logic the error code must be 4 or greater, and
> according to "man reiserfsck" that means it must be 4, 6, 8 or 16, but if a
> plain reiserfsck run doesn't show any errors, it almost has to be either 8
> or 16, but it would be nice to know what it's complaining about

fi
echo $FSCK_RETURN

Returns nothing except an empty line.  Is this a case where FSCK actually 
returns nothing.  If it is, it's a case that wasn't anticipated and could be 
the source of the problem.

I don't know if this means anything but after I tried it two or three times I 
added another echo $FSCK_RETURN below the first one and rebooted.  As far as 
I can tell only one empty line was returned.
Jerome