r3mus
Cadet
- Joined
- Feb 15, 2013
- Messages
- 4
Long story short, I've got a 12TB zpool (raid-z) that died when resilvering from a disk failure. Cause isn't important, only the fact that the data appears to still be intact.
Using zpool import -R /mnt/tank -o readonly=on rz0 I was able to successfully mount the "rz0" zpool in /mnt/tank. Once that worked, I can now browse into that directory and see "ex0", my iSCSI file extent, sitting there. If I run file ex0 I get this:
[root@freenas] /mnt/tank/rz0# file ex0
ex0: x86 boot sector; partition 1: ID=0xee, starthead 0, startsector 1, 4294967295 sectors, code offset 0xc0, OEM-ID " \320\274", Bytes/sector 190, sectors/cluster 124, reserved sectors 191, FATs 6, root entries 185, sectors 64514 (volumes <=32 MB) , Media descriptor 0xf3, sectors/FAT 20644, heads 6, hidden sectors 309755, sectors 2147991229 (volumes > 32 MB) , physical drive 0x7e, dos < 4.0 BootSector (0x0)
So it appears that the data is at least partially intact.
Problem:
I can't mount that file extent through the web GUI, and there doesn't seem to be any way to force it to mount. When trying to do it through the GUI, I'm getting this error: Your path to the extent must reside inside a volume/dataset mount point; all the information on the web points to how to create a new extent, but not mount an existing one that doesn't show up.
Solutions:
I need to A) find a way to mount this extent within FreeNAS, or B) (preferably) find a way to re-establish the iSCSI extent and target so I can transfer directly off the underlying partition (it's Windows NTFS).
Using zpool import -R /mnt/tank -o readonly=on rz0 I was able to successfully mount the "rz0" zpool in /mnt/tank. Once that worked, I can now browse into that directory and see "ex0", my iSCSI file extent, sitting there. If I run file ex0 I get this:
[root@freenas] /mnt/tank/rz0# file ex0
ex0: x86 boot sector; partition 1: ID=0xee, starthead 0, startsector 1, 4294967295 sectors, code offset 0xc0, OEM-ID " \320\274", Bytes/sector 190, sectors/cluster 124, reserved sectors 191, FATs 6, root entries 185, sectors 64514 (volumes <=32 MB) , Media descriptor 0xf3, sectors/FAT 20644, heads 6, hidden sectors 309755, sectors 2147991229 (volumes > 32 MB) , physical drive 0x7e, dos < 4.0 BootSector (0x0)
So it appears that the data is at least partially intact.
Problem:
I can't mount that file extent through the web GUI, and there doesn't seem to be any way to force it to mount. When trying to do it through the GUI, I'm getting this error: Your path to the extent must reside inside a volume/dataset mount point; all the information on the web points to how to create a new extent, but not mount an existing one that doesn't show up.
Solutions:
I need to A) find a way to mount this extent within FreeNAS, or B) (preferably) find a way to re-establish the iSCSI extent and target so I can transfer directly off the underlying partition (it's Windows NTFS).