I assume then that this is normal (since Time Slider has been having fun making snapshots while the disks were in a degraded state)? Once the scan finishes it should be back online?
pool: data
state: DEGRADED
status: One or more devices could not be opened. Sufficient replicas exist...
So I am working on trying to get my backup server back up and running, but in the meantime I would like to prevent any additional data loss on my primary array. Now that we've ruled it a power issue, is there a way I can clear the ZFS checksum errors by forcing a resliver? I checked the drives...
If I could hug you I would. I completely removed the new pool and the entire original array came online. It's absolutely I overloaded the molex expander from Norco. Now I just need to figure out a way to power all 6 backplanes without the use of expanders. Or else, not chain all of them off...
All the drives are showing up on the LSI control utility, and it's a single rail 900-something watt PSU. However, it is running a Norco 1-8 molex expansion. I'll try re-wiring it with the first few rows using the straight PSU molex. Otherwise I'll have to track down another PSU.
Right now it's running using SFF-8087 cabling on 3 IBM M1015 controllers. What would be the best way to test the controllers since I don't have any in reserve and no real funds to buy more at this point?
Allright I'm stumped. I got all the rest of the disks online and then when I tried to start a zfs send to the new pool it crashed. When I rebooted, I found this:
I'm fairly sure I wouldn't go from 1 dead drive (unvail) to 5 dead drives.
What is the best way to mount this read-only and...
Ahh, I was thinking you were looking at 3TB drives - which I would suggest.
The 3TB version has a slightly lower price/GB (actually if my math is right the 3TB and 4TB match). If your controller supports the larger drives I would highly recommend going with a larger drive as you'll get much...
Having a SAS connector opens you up to better compatibility with advanced SAS technologies like SAS expanders - effectively allowing you to chain chassis together using SAS external cabling and connects 50+ disks to a single host. From what I've heard depending on what you get SATA drives can...
I thought about that but since my array is all 4k 3TB drives I figured there was probably no way to force just one. I'm re-arranging my pools when I get my next shipment of drives in so I can have the new pool be ashift=12. It was my noobie mistake not forcing it on the pool in the first place.
Yea, I found R-studio years ago when my data drive accidentally got wiped out, recovered it 100% and it sold me on the product. I can't tell you how many times I've recovered 100% of USB pendrives that decided to format themselves too.
Since it's a 3-way mirror, I'd say offline the drive (command line: zpool offline <pool> <device ID>), pull the drive, then go to Disks> Replace. So long as it doesn't report as a 4k drive you should be gold. If it gives you the error I got then you need to find another older model drive that...
^^This if your computer supports it.
OpenIndiana is SUCH a pita that I purely use it for storage. I connect about 3 Ubuntu-based VMs to it over Cifs (since I have heavy NTFS permissions to secure data and NFS was hosing those). It makes it so much easier. Just make sure your chipset...
Try scanning it with a recovery utility like R-Studio or GetDataBack.
I've had great success with R-Studio recovering everything short of a mechnically failed drive (including complete recovers off dying disks sitting in coolers with dry ice)
You sir are my hero. That was it! Odd that this is the first time I've had to do that, I think the others worked fine. I could be mistaken however.
BTW, From my research, there's no way to convert from ashift 9 to ashift 12 on a pool with data on it correct? The best I can do is move it to...
I seem to have run into a strange issue:
I ordered 6 new drives for adding a 3rd vdev and when the disks are in Napp-it seems to hang on the following:
errors: No known data errorsexe (get-desk.pl 28): parted -lm
I suspect a drive is DOA, but it seems that the drive that sits on the...