Carabolic

Members
  • Posts

    26
  • Joined

  • Last visited

Everything posted by Carabolic

  1. Just upgraded from UnRAID v4.7 to v5.0.4 and so far had positive experience with this modified sleep script, which I used in v4.7: #!/bin/bash # Table of all possible drives when all drive slots are fully populated, with usb boot flash "/dev/sda" excluded drives="/dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sdl /dev/sdm /dev/sdn /dev/sdo" # Timeout in minutes timeout=60 count=$timeout while [ 1 ] do hdparm -C $drives | grep -q active if [ $? -eq 1 ] then count=$[$count-1] else count=$timeout fi if [ $count -le 0 ] then # Do pre-sleep activities sleep 5 # Flush hdd filebuffers sync # Go to sleep echo -n mem > /sys/power/state # Do post-sleep activities # Flush hdd filebuffers sync # Force NIC into gigabit mode # (might be needed forgets about gigabit when it wakes up) ethtool -s eth0 speed 1000 # Force a DHCP renewal (shouldn't be used for static-ip boxes) #/sbin/dhcpcd -n sleep 5 count=$timeout fi # Wait a minute echo COUNT $count sleep 60 done
  2. There is no such think as a 512b or 4k drive (not yet anyways). The setting just changes the location of the disk partition. Every drive presently available will work fine using the 4k-aligned setting except a WD EARS drive with the alignment jumper. Thanks for the reply, lionelhutz! Cheers!
  3. No, you do not "need" to run the pre-clear script on the new drive, but since 1 out of 5 drives seems to fail the preclear tests lately, all I can ask is "do you feel lucky?" If you would rather not trust your luck, I would suggest that before you assign the new drive to your array that you put it through at least one preclear cycle. You are mixing two different concepts. To replace a parity drive you just remove the old drive, plug the new drive onto the same cable, and start the array. Parity will be calculated and stored on the parity disk. once it is complete you should then perform a parity check to be certain it can be read. Regards, Peter Ok, Thanks Joe! Every thing's running fine now! One last question... As I've changed the filesystem setting to 4K sectors, will there be any problems when I attach a new 512k drive (my former parity drive) after I've removed any partitions on it and attached it as a file drive into the array? Will unRaid try to use it as a 4K or a 512K drive after I've changed the default setting to 4K? //Peter
  4. Two Questions for Joe.L: My unRaid server consist of several 1.5TB drives. As I need to expand the storage capacity, I'm planning to buy and insert a 2TB drive as the Parity drive and shifting that old 1.5 TB drive as a new storage drive. This will give me a 2TB 4k drive on the parity and 1.5 TB 512k drives for the actual storage. (my plan is to shift down the old 1.5 TB drives further as I will replace the top ones by time with 2TB ones. 1. When inserting the 2TB drive as parity, do I need to run the pre-clear script before creating the new parity data? 2. I think I read a couple of years ago that I could insert an empty parity drive and attach the old parity drive in the system and have the old parity data to be transfered to the new disk. Is this correct? Regards, Peter