February 10, 201412 yr I'm looking to add a second Norco SS-500 to my unRaid box. In doing so, I will be moving the parity drive from a single hot-swap bay into the one of the Norcos. In doing so, I will be swapping out the fan on my existing Norco, cleaning up the cable management, and generally be mucking about in the case and most likely removing all but the MoBo in the process. My question is probably a no-brainer that I missed when doing a preliminary search on these threads, but here it is: [*]When moving a drive(s) from one bay to another, will parity be an issue if I use the same SATA connection on the MoBo and just move it to the new enclosure?
February 10, 201412 yr No. unRAID assigns hard drives to SATA ports at boot. Shouldn't matter. You can mix up the SATA ports all you like. Just make sure that if you start with 7 drives connected by SATA, you reconnect 7 before you fire up unRAID. *IF* you clean everything up, AND you boot up unRAID AND you don't see all the drives you started with, THEN you have a problem. (something in the cabling or the BIOS or power isn't connected.) A couple of preventive measures (just in case) come to mind: 1. Save to your PC a screenshot of your webgui showing the serial numbers of your drives. In particular, if something goes wrong, you want to be sure that you reassign parity and cache drives correctly. 2. Make sure parity is correct before you clean up! 3. I'd run a set of SMART reports and Reiserfsck just to be sure. 4. DON'T tie your SATA cables together, unless they are shielded. (and the odds are 99 to 1 that they are NOT shielded:) SATA cables next to each other act have crosstalk.
February 11, 201412 yr Author Thanks for the info! I already have a spreadsheet tracking the drive info and mapping, so good to go there. I was not aware of the cross-talk potential with SATA cables, so that is seriously beneficial for my re-wiring.
February 11, 201412 yr Author Careful this DID matter in 4.7. How so? I am running 4.7 so can you point me to some documentation for this process?
February 11, 201412 yr Careful this DID matter in 4.7. OH! Sorry.. I missed the version 4.7 in your signature.
February 11, 201412 yr Careful this DID matter in 4.7. I thought that was only the case if you changed the ports that drives were plugged into? In this case where it simply putting the drives into NorCo mountings but keeping the ports constant does it matter? Having said hat I think it will be essential to have a screenshot of the disk assignments before the change to check you have not made any mistakes.
February 11, 201412 yr Drive assignments in Linux do not remain consistent between boots. I would get this all the time on my X7SBE MB with AOC-SAT2-MV8 cards and unRAID 4.6 because 4.6 used the drive letters to determine the slots the drives were assigned to. So about every 5th boot I would have drives show up as missing and/or their slots were switched. It was simple to fix since unRAID showed you what it was expecting but I quite often had 10 drives to rearrange in the gui on that 5th boot.
February 11, 201412 yr Careful this DID matter in 4.7. How so? I am running 4.7 so can you point me to some documentation for this process? As posted BobPhoenix drive assignments can change. Likely moving cables and slots wont matter but personally I would move to V5 which specifically doesnt care even if the drive letters change. If you cant or wont change take screenshots before and then worst case you can reassign.
February 11, 201412 yr 4.7 uses the physical SATA port to track disks and 5 uses the disk serial numbers. The device identifiers, i.e., sda, sdb, etc. are ephemeral and have never been used to track disks. They are inconsequential to any version of unRAID and there is never a reason the rearrange disks due to changing device identifiers unless poorly written scripts are added to the system. In any case, the order of the data disks is not important. Only the parity and cache drives need to be reassigned correctly.
Archived
This topic is now archived and is closed to further replies.