It happened again. I'm using a laptop with a short power cord and
sometimes I recline my recliner and don't notice it fell out. I'm
usually only up here in the winter.
Anyway I did the drive diagnostics again, saw the end this time and it
didn't find anything wrong. Rebooted and it fscked the b
It's running again. I ran Seagate Diagnostics, the long version, like
2 hours. When it was about 97% done it hadn't given any messages, and
I went to dinner. When I came back I found I'd knocked the power plug
out, the battery had run down, so I booted it up cold. Took longer
than usual but it
On Mon, Feb 29, 2016 at 11:24:23AM -0500, Alan Corey wrote:
> Everything's been stable for months. Then I was running badblocks on an SD
> card plugged into a USB card reader. The screen went white, I couldn't
> ssh to it, so I killed the power. It boots to just past the file system
> checks and
I forgot, wd0a and e aren't the only OpenBSD partitions, the biggie is
wd0m, about 500 gigs. There's 4 gigs of RAM and I never had a problem
with it before, but I can reproduce the uvm fault by trying to fsck it
in single user mode. I don't remember whether swap is on at that
point or not. Maybe
Transcribing from a cell phone picture of the screen on another machine later:
/dev/rwd0a fscked OK
/dev/rwd0e fscked OK (both of my OpenBSD partitions)
acpivideo1 unknown event 0x00
uhubs 0-6 detached
uhubs 0-6 at usb0-6 "Intel UHCI (and EHCI) root hub" rev 1.00 (2.0 on the EHCI)
uvm_fault (0xdaa
Everything's been stable for months. Then I was running badblocks on an SD
card plugged into a USB card reader. The screen went white, I couldn't
ssh to it, so I killed the power. It boots to just past the file system
checks and hangs, disk access light on. Did that before so I went away for
an
6 matches
Mail list logo
