September 13, 201015 yr Just noticed that my parity drive is not connected directly to the mobo which should give the most bandwidth, so I thought about swapping it out with a data drive's slot. Any suggestions how to accomplish this best? Parity is valid and everything else is working correctly. Possible to just manually reassign drives (even on the cmd line) and leave data including parity intact after stoping/reassigning/starting the volume?
September 13, 201015 yr Just noticed that my parity drive is not connected directly to the mobo which should give the most bandwidth, so I thought about swapping it out with a data drive's slot. Any suggestions how to accomplish this best? Parity is valid and everything else is working correctly. Possible to just manually reassign drives (even on the cmd line) and leave data including parity intact after stoping/reassigning/starting the volume? Stop the array, power down, switch cables, power up Go to the devices page, swap assignments Back on the main page, press "Start" That should do it. Joe L.
September 13, 201015 yr Author Could I just do by swapping the hotplug drive carriers without swapping cables in the case - will be basically the same?!
September 13, 201015 yr Could I just do by swapping the hotplug drive carriers without swapping cables in the case - will be basically the same?! I think it will. do it with the power off as unRAID is NOT a hot-swap OS.
September 13, 201015 yr How can I prevent the array from auto-starting after re-boot? if it does recognize the correct disks in the correct slots it will not start.
September 13, 201015 yr comment out the "emhttp" line in your go file. If you do this, you'll not be able to use the "Devices" page to re-assign the drives to their proper slots.
September 13, 201015 yr Ah true... Fortunately there should be a troubleshooting mode in the 5.0 series to do exactly this.
September 13, 201015 yr Author Hit a bug and the kernel panic'ed. Needed to reboot, parity check auto started. Canceled. Powered down. Swaped out drives. Powered on, re-assigned slots, started array without problems. It now shows parity to be valid and all excellent. However, will start a verification. Shouldn't a canceled parity check be marked as non valid?! However I don't see any performance improvements after attaching parity drive to mobo onboard SATA channel.
September 14, 201015 yr Author What is this message exactly? sdj is a reiserfs formatted USB stick. Message from syslogd@tower at Tue Sep 14 09:06:46 2010 ... tower kernel: Stack: Message from syslogd@tower at Tue Sep 14 09:06:46 2010 ... tower kernel: Code: 55 f0 e8 6a 92 a4 c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 ac 2d 6f f8 c1 e9 02 89 38 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89 Message from syslogd@tower at Tue Sep 14 09:06:46 2010 ... tower kernel: EIP: [<f86ed8e4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c465fef4 Message from syslogd@tower at Tue Sep 14 09:06:46 2010 ... tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host17/target17:0:0/17:0:0:0/block/sdj/removable Message from syslogd@tower at Tue Sep 14 09:06:46 2010 ... tower kernel: Call Trace: Message from syslogd@tower at Tue Sep 14 09:06:46 2010 ... tower kernel: CR2: 00000000f86f7000 Message from syslogd@tower at Tue Sep 14 09:06:46 2010 ... tower kernel: Process emhttp (pid: 2892, ti=c465e000 task=c46e1b80 task.ti=c465e000) Message from syslogd@tower at Tue Sep 14 09:06:46 2010 ... tower kernel: Oops: 0000 [#1] SMP
Archived
This topic is now archived and is closed to further replies.