February 25, 201115 yr Working on a 4.6 box now. I have: ST32000542AS_5XW2A0Y2 [parity (sda)]; WDC_WD3200AAJB-00J3A0_WD-WCAV2F345825 [disk1(hda)]; Maxtor_5A300J0_A8247TEE [disk2] (hdb) Can't get any smart info with the Maxtor on the MAIN Page but it is working right now. Disk /dev/hda: 320.0 GB, 320072933376 bytes 1 heads, 63 sectors/track, 9922896 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/hda1 63 625142447 312571192+ 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# fdisk -lu /dev/hdb Disk /dev/hdb: 300.0 GB, 300000739328 bytes 1 heads, 63 sectors/track, 9300618 cylinders, total 585938944 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/hdb1 63 585938943 292969440+ 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# fdisk -lu /dev/sda Disk /dev/sda: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 63 3907029167 1953514552+ 83 Linux Partition 1 does not end on cylinder boundary. (Still syncing) I did not run the pre-clear. (There are no jumpers on sda) I assigned the devices, started the array, then formatted. I did this with my 4.7 box as well. This is why I got the errors with my first build showing on the main page. After I ran the sync again on the 4.7 box the errors went to 0. I suspect I can do the same with this 4.6 box. I take it the correct way would have been to pre-clear then do the assignment, array, formatting. Is this an issue? Should I start over? Am I losing a lot with starting on sector 63? What do I do with the Maxtor that does not show smart when I boot (I see no smart on boot screen as well)? Will I benefit with a swap drive? Is it good practice to copy flash to another flash and/or unmenu folder?
February 25, 201115 yr This link has a discussion on pre-clear: http://lime-technology.com/forum/index.php?topic=11263.0 4K alignment, starting at 64 allows optimal performance for advanced format drives. Non-AF drives gain no benefit or harm but using 4K alignment for all new drives is recommended for simplicities sake. 4K aligned will soon be the default for unRAID. Existing non-AF drives should be left as is. Existing AF drives can be left as is if your happy with performance. EARS drives are a special case. EARS drives with a jumper should be treated as non-AF. EARS drives without a jumper should be treated as AF. Do not add a jumper to a new EARS drive if used under version 4.7+.
Archived
This topic is now archived and is closed to further replies.