First let me state that my FreeNAS server was assembled 2+ years ago and has been working great with no meddling on my part (also why I am still on the old version: FreeNAS 0.7.1 (Shere))
Regardless, my problem started a few days ago, and it basically indicated that the da2 drive had changed label to 15159316559305955361 (not sure why that happened, as it used to be dev/da2)
Then I spent quite some time reading various posts (and the FAQ here) and it seemed I had arrived at a solution on how to fix it, the last was to reformat the drive since it was still functional (so I did, using one of my Windows machines), and put the drive back in my server.
However, the steps definitely did not give me the expected result, and I am in quite a pickle as to what to do next. Please see the information readout from my pools/information listing
I can still access my server (thank goodness), but what should my next steps be? Given that I am on the older version of FreeNAS and using raidz2, I was hoping to wait to upgrade the OS until 8.3 came out... bad idea?
If I need to reformat the 2TB drive again, is there a simpler way than using my Windows machine (it took all night!)?
Thank you for your patience and also being as specific as possible with instructions to help.
EDIT1:
Note that I reformatted the drive using NTFS
And, on the normal disk/management readout, the drive shows as online:
EDIT2
I just noticed on the GUI that I can go into a Disks / Format section, which does show two drives available for formatting: da2 and da7... should I give that a go, since da2 in the zpool is faulted/unavailable anyway?
Regardless, my problem started a few days ago, and it basically indicated that the da2 drive had changed label to 15159316559305955361 (not sure why that happened, as it used to be dev/da2)
Then I spent quite some time reading various posts (and the FAQ here) and it seemed I had arrived at a solution on how to fix it, the last was to reformat the drive since it was still functional (so I did, using one of my Windows machines), and put the drive back in my server.
However, the steps definitely did not give me the expected result, and I am in quite a pickle as to what to do next. Please see the information readout from my pools/information listing
Code:
pool: tank state: DEGRADED scrub resilver completed with 0 errors on Tue Aug 14 10:56:33 2012 config: NAME STATE READ WRITE CKSUM tank DEGRADED 0 0 0 raidz2 DEGRADED 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 replacing UNAVAIL 0 0 0 insufficient replicas da2/old UNAVAIL 0 0 0 cannot open 15159316559305955361 FAULTED 0 0 0 was /dev/da2 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 da6 ONLINE 0 0 0 errors: No known data errors
I can still access my server (thank goodness), but what should my next steps be? Given that I am on the older version of FreeNAS and using raidz2, I was hoping to wait to upgrade the OS until 8.3 came out... bad idea?
If I need to reformat the 2TB drive again, is there a simpler way than using my Windows machine (it took all night!)?
Thank you for your patience and also being as specific as possible with instructions to help.
EDIT1:
Note that I reformatted the drive using NTFS
And, on the normal disk/management readout, the drive shows as online:
Code:
da0 1907730MB WDC WD2001FASS-00U0B R001 n/a 60 ZFS storage pool device ONLINE da1 1907730MB WDC WD2001FASS-00U0B R001 n/a 60 ZFS storage pool device ONLINE da2 1907730MB WDC WD2001FASS-00U0B R001 n/a 60 ZFS storage pool device ONLINE da3 1907730MB WDC WD2001FASS-00U0B R001 n/a 60 ZFS storage pool device ONLINE da4 1907730MB WDC WD2001FASS-00U0B R001 n/a 60 ZFS storage pool device ONLINE da5 1907730MB WDC WD2001FASS-00U0B R001 n/a 60 ZFS storage pool device ONLINE da6 1907730MB WDC WD2001FASS-00U0B R001 n/a 60 ZFS storage pool device ONLINE da7 1907730MB WDC WD2001FASS-00U0B R001 n/a 60 ZFS storage pool device ONLINE
EDIT2
I just noticed on the GUI that I can go into a Disks / Format section, which does show two drives available for formatting: da2 and da7... should I give that a go, since da2 in the zpool is faulted/unavailable anyway?