Hi, I don’t know how to debug this one. This time,
the boot screen seems to say that my mirrored /home
directory is not fsck-able. I’ve booted into Debian
and have fsck-ed /dev/md0 and everything is fine.
The openSuSE boot still complains. This happens so
early on that the messages in /opensuse/var/log/messages
stop with the last shutdown. (It went down cleanly with
no complaint.)
So, what should I be looking at? Whatever you ask for, it
will have to be hand transcribed and then typed back in
because nothing has mounted. Oh, yeah, the full symptom:
it asks for the root password and completely locks up.
Hard. No response. No three-fingered-salute. It is
power cycle time. This is so old.
bkorb wrote:
> Hi, I don’t know how to debug this one. This time,
> the boot screen seems to say that my mirrored /home
> directory is not fsck-able.
what do you mean by “mirrored /home directory”?
reading back though your earlier posts i wonder did you ever fully
recover from the unintentional ‘upgrade’ from your working 11.1 to
11.2 (you had already declared 11.2 DOA on your machine and gone back
to 11.1)?
that is, what were you running:
-11.1 from a fresh install after the “unintentional upgrade”, or
-11.2 from a fresh install after the killer mistake, or
-you don’t really know what bits of which where hanging around because
you ‘repaired’ the mess instead of doing a fresh install
is your “mirrored /home directory” on ext3 or something else?
note: the “three-fingered-salute” you tried, you should not…reserve
that maneuver for your game machine…
the question is, why does the boot want to run fsck anywho? what
happened?
if, as you say the previous shutdown was smooth with no complaints in
the surviving /var/log/messages, then i can think of NO possible
problem other than hardware failure, and guess your drive is toast…
OR something so catastrophic and magic occurred between the smooth
shutdown and next boot in your openSUSE that it is one for the record
books…
otoh, i suspect you have right properly murdered your system and will
have to start over with a fresh install…
It means I have a separate file system using mirrored partitions
Device Boot Start End Blocks Id System
sdb1 2 30401 244188000 fd Linux raid
Device Boot Start End Blocks Id System
sdc1 2 30401 244188000 fd Linux raid
and these partitions are not on the main drive. I’ve got three.
I’ve got three root partitions: SuSE 11.2 (dead), SuSE 11.1
(now dead) and Debian. I’m using the latter now and I see
the /home partition just fine:
/dev/md0 on /home type ext3 (rw)
…
note: the “three-fingered-salute” you tried, you should
not…reserve that maneuver for your game machine.
I don’t have a game machine. I reserve the maneuver for desperation. With the system completely non-responsive, I used it just before the power cycle maneuver. Note: Ctl-Alt-Del was ineffective.
OR something so catastrophic and magic occurred between the smooth
shutdown and next boot in your openSUSE that it is one for the record
books…
otoh, i suspect you have right properly murdered your system and will
have to start over with a fresh install.
Flaky sound due to pulseaudio not being compatible with KDE and
nevertheless installed; and the occasional blank right monitor
all recent and all not withstanding, I’ve been using this installation since the release of 11.2. I was hoping to avoid another re-installation. I was hoping that it would be possible to diagnose the real issue since the real issue is not a corrupt /home file system – despite the fact that the boot messages say I need to run fsck by hand. (I did so from Debian.) All file systems pass fsck. So it is something else. It happens sufficiently early on that “init 1” doesn’t work.
