Am 06/28/18 um 23:49 schrieb Stefan Wollny:
> Hi there!
>
> Unfortunately I have to hijack my own thread as it has the last working dmesg.
>
> Right after I had asked on misc@ about those KDE-apps I upgraded to the latest snapshot for amd64-current. By this I was hit by the "libxshmfence.so.0.0-issue".
> https://marc.info/?l=openbsd-tech&m=153003604704089&w=2
>
> Well - running -current is usually rock-solid, but I am well aware that every now-and-then things might go wrong and will be corrected by the devs with the next snapshot (or the one thereafter). Happens remarkably seldom but obviously here I had to make use of the next snapshot, which I did: Wham! I cannot log-in to the system any more!
>
> "booting sr0a:/bsd: sr0a:/bsd: Inappropriate file type or format
> failed(79). will try /bsd"
>
> Yes - this system is fully encrypted, secured by a key-disk. I have dd'ed two more copies of this key, both behave the same. Thus I dare to suppose that there is no technical issue with the key (in particular as the other two USB-keys have not been attached at the time of the last upgrade).
>
> Most likely I did unknowingly s.th. really dumb.
>
> OK - how to proceed? Yes - I am lucky having backed up the relevant data the night before. My fallback solution is to simply reinstall everything. Annoying, as it will take a little time, but I will survive.
>
> My question is, as I can boot into 'bsd.rd', what alternative(s) I have to
> '# bioctl -c C -k /dev/sd1a -l /sd0a softraid0'
> softraid0: chunk sd0a already in use
>
> bsd.rd-dmesg shows at the end sd1 being the USB-key-disk and sd2 being the unencrypted OpenBSD-crypto-file, thus I used sd0 with 'bioctl'.
>
> Anyone a clue what might have gone wrong and how to proceed (except reinstallation)?
>
> TIA!
>
> Best,
> STEFAN
>
For the records:
After some more reading of man-pages, the OpenBSD FAQ and some other
sites by the devs I realized that nothing is wrong with softraid(0) as
the encrypted disk (sd0) shows up as sd2. This 'disk' is accessible via
bsd.rd.
All that needed to be done was fsck'ing the partitions (/usr needed
help) and updating the system via bsd.rd to be back in business.
Another fine example that it takes a lot to wreck OpenBSD, actually.
To all devs: THANK YOU!
Best,
STEFAN
No comments:
Post a Comment