Re: crypto volume damaged after crash
On Thu, Nov 08, 2012 at 10:51:05PM +1100, Joel Sing wrote: > If this is a hardware failure then it is not overly interesting, however if > the underlying device is healthy then I would be interested in getting > further details. Thanks. I ran a diagnostics and it turned out to be the disk. Wonder when I will learn to always check the most obvious thing first. Sorry for the noise.
Re: crypto volume damaged after crash
On Thu, 8 Nov 2012, Erling Westenvik wrote: > I'm running current on a ThinkPad T500 with a fully encrypted disk (sd0) > and using a usb keydisk (sd1) to assemble the crypto volume on sd2. Last > snapshot upgrade was around 11th of October. > > Yesterday the machine suddenly stopped responding to keystrokes (even > though xscreensaver was running "fine"). Pinging it from one of my other > OpenBSD-machines worked, but when I tried to ssh into it, the connection > just timed out. Finally, when I tried to switch console by hitting > Ctrl-Alt-F2, it froze completely. > > No big deal, I thought. It had crashed numerous times before from empty > battery. So I booted, plugged in the keydisk, but after entering the > usual location for boot and swap partitions: > > root device (default sd0a): sd2a > swap device (default sd2b): sd0b > > I got this: (I had to write this down by hand. FYI, in case of typos.) > > ---8<--- > root on sd2a swap on sd0b dump on sd0b > Automatic boot in process: starting file system check. > /dev/sd2a (290d4f6dcbc2d7a7.a): file system is clean; not checking > softraid0: i/o error on block 257269168 This is the biggest hint at the real issue - for some reason the I/O to the underlying device has failed, which has then been propagated to the softraid volume. Unfortunately, at this stage this is sufficient to force the softraid crypto volume offline, hence from here on in there will be nothing but I/O errors when reading or writing to the volume (hence fsck_ffs complaining). If this is a hardware failure then it is not overly interesting, however if the underlying device is healthy then I would be interested in getting further details. > CANNOT READ: BLK 183692704 > /dev/sd2k (290d4f6dcbc2d7a7.k): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. CANNOT READ: BLK 128 > /dev/sd2d (290d4f6dcbc2d7a7.d): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. CANNOT READ: BLK 128 > /dev/sd2f (290d4f6dcbc2d7a7.f): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. CANNOT READ: BLK 128 > /dev/sd2g (290d4f6dcbc2d7a7.g): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. CANNOT READ: BLK 128 > /dev/sd2h (290d4f6dcbc2d7a7.h): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. CANNOT READ: BLK 128 > /dev/sd2j (290d4f6dcbc2d7a7.j): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. CANNOT READ: BLK 128 > /dev/sd2i (290d4f6dcbc2d7a7.i): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. CANNOT READ: BLK 128 > /dev/sd2e (290d4f6dcbc2d7a7.e): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENSY: > ffs: 290d4f6dcbc2d7a7.k (/home), ffs: 290d4f6dcbc2d7a7.d (/tmp), > ffs: 29 0d4f6dcbc2d7a7.f (/usr), ffs: 290d4f6dcbc2d7a7.g (/usr/X11R6), ffs: > 290d4f6dcbc2 d7a7.h (/usr/local), ffs: 290d4f6dcbc2d7a7.j (/usr/obj), ffs: > 290d4f6dcbc2d7a7.i (/usr/src), ffs: 290d4f6dcbc2d7a7.e (/var) > Automatic file system check failed; help! > Nov 7 23:09:59 init: /etc/pwd.db: Input/output error > Enter pathname of shell or RETURN for sh: > # fsck_ffs 290d4f6dcbc2d7a7.k > ** /dev/sd2k (290d4f6dcbc2d7a7.k ) > > CANNOT READ: BLK 128 > CONTINUE? [Fyn?] > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 128, 129, 130, 131, 132, 133, > 134, 135, 136, 137, 138, 139, 140, 141, 142, 143 > > LOOK FOR ALTERNATE SUPERBLOCKS? [Fyn?] _ > --->8--- > > Pressing "y" just causes similar messages to pop up "ad infitum". > > Any clues? I got everything backed up but would like to understand what > is going on rather than just do a fresh install. > > Erling -- "Reason is not automatic. Those who deny it cannot be conquered by it. Do not count on them. Leave them alone." -- Ayn Rand
Re: crypto volume damaged after crash
On Thu, Nov 8, 2012 at 3:27 AM, Erling Westenvik wrote: > I'm running current on a ThinkPad T500 with a fully encrypted disk (sd0) > and using a usb keydisk (sd1) to assemble the crypto volume on sd2. Last > snapshot upgrade was around 11th of October. > > Yesterday the machine suddenly stopped responding to keystrokes (even > though xscreensaver was running "fine"). Pinging it from one of my other > OpenBSD-machines worked, but when I tried to ssh into it, the connection > just timed out. Finally, when I tried to switch console by hitting > Ctrl-Alt-F2, it froze completely. > > No big deal, I thought. It had crashed numerous times before from empty > battery. So I booted, plugged in the keydisk, but after entering the > usual location for boot and swap partitions: > > root device (default sd0a): sd2a > swap device (default sd2b): sd0b > > I got this: (I had to write this down by hand. FYI, in case of typos.) > > ---8<--- > root on sd2a swap on sd0b dump on sd0b > Automatic boot in process: starting file system check. > /dev/sd2a (290d4f6dcbc2d7a7.a): file system is clean; not checking > softraid0: i/o error on block 257269168 > CANNOT READ: BLK 183692704 > /dev/sd2k (290d4f6dcbc2d7a7.k): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. > CANNOT READ: BLK 128 > /dev/sd2d (290d4f6dcbc2d7a7.d): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. > CANNOT READ: BLK 128 > /dev/sd2f (290d4f6dcbc2d7a7.f): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. > CANNOT READ: BLK 128 > /dev/sd2g (290d4f6dcbc2d7a7.g): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. > CANNOT READ: BLK 128 > /dev/sd2h (290d4f6dcbc2d7a7.h): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. > CANNOT READ: BLK 128 > /dev/sd2j (290d4f6dcbc2d7a7.j): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. > CANNOT READ: BLK 128 > /dev/sd2i (290d4f6dcbc2d7a7.i): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. > CANNOT READ: BLK 128 > /dev/sd2e (290d4f6dcbc2d7a7.e): UNEXPECTED INCONSISTENCY: RUN fsck_ffs > MANUALLY. > THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENSY: > ffs: 290d4f6dcbc2d7a7.k (/home), ffs: 290d4f6dcbc2d7a7.d (/tmp), ffs: > 29 > 0d4f6dcbc2d7a7.f (/usr), ffs: 290d4f6dcbc2d7a7.g (/usr/X11R6), ffs: > 290d4f6dcbc2 > d7a7.h (/usr/local), ffs: 290d4f6dcbc2d7a7.j (/usr/obj), ffs: > 290d4f6dcbc2d7a7.i > (/usr/src), ffs: 290d4f6dcbc2d7a7.e (/var) > Automatic file system check failed; help! > Nov 7 23:09:59 init: /etc/pwd.db: Input/output error > Enter pathname of shell or RETURN for sh: > # fsck_ffs 290d4f6dcbc2d7a7.k > ** /dev/sd2k (290d4f6dcbc2d7a7.k ) > > CANNOT READ: BLK 128 > CONTINUE? [Fyn?] > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 128, 129, 130, 131, 132, 133, > 134, > 135, 136, 137, 138, 139, 140, 141, 142, 143 > > LOOK FOR ALTERNATE SUPERBLOCKS? [Fyn?] _ > --->8--- > > Pressing "y" just causes similar messages to pop up "ad infitum". > > Any clues? I got everything backed up but would like to understand what > is going on rather than just do a fresh install. Since you have backups, I suggest you to just do a fresh install and take advantage of the new boot(8) code jsing@ did in -current. Real FDE is simply fantastic! Ciao, David
crypto volume damaged after crash
I'm running current on a ThinkPad T500 with a fully encrypted disk (sd0) and using a usb keydisk (sd1) to assemble the crypto volume on sd2. Last snapshot upgrade was around 11th of October. Yesterday the machine suddenly stopped responding to keystrokes (even though xscreensaver was running "fine"). Pinging it from one of my other OpenBSD-machines worked, but when I tried to ssh into it, the connection just timed out. Finally, when I tried to switch console by hitting Ctrl-Alt-F2, it froze completely. No big deal, I thought. It had crashed numerous times before from empty battery. So I booted, plugged in the keydisk, but after entering the usual location for boot and swap partitions: root device (default sd0a): sd2a swap device (default sd2b): sd0b I got this: (I had to write this down by hand. FYI, in case of typos.) ---8<--- root on sd2a swap on sd0b dump on sd0b Automatic boot in process: starting file system check. /dev/sd2a (290d4f6dcbc2d7a7.a): file system is clean; not checking softraid0: i/o error on block 257269168 CANNOT READ: BLK 183692704 /dev/sd2k (290d4f6dcbc2d7a7.k): UNEXPECTED INCONSISTENCY: RUN fsck_ffs MANUALLY. CANNOT READ: BLK 128 /dev/sd2d (290d4f6dcbc2d7a7.d): UNEXPECTED INCONSISTENCY: RUN fsck_ffs MANUALLY. CANNOT READ: BLK 128 /dev/sd2f (290d4f6dcbc2d7a7.f): UNEXPECTED INCONSISTENCY: RUN fsck_ffs MANUALLY. CANNOT READ: BLK 128 /dev/sd2g (290d4f6dcbc2d7a7.g): UNEXPECTED INCONSISTENCY: RUN fsck_ffs MANUALLY. CANNOT READ: BLK 128 /dev/sd2h (290d4f6dcbc2d7a7.h): UNEXPECTED INCONSISTENCY: RUN fsck_ffs MANUALLY. CANNOT READ: BLK 128 /dev/sd2j (290d4f6dcbc2d7a7.j): UNEXPECTED INCONSISTENCY: RUN fsck_ffs MANUALLY. CANNOT READ: BLK 128 /dev/sd2i (290d4f6dcbc2d7a7.i): UNEXPECTED INCONSISTENCY: RUN fsck_ffs MANUALLY. CANNOT READ: BLK 128 /dev/sd2e (290d4f6dcbc2d7a7.e): UNEXPECTED INCONSISTENCY: RUN fsck_ffs MANUALLY. THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENSY: ffs: 290d4f6dcbc2d7a7.k (/home), ffs: 290d4f6dcbc2d7a7.d (/tmp), ffs: 29 0d4f6dcbc2d7a7.f (/usr), ffs: 290d4f6dcbc2d7a7.g (/usr/X11R6), ffs: 290d4f6dcbc2 d7a7.h (/usr/local), ffs: 290d4f6dcbc2d7a7.j (/usr/obj), ffs: 290d4f6dcbc2d7a7.i (/usr/src), ffs: 290d4f6dcbc2d7a7.e (/var) Automatic file system check failed; help! Nov 7 23:09:59 init: /etc/pwd.db: Input/output error Enter pathname of shell or RETURN for sh: # fsck_ffs 290d4f6dcbc2d7a7.k ** /dev/sd2k (290d4f6dcbc2d7a7.k ) CANNOT READ: BLK 128 CONTINUE? [Fyn?] THE FOLLOWING DISK SECTORS COULD NOT BE READ: 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143 LOOK FOR ALTERNATE SUPERBLOCKS? [Fyn?] _ --->8--- Pressing "y" just causes similar messages to pop up "ad infitum". Any clues? I got everything backed up but would like to understand what is going on rather than just do a fresh install. Erling
