2012/5/20 Ted Unangst <[email protected]> > On Sun, May 20, 2012 at 20:47, Joaquin Herrero wrote: > > Hi, > > > > An OpenBSD 4.3 GENERIC Virtual Machine I have on VMware ESXi 3.5 crashed > > and after rebooting it complains that one of the disks is not configured: > > > No traces of the a partition in the disklabel! > > I accessed the hypervisor via ssh and can see that the datafile for that > > disk is still there. Checked the VMware configuration to see the name of > > the file containing the slice: > > you may want to try running scan_ffs. Or, if you used the whole disk > before, adding a new partition back may work, but disklabels do > not usually just disappear, so something went very wrong. >
Tried with scan_ffs with the following result: # scan_ffs sd2c scan_ffs: lseek: Invalid argument Tried also to create partition "a" so the disklabel now shows # disklabel sd2 # /dev/rsd1c: type: SCSI disk: SCSI disk label: Virtual disk flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 261 total sectors: 4194304 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # size offset fstype [fsize bsize cpg] a: 4194241 63 4.2BSD 2048 16384 1 c: 4194304 0 unused 0 0 But when I try to mount it an error shows up: # mount /dev/sd2a /mnt mount_ffs: /dev/sd1a on /mnt: Invalid argument Tried also to use scan_ffs on the new "a" partition, but same error: # scan_ffs -v sd2a scan_ffs: lseek: Invalid argument Tried also with "scan_ffs -s", the smart mode. Same result, lseek: Invalid argument So it seems that the disk is corrupted, but I am not clever enough to interpret the common "invalid argument" error. Any other ideas to try will be very welcome. Thanks a lot. -- Joaquin Herrero, @joakinen perl -le '$_="=6<678428378>12376=2>:02;:19<5>:4"; tr[0->][DREAM.IT KOWSVC]; print'
