Can't import disk or volume .... fsck_ufs /dev/da0 Cannot find file system superblock

Status
Not open for further replies.

bartek

Dabbler
Joined
Apr 3, 2017
Messages
11
Good evening any help very much appreciated.
I admit I am very new to FreeNas/FreeBSD and come from the linux world.
for four days I am googleling for a solution but all I find is to dd with zeros my drive that I can't import, what would delete all of the data remaining on the disk.
There was a power outage and the 8.3 server is no more. I have one SSD disk as a survivor.

I did set up a new server with 8.3 but didn't manage to import, now I did a new installation of 9.10 but with the same results.

I know my chances are low of getting my hands on the data remaining on the disk but it has some value to me, and so am asking kindly for your help.

While trying to import the disk I get the famous "The selected disks were not verified for these import rules. Filesystem check failed."

when I do

fsck_ufs /dev/da0
** /dev/da0
Cannot find file system superblock
ioctl (GCINFO): Inappropriate ioctl for device
fsck_ufs: /dev/da0: can't read disk label


zpool import returns nothing

I can manually mount da0 but ls -la returns "empty"

my dmesg output:

ugen0.7: <TOSHIBA> at usbus0
umass1: <TOSHIBA External USB 3.0, class 0/0, rev 2.10/1.07, addr 7> on usbus0
umass1: SCSI over Bulk-Only; quirks = 0x0100
umass1:4:1:-1: Attached to scbus4
(probe0:umass-sim1:1:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00
(probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error
(probe0:umass-sim1:1:0:0): SCSI status: Check Condition
(probe0:umass-sim1:1:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
(probe0:umass-sim1:1:0:0): Error 22, Unretryable error
da0 at umass-sim1 bus 1 scbus4 target 0 lun 0
da0: <TOSHIBA External USB 3.0 5438> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number 20150131031421
da0: 40.000MB/s transfers
da0: 953869MB (1953525164 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
GEOM: da0: the secondary GPT header is not in the last LBA.
GEOM_PART: integrity check failed (da0, GPT)


whend I do a fdisk /dev/da0


fdisk /dev/da0
******* Working on device /dev/da0 *******
parameters extracted from in-core disklabel are:
cylinders=121601 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=121601 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 238 (0xee),(EFI GPT)
start 1, size 1952972799 (953599 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 255/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>


bsdlabel returns no valid label found, I guess that is obvious by now.

fsdb is as much as dmesg

fsdb /dev/da0
** /dev/da0
Cannot find file system superblock
ioctl (GCINFO): Inappropriate ioctl for device
fsdb: /dev/da0: can't read disk label



camcontrol devlist
<ST1000DM003-1CH162 CC47> at scbus0 target 0 lun 0 (pass0,ada0)
<WDC WD10PURX-64E5EY0 01.01A01> at scbus1 target 0 lun 0 (pass1,ada1)
<TOSHIBA External USB 3.0 5438> at scbus4 target 0 lun 0 (da0,pass3)


I wonder why gpart is not showing da0

gpart show
=> 34 1953525101 ada0 GPT (932G)
34 6 - free - (3.0K)
40 1024 1 bios-boot (512K)
1064 1953524064 2 freebsd-zfs (932G)
1953525128 7 - free - (3.5K)

=> 34 1953525101 ada1 GPT (932G)
34 94 - free - (47K)
128 4194304 1 freebsd-swap (2.0G)
4194432 1949330696 2 freebsd-zfs (930G)
1953525128 7 - free - (3.5K)


debugfs gives me:


debugfs
debugfs 1.43.3 (04-Sep-2016)
debugfs: open /dev/da0
/dev/da0: Bad magic number in super-block while opening filesystem


since I don't understand yet what debugfs is capable of I kindly ask if this is the right direction to go...



I know my chances are low of getting my hands on the data remaining on the disk but it has some value to me, and so am asking kindly for your help.
 
D

dlavigne

Guest
It looks like the data is on a ZFS pool, which would explain why fsck_ufs is confused. Post the output of zpool status within code tags.
 

bartek

Dabbler
Joined
Apr 3, 2017
Messages
11
Code:
zpool status																									 
  pool: data																														
state: ONLINE																													 
  scan: none requested																											 
config:																															 
																																	
		NAME										  STATE	 READ WRITE CKSUM													
		data										  ONLINE	   0	 0	 0													
		  gptid/e0c43a4c-18b6-11e7-be85-fcaa149c651e  ONLINE	   0	 0	 0													
																																	
errors: No known data errors																										
																																	
  pool: freenas-boot																												
state: ONLINE																													 
  scan: none requested																											 
config:																															 
																																	
		NAME		STATE	 READ WRITE CKSUM																					 
		freenas-boot  ONLINE	   0	 0	 0																					
		  ada1p2	ONLINE	   0	 0	 0																					 
																																	
errors: No known data errors		
 
D

dlavigne

Guest
Looks like the ZFS pool imported and is online. How are you trying to access the data?
 

bartek

Dabbler
Joined
Apr 3, 2017
Messages
11
Looks like the ZFS pool imported and is online. How are you trying to access the data?

its not the same pool the one you see is a brand new and empty one, i read in the manual that you can save/backup data to a new place when importing a disk, that is what i was trying to do.
 

bartek

Dabbler
Joined
Apr 3, 2017
Messages
11
upload_2017-4-4_17-52-40.png


upload_2017-4-4_17-53-16.png
 

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
Looks like you need to pursue a UFS RAID recovery strategy, not a FreeNAS ZFS pool recovery strategy. What was your pool layout in 8.3? Current versions do not support UFS RAID.
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Please stop doing random things to any data you wish to save.

This is not any new stuff you have created, which of course does not matter right now.

Which disk is the old data on? Looking for a brand and model of disk, or multiple disks. How are they connected to the computer?
 

bartek

Dabbler
Joined
Apr 3, 2017
Messages
11
Please stop doing random things to any data you wish to save.

This is not any new stuff you have created, which of course does not matter right now.

Which disk is the old data on? Looking for a brand and model of disk, or multiple disks. How are they connected to the computer?

I am trying to avoid ruining my data for sure, I did clone the hard drive first and am "experimenting" with the clone.
The original data is on a SSD drive, as said before I did clone it and the clone is connected via usb 3.0 (its a closed case, that's why it's on a USB port) to a new machine running 9.10.2-U2 (e1497f2).
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Okay, on that machine, please show the output of gpart show da0. Please put it in code tags to preserve the spacing.
 

bartek

Dabbler
Joined
Apr 3, 2017
Messages
11
I was wondering why gpart is not showing da0, because when I use the import disk option in gui da0 shows up.
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
gpart looks for a partition table. If there isn't one, it will give that error.

What method did you use to "clone" the original SSD?

From the FreeNAS shell, please run file -s /dev/da0.
 

bartek

Dabbler
Joined
Apr 3, 2017
Messages
11
I used dd on linux to clone the disk.

Code:
file -s /dev/da0																								 
/dev/da0: DOS/MBR boot sector; partition 1 : ID=0xee, active, start-CHS (0x0,1,1), end-CHS (0x3ff,255,63), startsector 1, 1952972799
sectors
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
That is the start of a GPT partition table. If just one of the two GPT partition tables was okay, gpart would have been able to show it. But apparently it is not.

Please show the exact dd command you used. I suspect that disk is not an accurate copy of the original.
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Man, that must have taken forever. I suggest copying it again, but with a 1M buffer size (bs=) so it doesn't take hours, and possibly a noconv parameter to skip over errors. I have to leave now, but will check back later and can come up with more specifics.
 

bartek

Dabbler
Joined
Apr 3, 2017
Messages
11
Yeah it took a night but since I had the time I let dd do its job calmly. Sure I'll clone it again. Thank you for your help.
 
Status
Not open for further replies.
Top