Problems with Disks after power loss

Status
Not open for further replies.

4things

Cadet
Joined
Jun 27, 2012
Messages
2
Hey,

yesterday our powerline was cut by workers on the street so my server is dead.
After i restartet it it gave the following output:

GEOM: da0s2: geometry does not match label (16h,63s != 255h,63s)

After a short research i figured out to write the filesystem via fdisk like so:

# sysinstall

Go to “Configure”

Go to “Fdisk”

Do “W” (=write) and ignore the Warning

Do not install the bootmanger (choose “Cancel”)

Exit the install

After restarting the machine i get these error:

ugen4.2: <JetFlash> at usbus4
umass0: <JetFlash Mass Storage Device, class 0/0, rev 2.00/1.00, addr 2> on usbus4
ada0 at ahcich0 bus 0 scbus2 target 0 lun 0
ada0: <ST3500630AS 3.AAD> ATA-7 SATA 2.x device
ada0: 300.000MB/s transfers (SATA 2.x, da0 at umass-sim0 bus 0 scbus8 target 0 lun 0
da0: <JetFlash Transcend 4GB 8.07> Removable Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: 3829MB (7843838 512 byte sectors: 255H 63S/T 488C)
UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
ada1 at ahcich1 bus 0 scbus3 target 0 lun 0
ada1: <ST3500630AS 3.AAD> ATA-7 SATA 2.x device
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
ada2 at ahcich2 bus 0 scbus4 target 0 lun 0
ada2: <SAMSUNG HD103UJ 1AA01112> ATA-7 SATA 2.x device
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada3 at ahcich3 bus 0 scbus5 target 0 lun 0
ada3: <ST3500630AS 3.AAE> ATA-7 SATA 1.x device
ada3: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
Trying to mount root from ufs:/dev/ufs/FreeNASs1a
/: bad dir ino 75090 at offset 2028: mangled entry
/: bad dir ino 75090 at offset 2028: mangled entry
/: bad dir ino 68546 at offset 376: mangled entry
/: bad dir ino 68546 at offset 376: mangled entry
/: bad dir ino 68546 at offset 376: mangled entry
g_vfs_done():ufs/FreeNASs1a[READ(offset=275847811072, length=4096)]error = 5
vnode_pager_getpages: I/O read error
vm_fault: pager read error, pid 35 (mdmfs)
pid 35 (mdmfs), uid 0: exited on signal 11
/: bad dir ino 75090 at offset 2028: mangled entry
g_vfs_done():ufs/FreeNASs1a[READ(offset=1617653760, length=512)]error = 5
g_vfs_done():ufs/FreeNASs1a[READ(offset=1617653760, length=512)]error = 5
g_vfs_done():ufs/FreeNASs1a[READ(offset=275847811072, length=4096)]error = 5
vnode_pager_getpages: I/O read error
vm_fault: pager read error, pid 41 (mdmfs)
pid 41 (mdmfs), uid 0: exited on signal 11
g_vfs_done():ufs/FreeNASs1a[READ(offset=275847811072, length=4096)]error = 5
vnode_pager_getpages: I/O read error
vm_fault: pager read error, pid 46 (mdmfs)
pid 46 (mdmfs), uid 0: exited on signal 11
g_vfs_done():ufs/FreeNASs1a[READ(offset=8723914231808, length=4096)]error = 5
WARNING: /data was not properly dismounted

I've noticed that there are no backups from the configuration stick. I'm sorry

All in all the Freenas isn't comming up.

What can i do?

Build a new Stick and than is it possible to restore the two mirrors of 4 discs on a new system or is the data lost?

Thank you in advanced for your help

Regards

4things
 
Status
Not open for further replies.
Top