Hi Tim,
> > The machine swiftly boots from the remaining drive but then one of
> > systemd's targets is to fsck the RAID mirror and that fails as
> > a drive is missing. systemd promptly stops many of the things it
> > had started and drops me into rescue mode.
>
> Can you not simply stop the systemd FSCK from running (I am asking the
> obvious question and well as learning when the correct answer comes
> along.)
I don't think I can stop the systemd fsck target from running because
many other targets indirectly depend on that completing, i.e. they
should only start once the fsck has successfully finished. That's why
when the fsck currently fails, systemd ensures those dependencies are
stopped before leaving me with a root shell.
It seems things have worsened since the weekend. My guess is the disk
controller delivered corrupt data from the bad drive which ended up on
the good one, trashing filesystem metadata. An fsck wants to ‘fix’ so
much that little is left, e.g. shared libraries needed to boot are now
no longer present.
... i_size is 18446744073709551615, should be 0.
$ dc -e '18446744073709551615 16op'
FFFFFFFFFFFFFFFF
$ dc -e '18446744073709551615 16op' | sed 's/..../& /g'
FFFF FFFF FFFF FFFF
$
Fortunately, there's a third USB drive with a manually maintained
mirror, only a day or two out of date, which can be used to set up a new
system.
--
Cheers, Ralph.
--
Next meeting: Online, Jitsi, Tuesday, 2025-01-07 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... https://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
