HELP my RAID0 is down

[fozzy38]

Dear all,

I was getting back an old FreeNas server (0.7.2 Sabanda (revision 5543)) to migrate it to Nas4free, keeping data on it. I already have another Nas4free server for years.

The FreeNas server has 2 WD Caviar Green WD15EADS HDD 1.5 TB, originally setup as Raid 0.
When I power up the server I was able to access my data without trouble.

Then, I did something that break everything. As my W10 laptop crashed - motherboard I think - I plugged the laptop disk into the FreeNas server - so I add it to the current hardware setup, and I tried to boot.

Since then my Raid 0 is down, devices moved from ad4/ad6 to ad6/ad8, and I cannot succeed in accessing it again.

Even if this is a FreeNas (old version) topic, your help will be really appreciate, and I hope will give me the opportunity to move this server to Nas4free.

Below I put some command and logs output (NonSecurise is the Raid 0 name).
Is this normal than fdisk results are different? For ad6 I have sysid 238 (0xee),(EFI GPT), but for ad8: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)

Pleaseeee tell me that I can recover data :-/

Many thanks in advance for your help.
Cheers,
Fozzy38

From dmesg
ad6: 1430799MB <WDC WD15EADS-00P8B0 01.00A01> at ata3-master SATA300
ad8: 1430799MB <WDC WD15EADS-00P8B0 01.00A01> at ata4-master SATA300
acd0: DVDR <TSSTcorpCD/DVDW SH-S183A/SB03> at ata5-master SATA150
...
GEOM_STRIPE: Device NonSecurise created (id=2033048917).
GEOM_STRIPE: Disk ad8 attached to NonSecurise.

erablenas:~# diskinfo -v /dev/ad6
/dev/ad6
512 # sectorsize
1500301910016 # mediasize in bytes (1.4T)
2930277168 # mediasize in sectors
2907021 # Cylinders according to firmware.
16 # Heads according to firmware.
63 # Sectors according to firmware.
ad:WD-WMAVU0402199 # Disk ident.

erablenas:~# diskinfo -v /dev/ad8
/dev/ad8
512 # sectorsize
1500301910016 # mediasize in bytes (1.4T)
2930277168 # mediasize in sectors
2907021 # Cylinders according to firmware.
16 # Heads according to firmware.
63 # Sectors according to firmware.
ad:WD-WMAVU0889027 # Disk ident.

erablenas:~# ll /dev/ad*
crw-r----- 1 root operator 0, 72 Nov 8 13:44 /dev/ad6
crw-r----- 1 root operator 0, 73 Nov 8 13:44 /dev/ad6p1
crw-r----- 1 root operator 0, 74 Nov 8 13:44 /dev/ad8

erablenas:~# fdisk ad6
******* Working on device /dev/ad6 *******
parameters extracted from in-core disklabel are:
cylinders=2907021 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2907021 heads=16 sectors/track=63 (1008 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 4294967295 (2097151 Meg), flag 80 (active)
beg: cyl 0/ head 0/ sector 2;
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>

erablenas:~# fdisk ad8
******* Working on device /dev/ad8 *******
parameters extracted from in-core disklabel are:
cylinders=2907021 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2907021 heads=16 sectors/track=63 (1008 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 2930277105 (1430799 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 908/ head 15/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>

------------
Nas4Free 10.2.0.2 - Prester (revision 1814) embedded, Dell Optiplex 790, 8GB RAM, 3x2TB Sata HDD, ZFS Raidz1.
phpVirtualBox for OpenVPN, pyload, rutorrent, etc.
Raspberry Pi with OSMC

[daoyama]

First check current status by:
# gstripe status
# glabel status
# gpart show

[fozzy38]

Many thanks for your quick answer. Here are command output:

erablenas:~# gstripe status

erablenas:~# glabel status
Name Status Components
ufsid/4cd50a2c8b840dd2 N/A da0a

erablenas:~# gpart show
=> 34 2930277101 ad6 GPT (1.4T)
34 94 - free - (47K)
128 5860553984 1 freebsd-ufs (2.7T)

erablenas:~#

[fozzy38]

hello folks,

any idea?

[shakky4711]

Hello,

did you already remove the third harddisk? If no, please do it.
Then follow these instructions viewtopic.php?f=65&t=2890

Good luck!
Shakky



BTW: Two strange issues, Raid-0 is the absolute worst constellation for a NAS, one dying harddisk and all your data is lost, so double risk to loose date.
Second issue, WD-green are cheapest destop drives, the dy faster than all other harddisk types I have ever seen. So my strongest recommendation, replace the disks as soon as possible by WD-RED, these are made for NAS usage.

Always have a current backup from your data!

[fozzy38]

Hello,
sorry for my late answer, new job, so huge workload

Yes, I removed the 3rd HDD as soon as I saw the issue.
Now I will check the link.

Regarding your advice, that I already know of course. This NAS was mainly to store non critical files but also a short space with more critical ones. For these ones, I have a backup on an external HDD. But I would like to try to get back the non critical files also.

Thanks again!