downloadski

there is a animated picture on this page that gives me an idea: http://finalcutprox.net/how-to-add-24tb-of-storage-to-a-mac-pro 2 5,25 bays with a x-swing with 2 normal height hdd's in there. In the top bay there will not fit another one with 2 drives

I can get them for 6 euro, so it is not a big investment. I now use 5 in 3 units from norco (attach sliders to hdd, slide in) like 12 Euro each, but they are not really locked in well. Cooling i would fix with 120 mm fans in front of it from top to bottum.

I was thinking of using on top of each other. 12 bay case, but if i can only place1 hdd per 5,25 bay, it is not of much use. If i could place 4 discs in 3 positions, i can hold 16' which is almost enough. Might order 2 sets to try out

Question on that double twin mounting. I assume it take more room than 1 5,25 bay height when 2 hdd are fitted. Can someone tell me how high this is (in mm preferably) Thansk..

Want to bring this question up. If i do a ps, i see no mover process that i can kill. My system decided today to do moving at 500 KByte/sec, so this takes days. I had issues enough with the discs it moves to, to reboot the server. Pressing the stop array did not work. Any oppinions ? edit: returning after dinner and no webgui, no telnet, but console still works samba was stopped finally no more mounted discs. did umount for every disk, (umount /dev/md1 .. were not mounted anymore) did /root/mdcmd stop shutdown -h now does not get the server dwon: stopping system message bus unmounting remote filesystems /etc/rc.d/rc.apid: line 15: kill: (1385) INIT: no more processes left in this runlevel and than a flashing cursor, and no more action.

The sound level the Seasonics produce is very low indeed. Have them in 2 PC's (14 and 17 hdd's)

Other sata data cable, other power cable, same drive, same errors at 65% Other drive of same type continues with pre-clear. So drive issue i assum, will put it aside

Thx, i will do that once i get back home today after work. The SDI drive was continuing just fine it seems, so i guess i will have the 3 preclear files of that one. The drives are on one power cable with 4 sata connectors (2 used) - original cable that came with the Power supply (monster realpower M1000) No splitters there. The Sata cable is a SFf-8087 splitted to 4 sata data connectors. The 2nd preclair on this SDH drive i did on a other sata data connector on which i pre-cleared a disk fine. Is there a reason to suspect the quality of these SFF-8087 breakout cables ? http://cybershop.ri-vier.nl/discrete-sff8087-to-4x-sata-mini-sas-forward-brkout-cable-l50-p-103.html edit: they look a lot like these: mono price for $9.63 (payed like 20 euro) I had massive issues on my Areca also, if these things could be caused by the cables i would be wise to buy other ones to test perhaps. edit: (8-8-2012) the 3rd go failed as well. According to seagate i still have warrantee on this disk, so i will go for a swap of the hdd. Will get a seagate back it seems, do not know if i am very happy with that..

Can someone tell me what these errors mean during a preclear:" Aug 5 18:24:21 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1952:Release slot [3] tag[3], task [d6eaf900]: Aug 5 18:24:21 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 626:command active 0000000F, slot [3]. Aug 5 18:24:21 Tower kernel: sas: sas_ata_task_done: SAS error 8a Aug 5 18:24:21 Tower kernel: sd 0:0:0:0: [sdh] command f2f76480 timed out Aug 5 18:24:21 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1952:Release slot [1] tag[1], task [d6eaf2c0]: Aug 5 18:24:21 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 626:command active 00000007, slot [1]. Aug 5 18:24:21 Tower kernel: sas: sas_ata_task_done: SAS error 8a Aug 5 18:24:21 Tower kernel: sd 0:0:0:0: [sdh] command f2f760c0 timed out Aug 5 18:24:51 Tower kernel: sd 0:0:1:0: [sdi] command f2d75780 timed out Aug 5 18:24:51 Tower kernel: sd 0:0:1:0: [sdi] command f2e5c240 timed out Aug 5 18:24:51 Tower kernel: sas: Enter sas_scsi_recover_host busy: 4 failed: 4 Aug 5 18:24:51 Tower kernel: sas: trying to find task 0xd4febb80 Aug 5 18:24:51 Tower kernel: sas: sas_scsi_find_task: aborting task 0xd4febb80 Aug 5 18:24:51 Tower kernel: sas: sas_scsi_find_task: task 0xd4febb80 is aborted Aug 5 18:24:51 Tower kernel: sas: sas_eh_handle_sas_errors: task 0xd4febb80 is aborted Aug 5 18:24:51 Tower kernel: sas: trying to find task 0xde7f5680 Aug 5 18:24:51 Tower kernel: sas: sas_scsi_find_task: aborting task 0xde7f5680 Aug 5 18:24:51 Tower kernel: sas: sas_scsi_find_task: task 0xde7f5680 is aborted Aug 5 18:24:51 Tower kernel: sas: sas_eh_handle_sas_errors: task 0xde7f5680 is aborted Aug 5 18:24:51 Tower kernel: sas: ata7: end_device-0:0: cmd error handler Aug 5 18:24:51 Tower kernel: sas: ata8: end_device-0:1: cmd error handler Aug 5 18:24:51 Tower kernel: sas: ata7: end_device-0:0: dev error handler Aug 5 18:24:51 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 626:command active 00000004, slot [0]. Aug 5 18:24:51 Tower kernel: sas: ata8: end_device-0:1: dev error handler Aug 5 18:24:51 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen Aug 5 18:24:51 Tower kernel: ata8.00: failed command: READ FPDMA QUEUED Aug 5 18:24:51 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 Aug 5 18:24:51 Tower kernel: ata8.00: cmd 60/00:00:40:16:ef/01:00:6f:00:00/40 tag 0 ncq 131072 in Aug 5 18:24:51 Tower kernel: res 40/00:04:78:78:d7/00:00:6f:00:00/40 Emask 0x4 (timeout) Aug 5 18:24:51 Tower kernel: ata7.00: failed command: READ FPDMA QUEUED Aug 5 18:24:51 Tower kernel: ata7.00: cmd 60/00:00:30:8d:8e/01:00:72:00:00/40 tag 0 ncq 131072 in Aug 5 18:24:51 Tower kernel: res ff/3f:3f:37:c8:10/00:00:56:88:2a/00 Emask 0x403 (HSM violation) <F> Aug 5 18:24:51 Tower kernel: ata7.00: status: { Busy } Aug 5 18:24:51 Tower kernel: ata7.00: error: { IDNF ABRT } Aug 5 18:24:51 Tower kernel: ata8.00: status: { DRDY } Aug 5 18:24:51 Tower kernel: ata7.00: failed command: READ FPDMA QUEUED Aug 5 18:24:51 Tower kernel: ata7.00: cmd 60/00:00:30:8e:8e/01:00:72:00:00/40 tag 1 ncq 131072 in Aug 5 18:24:51 Tower kernel: res 01/04:04:30:8d:8e/00:00:72:00:00/40 Emask 0x2 (HSM violation) Aug 5 18:24:51 Tower kernel: ata7.00: status: { ERR } Aug 5 18:24:51 Tower kernel: ata7.00: error: { ABRT } Aug 5 18:24:51 Tower kernel: ata8.00: failed command: READ FPDMA QUEUED Aug 5 18:24:51 Tower kernel: ata8.00: cmd 60/00:00:40:17:ef/01:00:6f:00:00/40 tag 1 ncq 131072 in Aug 5 18:24:51 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 5 18:24:51 Tower kernel: ata7: hard resetting link Aug 5 18:24:51 Tower kernel: ata8.00: status: { DRDY } Aug 5 18:24:51 Tower kernel: ata8: hard resetting link Aug 5 18:24:51 Tower kernel: sas: sas_form_port: phy3 belongs to port1 already(1)! Aug 5 18:24:51 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 626:command active 00000004, slot [0]. Aug 5 18:24:51 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 626:command active 00000004, slot [0]. Aug 5 18:24:51 Tower kernel: ata7.00: both IDENTIFYs aborted, assuming NODEV Aug 5 18:24:51 Tower kernel: ata7.00: revalidation failed (errno=-2) Aug 5 18:24:53 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1522:mvs_I_T_nexus_reset for device[1]:rc= 0 Aug 5 18:24:54 Tower kernel: ata8.00: configured for UDMA/133 Aug 5 18:24:54 Tower kernel: ata8.00: device reported invalid CHS sector 0 Aug 5 18:24:54 Tower kernel: ata8: EH complete Aug 5 18:24:56 Tower kernel: ata7: hard resetting link Aug 5 18:24:56 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 626:command active 00000004, slot [0]. Aug 5 18:24:56 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 626:command active 00000004, slot [0]. Aug 5 18:24:56 Tower kernel: ata7.00: both IDENTIFYs aborted, assuming NODEV Aug 5 18:24:56 Tower kernel: ata7.00: revalidation failed (errno=-2) Aug 5 18:25:01 Tower kernel: ata7: hard resetting link Aug 5 18:25:02 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 626:command active 00000004, slot [0]. Aug 5 18:25:02 Tower kernel: drivers/scsi/mvsas/mv_94xx.c 626:command active 00000004, slot [0]. Aug 5 18:25:02 Tower kernel: ata7.00: both IDENTIFYs aborted, assuming NODEV Aug 5 18:25:02 Tower kernel: ata7.00: revalidation failed (errno=-2) Aug 5 18:25:02 Tower kernel: ata7.00: disabled Aug 5 18:25:02 Tower kernel: ata7: EH complete Aug 5 18:25:02 Tower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Unhandled error code Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 72 8e 8e 30 00 01 00 00 Aug 5 18:25:02 Tower kernel: end_request: I/O error, dev sdh, sector 1921945136 Aug 5 18:25:02 Tower kernel: Buffer I/O error on device sdh, logical block 240243142 Aug 5 18:25:02 Tower kernel: Buffer I/O error on device sdh, logical block 240243143 Aug 5 18:25:02 Tower kernel: Buffer I/O error on device sdh, logical block 240243144 Aug 5 18:25:02 Tower kernel: Buffer I/O error on device sdh, logical block 240243145 Aug 5 18:25:02 Tower kernel: Buffer I/O error on device sdh, logical block 240243146 Aug 5 18:25:02 Tower kernel: Buffer I/O error on device sdh, logical block 240243147 Aug 5 18:25:02 Tower kernel: Buffer I/O error on device sdh, logical block 240243148 Aug 5 18:25:02 Tower kernel: Buffer I/O error on device sdh, logical block 240243149 Aug 5 18:25:02 Tower kernel: Buffer I/O error on device sdh, logical block 240243150 Aug 5 18:25:02 Tower kernel: Buffer I/O error on device sdh, logical block 240243151 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Unhandled error code Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 72 8e 8d 30 00 01 00 00 Aug 5 18:25:02 Tower kernel: end_request: I/O error, dev sdh, sector 1921944880 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Unhandled error code Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 72 8e 8d 30 00 00 08 00 Aug 5 18:25:02 Tower kernel: end_request: I/O error, dev sdh, sector 1921944880 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Unhandled error code Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 72 8e 8d 30 00 00 08 00 Aug 5 18:25:02 Tower kernel: end_request: I/O error, dev sdh, sector 1921944880 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Unhandled error code Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 72 8e aa 50 00 00 20 00 Aug 5 18:25:02 Tower kernel: end_request: I/O error, dev sdh, sector 1921952336 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Unhandled error code Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Aug 5 18:25:02 Tower kernel: sd 0:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 72 8e aa 50 00 00 08 00 Aug 5 18:25:02 Tower kernel: end_request: I/O error, dev sdh, sector 1921952336 The preclear was at 65% I have many thoused of these errrors, and i stopped the preclear. In the beginning it were multiple sectors, the last 8000 lines it is only one sector it complains about. Aug 5 18:44:28 Tower kernel: end_request: I/O error, dev sdh, sector 2930275776 Aug 5 18:44:28 Tower kernel: sd 0:0:0:0: [sdh] Unhandled error code Aug 5 18:44:28 Tower kernel: sd 0:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Aug 5 18:44:28 Tower kernel: sd 0:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 ae a8 75 c0 00 00 08 00 Aug 5 18:44:28 Tower kernel: end_request: I/O error, dev sdh, sector 2930275776 what i did: - moved the hdd over to another sata data and power port (SFF8087 to 4 sata) on which another disk precleared fine I am running 5.0 RC6 This disc is connected to a supermicro AOC-SAS2LP-MV8 Is the HDD bad, and perhaps remapping bad sectors ? I can imagine if this takes to long unraid times out.

I tried to preclear 6 drives at once: system: System: Supermicro - X7SPA-HF CPU: Intel® AtomTM CPU D525 @ 1.80GHz - 1.8 GHz Cache: 48 kB Memory: 4 GB - 800 MHz Network: 1000Mb/s - Full Duplex 5.0-rc5 drive on mainbord: 1) Hitachi_HDS724040ALE640_PK1311PAG4DNJS (sda) 3907018584 drives on ARC1300-16: 2) Hitachi_HDS724040ALE640_PK1311PAG4VJ7S (sdd) 3907018584 3) Hitachi_HDS724040ALE640_PK2311PAG4R9WM (sde) 3907018584 4) Hitachi_HDS724040ALE640_PK1311PAG4VMSS (sdf) 3907018584 5) Hitachi_HDS724040ALE640_PK2311PAG4SX0M (sdg) 3907018584 6) Hitachi_HDT725032VLA380_VFA200R2CL7TPA (sdh) 312571224 6) worked ok and finsihed ok (320 GB) 1) still running 3) still running 4) still running 2) stopped at 1:40 hours in first step 5) stopped at 1:40 hours in first step I added a part of the syslog with the errors, seems something crashed. Can someone look and comment what is wrong here ? Also i have the syslog filled with these lines: Jul 22 06:52:52 Tower emhttp: shcmd (1274): /usr/local/sbin/emhttp_event driver_loaded Jul 22 06:52:52 Tower emhttp_event: driver_loaded Jul 22 06:52:56 Tower emhttp: shcmd (1275): rmmod md-mod |& logger Jul 22 06:52:56 Tower emhttp: shcmd (1276): modprobe md-mod super=/boot/config/super.dat slots=21 |& logger Jul 22 06:52:56 Tower kernel: md: unRAID driver removed Jul 22 06:52:56 Tower emhttp: shcmd (1277): udevadm settle Jul 22 06:52:56 Tower kernel: md: unRAID driver 2.1.4 installed Jul 22 06:52:56 Tower kernel: read_file: error 2 opening /boot/config/super.dat Jul 22 06:52:56 Tower kernel: md: could not read superblock from /boot/config/super.dat Jul 22 06:52:56 Tower kernel: md: initializing superblock Jul 22 06:52:56 Tower emhttp: Device inventory: Jul 22 06:52:56 Tower emhttp: Hitachi_HDT721010SLA360_STF604MH0RR14B (sdb) 976762584 Jul 22 06:52:56 Tower emhttp: Hitachi_HDS724040ALE640_PK1311PAG4DNJS (sda) 3907018584 Jul 22 06:52:56 Tower emhttp: Hitachi_HDS724040ALE640_PK1311PAG4VJ7S (sdd) 3907018584 Jul 22 06:52:56 Tower emhttp: Hitachi_HDS724040ALE640_PK2311PAG4R9WM (sde) 3907018584 Jul 22 06:52:56 Tower emhttp: Hitachi_HDS724040ALE640_PK1311PAG4VMSS (sdf) 3907018584 Jul 22 06:52:56 Tower emhttp: Hitachi_HDS724040ALE640_PK2311PAG4SX0M (sdg) 3907018584 Jul 22 06:52:56 Tower emhttp: Hitachi_HDT725032VLA380_VFA200R2CL7TPA (sdh) 312571224 Jul 22 06:52:56 Tower kernel: mdcmd (1): import 0 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (2): import 1 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (3): import 2 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (4): import 3 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (5): import 4 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (6): import 5 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (7): import 6 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (: import 7 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (9): import 8 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (10): import 9 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (11): import 10 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (12): import 11 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (13): import 12 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (14): import 13 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (15): import 14 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (16): import 15 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (17): import 16 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (18): import 17 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (19): import 18 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (20): import 19 0,0 Jul 22 06:52:56 Tower kernel: mdcmd (21): import 20 0,0 What does this mean ? System is in a cooled room. The arc 1300 is colled with a fan. Powersupply is a 1000 watts 80 amps single rail cooler master silent pro. Thanks, Jaco syslog_extract_preclear.txt

i looked up all the manufacturers specs for my hdd's: Hitachi 7K4000 2,0 Hitachi HDT721010SLA360 1,87 Samsung HD103UJ 2,4 Samsung HD145UI 2,0 seagate ST2000DL003 2,1 All values for Amperage at 12 volts during startup This would be around 47 amps at startup for the 12 Volt.

Is a seasonic Platinum powersupply advised nowdays ? http://www.seasonicusa.com/Platinum_Series.htm I will have 22 hdd's i think, most of them 7200 RPM. Is the 860 enough (71 AMP) or better the 1000 (83 AMP) The drives: 7200 RPM Hitachi 7K4000 (4TB) (5) Hitachi HDT721010SLA360 (1TB) (5) Samsung HD103UJ (2) green: Seagate ST2000DL003 (2TB) (3) Samsung HD145UI (1.5 TB) (5) Growth/replacement most likely hitachi 5K3000 / 7K4000 edit: only 22, no more sata ports edit 2: 'only' 11 Sata and 8 molex connectors.