lazant

Can someone explain how I go about removing my 2nd parity disk before I start the mirroring process for upgrading file systems? Do I just unassign the parity 2 drive? Thanks.

I’m finally getting around to converting file systems on my ancient Atlas build from reiserfs to btrfs or xfs (haven’t decided yet). I currently have 12 disks in my array, 10x 3TB WD Greens and 2x 3TB Seagate Barracudas for parity. One of the data drives is having read errors so I’m going to replace it. I picked up 5x 6TB WD Red Pro’s the other day when Amazon was having a sale. My plan, eventually, is to replace the parity drives with these, add a cache drive and keep a couple precleared and ready to go in case of drive failures. Here’s the order I’m planning to do things in: 1. Replace parity drive 1 with new 6TB Red Pro 2. Unassign parity drive 2 3. Replace data drive having read errors with 6TB Red 4. Use mirroring method to upgrade array to new file system 5. Add 2nd parity back to array 6. Add cache drive Does this order make the most sense? I would also like to eventually convert to running unraid bare metal. As it stands I have it running as one of 4 VMs under esxi.

Ok that's what I figured. Just though I would ask. Thanks.

I have another question for you. During a rebuild, is it possible to convert the filesystem? All of my drives are still on ReiserFS and it would probably be a good idea to start converting. Or is it best to just do the mirroring method?

So the drive had another read error in a different slot on a different backplane. I guess that's good news because it's easy to replace the drive. Thanks again for all your help.

So everything went well with the rebuild, but as you anticipated, it is now a week later and it has happened again I think. I have the Norco 4224 case which has 4 drives per cable/backplane. I'm just wondering what my next step should be. Should I replace the backplane even though I'm not experiencing any issues with the other 3 drives on the backplane with disk 10? Replace the cable going to the backplane? Abandon that slot and put disk 10 in a different tray? Thanks for your help.

Thanks. Rebooted and you're correct, it's now sdn. Waiting for an extended SMART report now and then I'll rebuild.

I just recently upgraded from 5.04 to 6.7.0 and discovered one of my disk had 2 read errors. I then went to try to get a SMART report for the disk (sdh) but when I click the Spin Up button, nothing happens. It still says "Unavailable - disk must be spun up". Looking at the logs I see this: May 22 21:51:18 Asteria kernel: mdcmd (113): spinup 10 May 22 21:51:18 Asteria kernel: md: do_drive_cmd: lock_bdev error: -2 Any thoughts? Thanks in advance.