downloadski
-
Posts
222 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by downloadski
-
-
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)
-
Are other users able to preclear 3TB using the defaults without running out of memory?
Yes, i have precleared a Toshiba 3T with the standaard preclear command. This was done in 25 hours (i3-2100t processor and 16 GB RAM on a sata-600 interface )
-
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 1921952336The 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 pulled the card from the system. I had several crashes/hanging system and always a drive on this card had the mvsas issues.
Perhaps the combination of the marvel chip with the lsi sas expander chip behind is critical with timings or such. I do not care to find out, i will buy a 8 port card which has better reputation.
If i need more drives than 6 + 8 i might look for another mainbord with more pci-e slots.
This card is not advised for unraid as far as my experience till now. Hopefully people will stay away form this product.
-
Jowi, yes i thought of you.
Well, 4 out of 6 drives were working.
I think 4 on one split out cable was too much.
Anyway, i will re run the 2 failed disks.
-
Johnm,
I run with 4 MB of Ram on a ATOM based mainbord: Supermicro X7SPA-HF
I posted the errors i received here: http://lime-technology.com/forum/index.php?topic=4068.msg191817#msg191817
I though of a issue with pre-clear, but there i think my memory was indeed the issue seen in the error in the above mentioned thread. So it was not wise to start with 6 discs i guess.
On the bandwidth. It is a 16 port SAS non raid controller with PCI-E 4x
From the Marvel Site:
The first product in Marvell’s SAS controller portfolio is the Marvell 88SE6440 host controller, supporting four SAS/SATA ports. The 88SE6440 offers 4-lane PCI-Express connectivity to the host system for high throughput in bandwidth-hungry applications
From their PDF:
88SE6440 PCIe x4 to 4 SAS/SATA 3Gb/s Ports RAID Controller
From the sata wiki
SATA revision 2.0 (SATA 3 Gbit/s)Second generation SATA interfaces running at 3.0 Gbit/s shipped in high volume by 2010, and were prevalent in all[citation needed] SATA disk drives and most PC and server chipsets. With a native transfer rate of 3.0 Gbit/s, and taking 8b/10b encoding into account, the maximum uncoded transfer rate is 2.4 Gbit/s (300 MB/s).
So with this LSI SAS expander behind the Marvel chip there is never more than 4 times 300 Mbyte/sec
This must be somehow shared between the 16 ports, i assume every 4 usable sata interfaces share one Marvel Sata interface as 4 x 4 = 16.
Than each physical interface can use maximal 300/4 = 75 Mbyte/sec
I saw 2 discs doing around 150 Mbyte/sec in the pre-clear, and 2 rather slow ones at the start which failed after like 1 hour and some minutes.
-
After some more checking on the web i think that it has a Marvell 88se6440 for the connection to the PCI-E 4x slot. It than outputs 4 SAS/SATA channels of 300 (?) Mbyte/sec into a LSI SASX28 which seems to be a port muliplier.
http://www.marvell.com/products/storage/Serial_Attached_SCSI_SAS_Storage_Controller/release/742/
So i fear every SFF-8087 connector (behind the SASX28) which fans out into 4 SATA cables is in fact sharing 300 (?) Mbyte/sec from one of the Marvel 'channels'
If this info is correct, i am not surprised it stopped working for half the discs as i had 4 times a hdd connected that does >150 MB/sec on the outer sectors.
2 were working, 2 not... (or better said: slow at start, stopped after 1 hour 40 minutes)
Have to try out this: Not do connect 4 drives on one fan-out cable, but distribute across the 4 fan-out cables to utilise all the 4 channels.
One question left:
Will this work with parity calculation where every disk is read (i assume starting at the lowest sector for all disks at once and than work its way up)
-
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
-
The 2. 14% ones seem stuck, their run time counter does not increase anymore.
I thought there are some issues with the hardware, but than i found this in the syslog:
Jul 22 01:49:10 Tower kernel: dd: page allocation failure: order:1, mode:0x8020 Jul 22 01:49:10 Tower kernel: Pid: 30243, comm: dd Tainted: G W 3.0.35-unRAID #2 Jul 22 01:49:10 Tower kernel: Call Trace: Jul 22 01:49:10 Tower kernel: [] warn_alloc_failed+0xb2/0xc4 Jul 22 01:49:10 Tower kernel: [] __alloc_pages_nodemask+0x456/0x47f Jul 22 01:49:10 Tower kernel: [] dma_generic_alloc_coherent+0x57/0xe8 Jul 22 01:49:10 Tower kernel: [] T.475+0xb1/0x123 Jul 22 01:49:10 Tower kernel: [] ? dma_set_mask+0x37/0x37 Jul 22 01:49:10 Tower kernel: [] dma_pool_alloc+0x53/0x107 Jul 22 01:49:10 Tower kernel: [] mvs_task_prep+0x1b3/0x373 [mvsas] Jul 22 01:49:10 Tower kernel: [] mvs_task_exec+0x53/0xc5 [mvsas] Jul 22 01:49:10 Tower kernel: [] mvs_queue_command+0x23/0x32 [mvsas] Jul 22 01:49:10 Tower kernel: [] sas_ata_qc_issue+0x1da/0x236 [libsas] Jul 22 01:49:10 Tower kernel: [] ata_qc_issue+0x273/0x291 Jul 22 01:49:10 Tower kernel: [] ata_scsi_translate+0xcf/0xfd Jul 22 01:49:10 Tower kernel: [] ? ata_scsiop_mode_sense+0x257/0x257 Jul 22 01:49:10 Tower kernel: [] ata_sas_queuecmd+0x17e/0x1ac Jul 22 01:49:10 Tower kernel: [] sas_queuecommand_lck+0x78/0x13a [libsas] Jul 22 01:49:10 Tower kernel: [] sas_queuecommand+0x27/0x3a [libsas] Jul 22 01:49:10 Tower kernel: [] scsi_dispatch_cmd+0xfa/0x125 Jul 22 01:49:10 Tower kernel: [] scsi_request_fn+0x27e/0x3a2 Jul 22 01:49:10 Tower kernel: [] __blk_run_queue+0x14/0x16 Jul 22 01:49:10 Tower kernel: [] blk_flush_plug_list+0x159/0x16b Jul 22 01:49:10 Tower kernel: [] io_schedule+0x2f/0x54 Jul 22 01:49:10 Tower kernel: [] dio_await_completion+0x40/0x94 Jul 22 01:49:10 Tower kernel: [] direct_io_worker+0x2d2/0x33a Jul 22 01:49:10 Tower kernel: [] ? __blockdev_direct_IO+0x125/0x250 Jul 22 01:49:10 Tower kernel: [] __blockdev_direct_IO+0x23a/0x250 Jul 22 01:49:10 Tower kernel: [] ? blkdev_max_block+0x65/0x65 Jul 22 01:49:10 Tower kernel: [] blkdev_direct_IO+0x2f/0x34 Jul 22 01:49:10 Tower kernel: [] ? blkdev_max_block+0x65/0x65 Jul 22 01:49:10 Tower kernel: [] generic_file_aio_read+0x105/0x1fa Jul 22 01:49:10 Tower kernel: [] do_sync_read+0x8a/0xc5 Jul 22 01:49:10 Tower kernel: [] ? do_page_fault+0x302/0x332 Jul 22 01:49:10 Tower kernel: [] vfs_read+0x88/0xfa Jul 22 01:49:10 Tower kernel: [] ? do_sync_write+0xc5/0xc5 Jul 22 01:49:10 Tower kernel: [] sys_read+0x3b/0x60 Jul 22 01:49:10 Tower kernel: [] syscall_call+0x7/0xb Jul 22 01:49:10 Tower kernel: Mem-Info: Jul 22 01:49:10 Tower kernel: DMA per-cpu: Jul 22 01:49:10 Tower kernel: CPU 0: hi: 0, btch: 1 usd: 0 Jul 22 01:49:10 Tower kernel: CPU 1: hi: 0, btch: 1 usd: 0 Jul 22 01:49:10 Tower kernel: CPU 2: hi: 0, btch: 1 usd: 0 Jul 22 01:49:10 Tower kernel: CPU 3: hi: 0, btch: 1 usd: 0 Jul 22 01:49:10 Tower kernel: Normal per-cpu: Jul 22 01:49:10 Tower kernel: CPU 0: hi: 186, btch: 31 usd: 0 Jul 22 01:49:10 Tower kernel: CPU 1: hi: 186, btch: 31 usd: 14 Jul 22 01:49:10 Tower kernel: CPU 2: hi: 186, btch: 31 usd: 0 Jul 22 01:49:10 Tower kernel: CPU 3: hi: 186, btch: 31 usd: 14 Jul 22 01:49:10 Tower kernel: HighMem per-cpu: Jul 22 01:49:10 Tower kernel: CPU 0: hi: 186, btch: 31 usd: 29 Jul 22 01:49:10 Tower kernel: CPU 1: hi: 186, btch: 31 usd: 30 Jul 22 01:49:10 Tower kernel: CPU 2: hi: 186, btch: 31 usd: 30 Jul 22 01:49:10 Tower kernel: CPU 3: hi: 186, btch: 31 usd: 9 Jul 22 01:49:10 Tower kernel: active_anon:20432 inactive_anon:36 isolated_anon:0 Jul 22 01:49:10 Tower kernel: active_file:24040 inactive_file:274362 isolated_file:55 Jul 22 01:49:10 Tower kernel: unevictable:0 dirty:27208 writeback:8868 unstable:0 Jul 22 01:49:10 Tower kernel: free:708733 slab_reclaimable:5115 slab_unreclaimable:1829 Jul 22 01:49:10 Tower kernel: mapped:1620 shmem:41 pagetables:317 bounce:127 Jul 22 01:49:10 Tower kernel: DMA free:3508kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:8352kB unevictable:0kB isolated(anon):0kB isolated(file):128kB present:15784kB mlocked:0kB dirty:2432kB writeback:36kB mapped:0kB shmem:0kB slab_reclaimable:3396kB slab_unreclaimable:268kB kernel_stack:104kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Jul 22 01:49:10 Tower kernel: lowmem_reserve[]: 0 869 4039 4039 Jul 22 01:49:10 Tower kernel: Normal free:3764kB min:3736kB low:4668kB high:5604kB active_anon:0kB inactive_anon:0kB active_file:3544kB inactive_file:812928kB unevictable:0kB isolated(anon):0kB isolated(file):92kB present:890008kB mlocked:0kB dirty:106400kB writeback:35436kB mapped:4kB shmem:0kB slab_reclaimable:17064kB slab_unreclaimable:7048kB kernel_stack:808kB pagetables:0kB unstable:0kB bounce:508kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Jul 22 01:49:10 Tower kernel: lowmem_reserve[]: 0 0 25363 25363 Jul 22 01:49:10 Tower kernel: HighMem free:2827660kB min:512kB low:3920kB high:7328kB active_anon:81728kB inactive_anon:144kB active_file:92616kB inactive_file:276168kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:3246564kB mlocked:0kB dirty:0kB writeback:0kB mapped:6476kB shmem:164kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:1268kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Jul 22 01:49:10 Tower kernel: lowmem_reserve[]: 0 0 0 0 Jul 22 01:49:10 Tower kernel: DMA: 3*4kB 5*8kB 0*16kB 0*32kB 4*64kB 13*128kB 4*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 3508kB Jul 22 01:49:10 Tower kernel: Normal: 864*4kB 21*8kB 12*16kB 1*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3848kB Jul 22 01:49:10 Tower kernel: HighMem: 15*4kB 12*8kB 8*16kB 4*32kB 89*64kB 122*128kB 36*256kB 18*512kB 4*1024kB 3*2048kB 678*4096kB = 2827484kB Jul 22 01:49:10 Tower kernel: 298464 total pagecache pages Jul 22 01:49:10 Tower kernel: 0 pages in swap cache Jul 22 01:49:10 Tower kernel: Swap cache stats: add 0, delete 0, find 0/0 Jul 22 01:49:10 Tower kernel: Free swap = 0kB Jul 22 01:49:10 Tower kernel: Total swap = 0kB Jul 22 01:49:10 Tower kernel: 1310704 pages RAM Jul 22 01:49:10 Tower kernel: 1082370 pages HighMem Jul 22 01:49:10 Tower kernel: 274053 pages reserved Jul 22 01:49:10 Tower kernel: 232113 pages shared Jul 22 01:49:10 Tower kernel: 106449 pages non-shared Jul 22 01:49:10 Tower kernel: mvsas 0000:01:00.0: mvsas prep failed[0]! Jul 22 01:49:10 Tower kernel: dd: page allocation failure: order:1, mode:0x8020 Jul 22 01:49:10 Tower kernel: Pid: 30124, comm: dd Tainted: G W 3.0.35-unRAID #2 Jul 22 01:49:10 Tower kernel: Call Trace: Jul 22 01:49:10 Tower kernel: [] warn_alloc_failed+0xb2/0xc4 Jul 22 01:49:10 Tower kernel: [] __alloc_pages_nodemask+0x456/0x47f Jul 22 01:49:10 Tower kernel: [] ? drain_pages+0x4a/0x56 Jul 22 01:49:10 Tower kernel: [] ? free_pcppages_bulk+0x24d/0x258 Jul 22 01:49:10 Tower kernel: [] dma_generic_alloc_coherent+0x57/0xe8 Jul 22 01:49:10 Tower kernel: [] T.475+0xb1/0x123 Jul 22 01:49:10 Tower kernel: [] ? dma_set_mask+0x37/0x37 Jul 22 01:49:10 Tower kernel: [] dma_pool_alloc+0x53/0x107 Jul 22 01:49:10 Tower kernel: [] ? mempool_alloc_slab+0xe/0x10 Jul 22 01:49:10 Tower kernel: [] mvs_task_prep+0x1b3/0x373 [mvsas] Jul 22 01:49:10 Tower kernel: [] mvs_task_exec+0x53/0xc5 [mvsas] Jul 22 01:49:10 Tower kernel: [] mvs_queue_command+0x23/0x32 [mvsas] Jul 22 01:49:10 Tower kernel: [] sas_ata_qc_issue+0x1da/0x236 [libsas] Jul 22 01:49:10 Tower kernel: [] ata_qc_issue+0x273/0x291 Jul 22 01:49:10 Tower kernel: [] ata_scsi_translate+0xcf/0xfd Jul 22 01:49:10 Tower kernel: [] ? ata_scsiop_mode_sense+0x257/0x257 Jul 22 01:49:10 Tower kernel: [] ata_sas_queuecmd+0x17e/0x1ac Jul 22 01:49:10 Tower kernel: [] sas_queuecommand_lck+0x78/0x13a [libsas] Jul 22 01:49:10 Tower kernel: [] sas_queuecommand+0x27/0x3a [libsas] Jul 22 01:49:10 Tower kernel: [] scsi_dispatch_cmd+0xfa/0x125 Jul 22 01:49:10 Tower kernel: [] scsi_request_fn+0x27e/0x3a2 Jul 22 01:49:10 Tower kernel: [] __blk_run_queue+0x14/0x16 Jul 22 01:49:10 Tower kernel: [] blk_flush_plug_list+0x159/0x16b Jul 22 01:49:10 Tower kernel: [] blk_finish_plug+0xd/0x28 Jul 22 01:49:10 Tower kernel: [] read_pages+0x9d/0xa7 Jul 22 01:49:10 Tower kernel: [] __do_page_cache_readahead+0xea/0x103 Jul 22 01:49:10 Tower kernel: [] ra_submit+0x17/0x1c Jul 22 01:49:10 Tower kernel: [] ondemand_readahead+0x17c/0x188 Jul 22 01:49:10 Tower kernel: [] page_cache_async_readahead+0x54/0x5f Jul 22 01:49:10 Tower kernel: [] T.891+0xfa/0x3a6 Jul 22 01:49:10 Tower kernel: [] generic_file_aio_read+0x1c9/0x1fa Jul 22 01:49:10 Tower kernel: [] ? sched_clock_local+0x17/0x13d Jul 22 01:49:10 Tower kernel: [] do_sync_read+0x8a/0xc5 Jul 22 01:49:10 Tower kernel: [] ? fsnotify+0x1ad/0x1c7 Jul 22 01:49:10 Tower kernel: [] vfs_read+0x88/0xfa Jul 22 01:49:10 Tower kernel: [] ? do_sync_write+0xc5/0xc5 Jul 22 01:49:10 Tower kernel: [] sys_read+0x3b/0x60 Jul 22 01:49:10 Tower kernel: [] syscall_call+0x7/0xb Jul 22 01:49:10 Tower kernel: [] ? _cpu_down+0xc4/0x1bc Jul 22 01:49:10 Tower kernel: Mem-Info: Jul 22 01:49:10 Tower kernel: DMA per-cpu: Jul 22 01:49:10 Tower kernel: CPU 0: hi: 0, btch: 1 usd: 0 Jul 22 01:49:10 Tower kernel: CPU 1: hi: 0, btch: 1 usd: 0 Jul 22 01:49:10 Tower kernel: CPU 2: hi: 0, btch: 1 usd: 0 Jul 22 01:49:10 Tower kernel: CPU 3: hi: 0, btch: 1 usd: 0 Jul 22 01:49:10 Tower kernel: Normal per-cpu: Jul 22 01:49:10 Tower kernel: CPU 0: hi: 186, btch: 31 usd: 74 Jul 22 01:49:10 Tower kernel: CPU 1: hi: 186, btch: 31 usd: 3 Jul 22 01:49:10 Tower kernel: CPU 2: hi: 186, btch: 31 usd: 30 Jul 22 01:49:10 Tower kernel: CPU 3: hi: 186, btch: 31 usd: 0 Jul 22 01:49:10 Tower kernel: HighMem per-cpu: Jul 22 01:49:10 Tower kernel: CPU 0: hi: 186, btch: 31 usd: 0 Jul 22 01:49:10 Tower kernel: CPU 1: hi: 186, btch: 31 usd: 74 Jul 22 01:49:10 Tower kernel: CPU 2: hi: 186, btch: 31 usd: 0 Jul 22 01:49:10 Tower kernel: CPU 3: hi: 186, btch: 31 usd: 0 Jul 22 01:49:10 Tower kernel: active_anon:20432 inactive_anon:36 isolated_anon:0 Jul 22 01:49:10 Tower kernel: active_file:24040 inactive_file:274297 isolated_file:55 Jul 22 01:49:10 Tower kernel: unevictable:0 dirty:27245 writeback:8868 unstable:0 Jul 22 01:49:10 Tower kernel: free:708687 slab_reclaimable:5115 slab_unreclaimable:1829 Jul 22 01:49:10 Tower kernel: mapped:1620 shmem:41 pagetables:317 bounce:127 Jul 22 01:49:10 Tower kernel: DMA free:3508kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:8352kB unevictable:0kB isolated(anon):0kB isolated(file):128kB present:15784kB mlocked:0kB dirty:2432kB writeback:36kB mapped:0kB shmem:0kB slab_reclaimable:3396kB slab_unreclaimable:268kB kernel_stack:104kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Jul 22 01:49:10 Tower kernel: lowmem_reserve[]: 0 869 4039 4039 Jul 22 01:49:10 Tower kernel: Normal free:3736kB min:3736kB low:4668kB high:5604kB active_anon:0kB inactive_anon:0kB active_file:3544kB inactive_file:812668kB unevictable:0kB isolated(anon):0kB isolated(file):92kB present:890008kB mlocked:0kB dirty:106548kB writeback:35436kB mapped:4kB shmem:0kB slab_reclaimable:17064kB slab_unreclaimable:7048kB kernel_stack:808kB pagetables:0kB unstable:0kB bounce:508kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Jul 22 01:49:10 Tower kernel: lowmem_reserve[]: 0 0 25363 25363 Jul 22 01:49:10 Tower kernel: HighMem free:2827504kB min:512kB low:3920kB high:7328kB active_anon:81728kB inactive_anon:144kB active_file:92616kB inactive_file:276168kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:3246564kB mlocked:0kB dirty:0kB writeback:0kB mapped:6476kB shmem:164kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:1268kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Jul 22 01:49:10 Tower kernel: lowmem_reserve[]: 0 0 0 0 Jul 22 01:49:10 Tower kernel: DMA: 3*4kB 5*8kB 0*16kB 0*32kB 4*64kB 13*128kB 4*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 3508kB Jul 22 01:49:10 Tower kernel: Normal: 865*4kB 9*8kB 10*16kB 1*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3724kB Jul 22 01:49:10 Tower kernel: HighMem: 16*4kB 12*8kB 10*16kB 6*32kB 90*64kB 122*128kB 36*256kB 18*512kB 4*1024kB 3*2048kB 678*4096kB = 2827648kB Jul 22 01:49:10 Tower kernel: 298427 total pagecache pages Jul 22 01:49:10 Tower kernel: 0 pages in swap cache Jul 22 01:49:10 Tower kernel: Swap cache stats: add 0, delete 0, find 0/0 Jul 22 01:49:10 Tower kernel: Free swap = 0kB Jul 22 01:49:10 Tower kernel: Total swap = 0kB Jul 22 01:49:10 Tower kernel: 1310704 pages RAM Jul 22 01:49:10 Tower kernel: 1082370 pages HighMem Jul 22 01:49:10 Tower kernel: 274053 pages reserved Jul 22 01:49:10 Tower kernel: 232138 pages shared Jul 22 01:49:10 Tower kernel: 106448 pages non-shared Jul 22 01:49:10 Tower kernel: mvsas 0000:01:00.0: mvsas prep failed[0]!
Was i simply out of memorey there ?
I did run a pre-clear on 6 drives at once. An 320 GB succeeded, 3 x a 4 TB disk is still running, and 2 are stuck.
After this error the syslog is filled with these:
Jul 22 01:49:40 Tower kernel: sas: command 0xc0f20f00, task 0xd3496640, not at initiator: BLK_EH_RESET_TIMER Jul 22 01:49:40 Tower kernel: sas: command 0xdd93bc00, task 0xc75472c0, not at initiator: BLK_EH_RESET_TIMER Jul 22 01:50:11 Tower kernel: sas: command 0xc0f20f00, task 0xd3496640, not at initiator: BLK_EH_RESET_TIMER Jul 22 01:50:11 Tower kernel: sas: command 0xdd93bc00, task 0xc75472c0, not at initiator: BLK_EH_RESET_TIMER
This last error is reported on this site with issues with 3 TB drives also:
http://lime-technology.com/forum/index.php?topic=15810.0
This specific error perhaps comes up in google search frequently like this one:
http://www.spinics.net/lists/linux-ide/msg42602.html
Perhaps me starting 4 times a 4 TB hitachi 7K4000 was too much data for the Areca, or simply too much for the system, as on the mainboard an hitachi 320 Gb and a 4TB were also preclearing.
I will wait for the 3 curently running ones (1 on mainboard and 2 on the areca) and reboot and retry the failed 2. (one on the areca and one on the mainbord than to compare)
-
In the meanwhile i received my components, and now all seems to work.
I have precleared 1 TB via the mainbord, and now running 5 drive pre-clear (1 via mainbord, 2- 4 via the ARC-1300)
Strange effect though:
1) 76% - 36 degrees
2) 14% - 40 degrees
3) 66% - 41 degrees
4) 65% - 40 degrees
5) 14% - 37 degrees
So i seem to have 2 slow ones, and 2 faster ones. These drives are all connecte via an sff8087 to 4 sata cabel.
Perhaps config issueon the areca ?
-
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.
-
Dhcp did not work, so i did put in a ip address manually.
Is there a text based gui ? I should read more info first i guess. The description of the http based gui seemed clear, so i hoped to use that
-
I could not do much during my tests unfortunately.
I have issues getting the LAN to work. I configured the eth0 with fixed ip, but it comes up in 10 mbps half duplex.
I cannot ping the default gateway (i am sure on the ip adressing)
How do i set the ethernet config to 1000 full fixed ?
I assume if i get the ip connection working i can use a other device to browse to the web interface of it and have a more manageble interface (for me as a non linux user at least)
-
Hello all, i am new to this forum.
I am thinking of setting up a unraid server.
For sata ports i have a Areca ARC-1300ix-16 available. http://www.areca.com.tw/products/sasnoneraid3g.htm
I did download a free version of unraid (unRAID Server 5.0-rc5 AiO) and created abootable usb flash disk (sandisk 8 GB)
For test purpose i used my main PC which is a Asus P6T WS pro mainbord with i7 and 12 GB ram.
X58 / ICH10R - 2 x Realtek® 8111C PCIe Dual Gigabit LAN controllers and only that areca controller with one 320 GB hitachi disk attached.
It seems to start ok, end i end up on the linux command prompt.
If i browse through the syslog i see the following entrys:
Jul 6 18:37:24 Tower kernel: sas: Enter sas_scsi_recover_host Jul 6 18:37:24 Tower kernel: ata7: sas eh calling libata port error handler Jul 6 18:37:24 Tower kernel: sas: sas_ata_hard_reset: Found ATA device. Jul 6 18:37:24 Tower kernel: ata7.00: ATA-7: Hitachi HDT725032VLA380, V54OA52A, max UDMA/133 Jul 6 18:37:24 Tower kernel: ata7.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32) Jul 6 18:37:24 Tower kernel: ata7.00: configured for UDMA/133 Jul 6 18:37:24 Tower kernel: sas: --- Exit sas_scsi_recover_host Jul 6 18:37:24 Tower kernel: scsi 0:0:0:0: Direct-Access ATA Hitachi HDT72503 V54O PQ: 0 ANSI: 5 Jul 6 18:37:24 Tower kernel: sd 0:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB) Jul 6 18:37:24 Tower kernel: sd 0:0:0:0: Attached scsi generic sg1 type 0 Jul 6 18:37:24 Tower kernel: sd 0:0:0:0: [sdb] Write Protect is off Jul 6 18:37:24 Tower kernel: sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 6 18:37:24 Tower kernel: sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 6 18:37:24 Tower kernel: scsi 0:0:1:0: Enclosure Areca x28-05.60.1.30 000 PQ: 0 ANSI: 3 Jul 6 18:37:24 Tower kernel: scsi 0:0:1:0: Attached scsi generic sg2 type 13 Jul 6 18:37:24 Tower kernel: sas: DONE DISCOVERY on port 0, pid:910, result:0 Jul 6 18:37:24 Tower kernel: sdb: sdb1 Jul 6 18:37:24 Tower kernel: sd 0:0:0:0: [sdb] Attached SCSI disk
So this makes me think it does support the controller, as it finds the disk i hooked up behind it.
MY unix/linux knowledge is a bit oof (had some when i was a student) but reading through the forum and the wiki i found a few command which i tested:
hdparmcheck:
/dev/sdb:
ATA device, with non-removable media
Model Number: Hitachi HDT725032VLA380
Serial Number: VFA200R2CL7TPA
Firmware Revision: V54OA52A
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 1
Supported: 7 6 5 4 & some of 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 625142448
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 305245 MBytes
device size with M = 1000*1000: 320072 MBytes (320 GB)
cache/buffer size = 7372 KBytes (type=DualPortCache)
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 0
Advanced power management level: disabled
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
Advanced Power Management feature set
Power-Up In Standby feature set
SET_FEATURES required to spinup after power up
Address Offset Reserved Area Boot
SET_MAX security extension
Automatic Acoustic Management feature set
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
Media Card Pass-Through
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* URG for READ_STREAM[_DMA]_EXT
* URG for WRITE_STREAM[_DMA]_EXT
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
Non-Zero buffer offsets in DMA Setup FIS
DMA Setup Auto-Activate optimization
Device-initiated interface power management
In-order data delivery
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
128min for SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000cca211c84bf2
NAA : 5
IEEE OUI : 000cca
Unique ID : 211c84bf2
Checksum: correct
Smartinfo:
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Deskstar T7K500
Device Model: Hitachi HDT725032VLA380
Serial Number: VFA200R2CL7TPA
Firmware Version: V54OA52A
User Capacity: 320,072,933,376 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 1
Local Time is: Fri Jul 6 19:01:47 2012 Local time zone must be set--see zic m
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (5601) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 94) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0007 115 115 024 Pre-fail Always - 317 (Average 332)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 62
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 133
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 61
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 64
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 64
194 Temperature_Celsius 0x0002 181 181 000 Old_age Always - 33 (Min/Max 16/42)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 24
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
hdparmtest:
/dev/sdb:
Timing cached reads: 16828 MB in 2.00 seconds = 8433.67 MB/sec
Timing buffered disk reads: 214 MB in 3.00 seconds = 71.26 MB/sec
lsmod:
Module Size Used by
md_mod 45765 0
xor 13949 1 md_mod
sg 13023 0
i2c_i801 6261 0
i2c_core 12704 1 i2c_i801
pata_marvell 1837 0
ahci 17441 0
libahci 13678 1 ahci
ata_piix 17826 0
r8169 30022 0
mvsas 34043 0
libsas 41955 1 mvsas
scsi_transport_sas 16573 2 mvsas,libsas
asus_atk0110 6597 0
hwmon 945 1 asus_atk0110
I attached the syslog, if someone would be able to check if that looks basically ok i would be gratefull.
If this controller really works i intend to buy a supermicro ATOM mainbord http://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPA-HF-D525.cfm
I have also orginal Cooler Master CM Stacker case, and a coolermaster 1000 watt power supply spare for this.
I can than go for 3 times a 5in3 module and so go to 15 drives without to much cost in the hardware outside the new 3 TB Hdd´s
Thanks for any help.
MicroServer N36L/N40L/N54L - 6 Drive Edition
in Unraid Compulsive Design
Posted
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