View Single Post
Old 15th August 2011
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,977
Default

I do not understand why # fdisk sd0 works yet # fdisk -e sd0 fails, without a kernel message. BSDfan666 has stated he's seen similar non-error errors, but this is outside my experience. I would install sysutils/smartmontools, and look to # smartctl -s on /dev/sd0c; smartctl -a /dev/sd0c to enable SMART and then query the electronics on the drive for insights. However, you are running 4.9-release and I do not believe that is new enough for smartmontools to work with USB devices. If you are serious about recovering what is on that drive, -current may aid you in at least communicating with SMART on the drive.

Windows will not aid you with either diagnostics or recovery, since your configuration violates Windows standards and expectations.

If you can install the drive internally on an OpenBSD machine, I might be able to guide you closer to recovery. Might.
Reply With Quote