Slydogsz
Dabbler
- Joined
- May 7, 2016
- Messages
- 18
I just want to say up front that any assistance is appreciated. I know everyone is volunteering their time to provide people help. Thanks for what you do, support is not always appreciated.
Thanks for your help in advance.
I admit it, I did not configure my FreeNas correctly. I ran it on older hardware, with not enough memory and no ECC memory. I didn't do a lot of things that I should of, I get that and hope to of corrected what I can.
What that doesn't change is that I have a down FreeNas. Mission critical, no but I do believe my data is still there and dont want to give up on it unless I am told it is gone. I see nothing that indicates any of the drives are bad. What I lack is the knowledge and skills to get access to the data.
Here are some details that I hope someone will be able to point me in the right direction to recover the data or tell me my drives are done for. I can accept that the data is gone but I have not seen anything that indicates there was a hardware failure. My ID10T issues are a given.
Image of crash http://imgur.com/e375vbH
camcontrol devlist http://pastebin.com/AYAj4eZ1
smartctl -x /dev/da0 http://pastebin.com/ibN9aDUR
smartctl -x /dev/da1 http://pastebin.com/ZMKRd6tK
smartctl -x /dev/da2 http://pastebin.com/5wWTjT3k
smartctl -x /dev/da3 http://pastebin.com/s4JKiB31
sysctl -a | grep mps http://pastebin.com/94bt9WgJ
sas2flash -list http://pastebin.com/LHbD4dUt
This was a 4 drive ZFS1 array with a OCZ SSD drive as cache. I have learned that the cache was a bad idea.
The array was then presented as an ISCSI Lun to a ESXi cluster which then formatted the lun as a large 7tb VMFS5 volume. More bad practices I have been told. All of this was running on a Core 2 Duo system that I had laying around with 4gb of ram. Yes I know, it should of been 8gb and ECC. Probably a under-powered CPU as well.
This system worked great for over a year, then one night I was streaming a move from my virtualized media server when the movie just stopped, I went to look at my ESXi cluster and found the crash on the FreeNas screen.
After getting chastised for not having the right hardware, I have upgraded the server to a dual quad core Xeon dell server with 16gb of ECC ram and a Dell H200 SATA/SAS controller that has been flashed to IT mode.
I removed the Volume from the config and can now boot into the FreeNas console with no issues but I cant get the Volume to Import. When I try I get lots of text scrolling by and then the server reboots. No crash logs are in /var/crash and /var/messages just show the boot messages but nothing about why the import fails.
So outside of the given "You are dumb for building your NAS this way" post that I do deserve, is there anything outside of taking this server to a data recovery specialist that I can do to get to the data or should I just give up and start over ?
Thanks for your help in advance.
I admit it, I did not configure my FreeNas correctly. I ran it on older hardware, with not enough memory and no ECC memory. I didn't do a lot of things that I should of, I get that and hope to of corrected what I can.
What that doesn't change is that I have a down FreeNas. Mission critical, no but I do believe my data is still there and dont want to give up on it unless I am told it is gone. I see nothing that indicates any of the drives are bad. What I lack is the knowledge and skills to get access to the data.
Here are some details that I hope someone will be able to point me in the right direction to recover the data or tell me my drives are done for. I can accept that the data is gone but I have not seen anything that indicates there was a hardware failure. My ID10T issues are a given.
Image of crash http://imgur.com/e375vbH
camcontrol devlist http://pastebin.com/AYAj4eZ1
smartctl -x /dev/da0 http://pastebin.com/ibN9aDUR
smartctl -x /dev/da1 http://pastebin.com/ZMKRd6tK
smartctl -x /dev/da2 http://pastebin.com/5wWTjT3k
smartctl -x /dev/da3 http://pastebin.com/s4JKiB31
sysctl -a | grep mps http://pastebin.com/94bt9WgJ
sas2flash -list http://pastebin.com/LHbD4dUt
This was a 4 drive ZFS1 array with a OCZ SSD drive as cache. I have learned that the cache was a bad idea.
The array was then presented as an ISCSI Lun to a ESXi cluster which then formatted the lun as a large 7tb VMFS5 volume. More bad practices I have been told. All of this was running on a Core 2 Duo system that I had laying around with 4gb of ram. Yes I know, it should of been 8gb and ECC. Probably a under-powered CPU as well.
This system worked great for over a year, then one night I was streaming a move from my virtualized media server when the movie just stopped, I went to look at my ESXi cluster and found the crash on the FreeNas screen.
After getting chastised for not having the right hardware, I have upgraded the server to a dual quad core Xeon dell server with 16gb of ECC ram and a Dell H200 SATA/SAS controller that has been flashed to IT mode.
I removed the Volume from the config and can now boot into the FreeNas console with no issues but I cant get the Volume to Import. When I try I get lots of text scrolling by and then the server reboots. No crash logs are in /var/crash and /var/messages just show the boot messages but nothing about why the import fails.
So outside of the given "You are dumb for building your NAS this way" post that I do deserve, is there anything outside of taking this server to a data recovery specialist that I can do to get to the data or should I just give up and start over ?