Re: /lib/casper: read error: Invalid argument

Am Sun, 14 Jan 2018 06:57:38 -0500
Charlie Li <ml_at_vishwin.info> schrieb:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> On 14/01/2018 06:10, Hartmann, O. wrote:
> > I tried to investigate with the USB image created 10th January
> > 2018 from ISO downloads and it showed, that /boot/ was obviously
> > intact, but files in /usr/sbin, /usr/bin were zero in size, also
> > some libs in /usr/lib and /lib. While /boot/ seemingly being
> > already installed while other portions failed, I knew from the past
> > that I had to replace all /boot, /bin, /sbin, /usr/sbin, /usr/bin,
> > /lib, /usr/lib , /usr/libexec and /libexec from the recent USB
> > image. I did so via "pax -v -rw -pe", but I had to "chflags noschg"
> > some files/libraries on the target to get them overwritten. I
> > simply did a
> > 
> > chflags noschg *
> > 
> > to every folder/subfolder and "pax'ed" the destination then. So
> > far. I'm able to boot into single user again, but when it comes to
> > the shell and /bin/sh is supposed to be executed, I get the
> > strange message:
> > 
> > /lib/casper/: read error: Invalid argument
> > 
> > and the prompt is jumping back to ensure the PASSWORD (console is 
> > password protected).
> >   
> Something like this happened to me once, albeit a libc.so symbol
> mismatch after a hard crash that corrupted that and some more system
> files.
> 
> So far you're on the right track with copying files off the image,
> though I extracted the relevant files/directory structures from the
> base.txz that bsdinstall uses.
> > Something is hindering to start the compiler somehow and it is
> > related to /lib/casper/: read error: Invalid argument?
> > 
> > What is wrong here? How to fix this?
> >   
> Don't reboot out of the USB image. Stay there and chroot into your
> mounted root filesystem, then run make installworld.
> 
> - -- 
> Charlie Li
> Can't think of a witty .sigline today…
> 
> (This email address is for mailing list use only;
> replace local-part with vishwin for off-list communication)
> -----BEGIN PGP SIGNATURE-----
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iQIzBAEBCgAdFiEE/RdyC3Asy49czZEGtQ4IJhNZSS0FAlpbRZ0ACgkQtQ4IJhNZ
> SS0aAxAAplLJ9NCLgttDDRLANK+ql15E5AE6pV1Y8jdLM7CunUzgMsyg/1hhy8ZK
> 2TG/0mEE7+jsxYjW5Wu9uBjsGaRuwY4dAO7TNdkbn3DMzJsrbBCfkXKGjeFKHwQu
> CB2fZRwfH6hdR0CxMeth9ftPHn8mbEqwl5YC4SLXBzixgi8Hpjj5J2Gne2nIur7q
> yhXdChon+k50zl+WxAeCNXTkKK7QKEANh56D/6VgTEyR1POFJqKBywLKm07tePUC
> 4Yqo4IPQsJsfQFCJ5V7o87PWqIpfsb/gPJkEsT81MKT0/XWRHXtHvzA0Ero7dMDS
> WbGFblyPg7GRzNRC7FLfqPmcOW6Qc3JFr2KA6b5IVoV3IhCor1o+mEV8tkZY2iPz
> scCImjPqr+QWoSt2Hv0QUc8i3L40pc4OAxslC8lCOKZrePA/nIowfRS8oJmhgKrL
> 9gJDQxPQGAn0fYKoY3n+oI95YfIn9MBE6hmpUKfXSRqh+s6xX5sMnf2tqm7Swiul
> Tjp05MbhBQn/Yxmwxa8Lnk6U3jtumza8qS8SXX3b039+8ADd4Y9L6l0IVk7+cG2i
> uNXxbl9o5jqoUyRgEvGAGzohGGUzzpz4k/wHht1gWeEmww4WJ2VN6eL8FFepWi2v
> o5rOeFbnuSzqOOslA6rQ6mkwDKPRoIVNFWEkQO1FR9MjyhKk7+4=
> =YOoR
> -----END PGP SIGNATURE-----
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"

I was afraid of using bsdinstall or just tar'ing the base.txz into the mounted partition,
since I know that several issues existed in the past with overwriting crucuial
files. /etc/ is always backuped, but /var/db holds other files, like from OpenLDAP. And
it seems FreeBSD didn't take care of those.

Somehow I "bravely" extracted base.txz - successfully. 

I wasn't able to isolate the /lib/casper/ issue - which is really a pity since it would
have been important for desaster-recovery analysis.

Another point is that FreeBSD's kernel is quiet when it fails to boot into multiuser
mode. The phenomenon with the broken installation was, that the kernel stopped issuing
anything after USB subsystem has been started. Pluggin and unplugging was reported, but
the boot didn't proceed. Somehow this is annoying.

Also, with CURRENT  FreeBSD 12.0-CURRENT #75 r327948: Sat Jan 13 23:00:08 CET 2018 amd64
up and running again, there are some strange leftovers in /usr/lib:

find ./ -ctime +5 -a -name "*.a" -exec ls -l {} \;
-r--r--r--  1 root  wheel  173698 Dec 23 23:02 ./libmlx5.a
-r--r--r--  1 root  wheel  75698 Dec 23 23:02 ./libibnetdisc.a
-r--r--r--  1 root  wheel  43516 Dec 25 03:49 ./libcxgb4.a
-r--r--r--  1 root  wheel  6044 Dec 23 23:02 ./libnandfs.a
-r--r--r--  1 root  wheel  6580 Dec 23 23:02 ./libnandfs_p.a
-r--r--r--  1 root  wheel  86580 Dec 25 03:49 ./libosmcomp.a
-r--r--r--  1 root  wheel  22104 Oct 31 13:33 ./libibcommon.a
-r--r--r--  1 root  wheel  69812 Dec 23 23:02 ./libibumad.a
-r--r--r--  1 root  wheel  105084 Dec 25 03:49 ./libibverbs.a
-r--r--r--  1 root  wheel  182118 Dec 23 23:02 ./libibmad.a
-r--r--r--  1 root  wheel  67548 Dec 23 23:02 ./libmlx4.a
-r--r--r--  1 root  wheel  51190 Oct 16 22:31 ./libmthca.a
-r--r--r--  1 root  wheel  125960 Dec 23 23:02 ./libopensm.a
-r--r--r--  1 root  wheel  39574 Dec 23 23:02 ./libosmvendor.a
-r--r--r--  1 root  wheel  17466 Dec 23 23:02 ./libibcm.a
-r--r--r--  1 root  wheel  62058 Dec 23 23:02 ./librdmacm.a
-r--r--r--  1 root  wheel  112430 Oct 31 13:33 ./libibsdp.a

Those files aren't addressed by "make delete-old-libs" and some of them seem to belong to
outdated or switched off portions of the tree.

Regards,

Oliver

-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).