So, let me start from the beginning...
I'm running a Dell PowerEdge R720 with a PERC H710 RAID controller.
I'm using VMWare ESXi to host virutal machines, one of which is FreeNAS (11.2-U2.1).
I was attempting to remove a drive that did not belong to the FreeNAS VM...or so I thought. I accidentally removed one that had lots of important files on it, and, of course, this was a single RAID 0 drive (I know...not smart). I had copied the files temporarily to this drive as I was redoing the other drives (which of course have already been wiped) and I was going to copy them back to the RAID 1 disks.
Anyway, I put the drive back in the system and had to re-create the virtual disk (without initializing it so that it would not wipe out the data) as I have read on other forums that this should make the disk come right back. However, nothing seems to be showing up.
fdisk -l shows this for the drive through ESXi:
Disk /dev/disks/naa.6b8ca3a0efd589002465f0e0173b8395: 999.6 GB, 999653638144 bytes
255 heads, 63 sectors/track, 121534 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/disks/naa.6b8ca3a0efd589002465f0e0173b8395 doesn't contain a valid partition table
In FreeNAS I run gpart show and the drive (da2) does not show up. If I run gpart show /dev/da2 it says, "gpart: No such geom: /dev/da2."
If I run fdisk /dev/da2 I get:
******* Working on device /dev/da2 *******
parameters extracted from in-core disklabel are:
cylinders=121534 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=121534 heads=255 sectors/track=63 (16065 blks/cyl)
fdisk: invalid fdisk partition table found
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 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 1952443647 (953341 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 701/ head 254/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
When I originally added the drive to FreeNAS I had created an encrypted dataset, then within that a zvol that I used for iSCSI.
So...does the fact that it lists a partition 1 through fdisk mean everything is still there? Is there any way to fix the partition table and recover everything and re-import the volume? Please tell me there's a way!
If any further information is needed please let me know.
Thanks!
I'm running a Dell PowerEdge R720 with a PERC H710 RAID controller.
I'm using VMWare ESXi to host virutal machines, one of which is FreeNAS (11.2-U2.1).
I was attempting to remove a drive that did not belong to the FreeNAS VM...or so I thought. I accidentally removed one that had lots of important files on it, and, of course, this was a single RAID 0 drive (I know...not smart). I had copied the files temporarily to this drive as I was redoing the other drives (which of course have already been wiped) and I was going to copy them back to the RAID 1 disks.
Anyway, I put the drive back in the system and had to re-create the virtual disk (without initializing it so that it would not wipe out the data) as I have read on other forums that this should make the disk come right back. However, nothing seems to be showing up.
fdisk -l shows this for the drive through ESXi:
Disk /dev/disks/naa.6b8ca3a0efd589002465f0e0173b8395: 999.6 GB, 999653638144 bytes
255 heads, 63 sectors/track, 121534 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/disks/naa.6b8ca3a0efd589002465f0e0173b8395 doesn't contain a valid partition table
In FreeNAS I run gpart show and the drive (da2) does not show up. If I run gpart show /dev/da2 it says, "gpart: No such geom: /dev/da2."
If I run fdisk /dev/da2 I get:
******* Working on device /dev/da2 *******
parameters extracted from in-core disklabel are:
cylinders=121534 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=121534 heads=255 sectors/track=63 (16065 blks/cyl)
fdisk: invalid fdisk partition table found
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 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 1952443647 (953341 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 701/ head 254/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
When I originally added the drive to FreeNAS I had created an encrypted dataset, then within that a zvol that I used for iSCSI.
So...does the fact that it lists a partition 1 through fdisk mean everything is still there? Is there any way to fix the partition table and recover everything and re-import the volume? Please tell me there's a way!
If any further information is needed please let me know.
Thanks!