Frikkie274
Cadet
- Joined
- Oct 12, 2020
- Messages
- 1
Hi.
I am running a FreeNAS home-built nas at home. It has an i5 3200 and 16gb of ram, with an intel desktop board. For storage, I have a single 2tb disk for my main storage and a few other disks for my VMS and so forth. I recently acquired another 2tb disk from a friend. I installed it into my system and added it to my main storage volume in a stripe config. All disks are NTFS format.
I started noticing the other day that this new drive is spitting out read errors and then i/o errors and as a result later on my FreeNAS server crashed. I pulled the suspect drive out and rebooted the nas. now my main storage pool is missing and now I tried to connect the drive to my pc. In diskpart I do see my drive being picked up but no way to assign a drive letter to it or send the data of the drive to what's left of my nas.
Any suggestions on how I should go about this? Or should I just accept that my data is all gone?
I am running a FreeNAS home-built nas at home. It has an i5 3200 and 16gb of ram, with an intel desktop board. For storage, I have a single 2tb disk for my main storage and a few other disks for my VMS and so forth. I recently acquired another 2tb disk from a friend. I installed it into my system and added it to my main storage volume in a stripe config. All disks are NTFS format.
I started noticing the other day that this new drive is spitting out read errors and then i/o errors and as a result later on my FreeNAS server crashed. I pulled the suspect drive out and rebooted the nas. now my main storage pool is missing and now I tried to connect the drive to my pc. In diskpart I do see my drive being picked up but no way to assign a drive letter to it or send the data of the drive to what's left of my nas.
Any suggestions on how I should go about this? Or should I just accept that my data is all gone?