f00kie

Bump. Anyone have this working?

Still looking for some advice on this. What if I buy another Antec 1200 case and start adding drives to it. What kind of a card do I need in the host server (current 1200) and the slave server (new 1200) to link the two? I do not want two separate Unraid instances, as I like my folder structure to be clean.

It would suck if I have to get rid of my 2TB drives -- they're WD drives and are running fine. Is there a way I can 'add-on' to the same array via another case? I don't want build a second Unraid array because, one of the key benefits of Unraid, is that all of the data is pooled into one array. I looked into 5x3 enclosures - and they're $100! Seems way too much to be a viable solution.

I have been running Unraid for about 2 years now and love this thing - since it doesn't have a GUI, I don't touch it's setting, which is great because it's rock solid and stable. Anyway, I am running out of HDD space, as well as physical space in my enclosure. I have: Antec 1200 Case 3x 4-in-3 HDD Enclosures (Coolermaster I believe) 1x parity 2TB 14x drive 2TB 1x cache 500GB That's all the physical space I have in the case, but I am down to about 3.3TB of free space, which sounds like a lot, but isn't when looking at each individual drive (they're well balanced at about 87% full). So what are my choices? I think I have slots of my controller card for more SATA connections. I can start converting the 4-in-3 enclosures to 5-in-3 and keep purchasing 2TB drives? I can purchase a bigger enclosure (I'd like to maintain the desktop form factor though)? I can start upgrading to 3TB drives? What would you suggest?

I just had the same show up, and I am running the AOC-SASLP-MV8. I have a lot of drives connected through. Dec 12 09:21:11 Tower kernel: ------------[ cut here ]------------ Dec 12 09:21:11 Tower kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() (Minor Issues) Dec 12 09:21:11 Tower kernel: Hardware name: GA-MA770-DS3P Dec 12 09:21:11 Tower kernel: Modules linked in: md_mod xor atiixp ahci r8169 sata_sil24 mvsas libsas scst scsi_transport_sas [last unloaded: xor] (Drive related) Dec 12 09:21:11 Tower kernel: Pid: 12499, comm: smartctl Tainted: G W 2.6.32.9-unRAID #8 (Errors) Dec 12 09:21:11 Tower kernel: Call Trace: (Errors) Dec 12 09:21:11 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Dec 12 09:21:11 Tower kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors) Dec 12 09:21:11 Tower kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 (Errors) Dec 12 09:21:11 Tower kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff (Errors) Dec 12 09:21:11 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Dec 12 09:21:11 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Dec 12 09:21:11 Tower kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 (Errors) Dec 12 09:21:11 Tower kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d (Errors) Dec 12 09:21:11 Tower kernel: [<f841d69a>] sas_queuecommand+0x65/0x20d [libsas] (Errors) Dec 12 09:21:11 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Dec 12 09:21:11 Tower kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 (Errors) Dec 12 09:21:11 Tower kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 (Errors) Dec 12 09:21:11 Tower kernel: [<c11269a8>] __generic_unplug_device+0x26/0x29 (Errors) Dec 12 09:21:11 Tower kernel: [<c112934a>] blk_execute_rq_nowait+0x56/0x73 (Errors) Dec 12 09:21:11 Tower kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 (Errors) Dec 12 09:21:11 Tower kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 (Errors) Dec 12 09:21:11 Tower kernel: [<c112636f>] ? get_request+0x204/0x28d (Errors) Dec 12 09:21:11 Tower kernel: [<c11269d6>] ? get_request_wait+0x2b/0xd9 (Errors) Dec 12 09:21:11 Tower kernel: [<c1125ce9>] ? __blk_put_request+0x8c/0x92 (Errors) Dec 12 09:21:11 Tower kernel: [<c11ac58a>] scsi_execute+0xbf/0x113 (Errors) Dec 12 09:21:11 Tower kernel: [<c11bb527>] ata_task_ioctl+0xb4/0x165 (Errors) Dec 12 09:21:11 Tower kernel: [<c11bb967>] ata_sas_scsi_ioctl+0x1d5/0x1e8 (Errors) Dec 12 09:21:11 Tower kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Dec 12 09:21:11 Tower kernel: [<f841d33d>] sas_ioctl+0x36/0x43 [libsas] (Errors) Dec 12 09:21:11 Tower kernel: [<c11a94c8>] scsi_ioctl+0x299/0x2ad (Errors) Dec 12 09:21:11 Tower kernel: [<f841d307>] ? sas_ioctl+0x0/0x43 [libsas] (Errors) Dec 12 09:21:11 Tower kernel: [<c104c98a>] ? get_page_from_freelist+0x70/0x344 (Errors) Dec 12 09:21:11 Tower kernel: [<c11b326d>] sd_ioctl+0x80/0x8c (Errors) Dec 12 09:21:11 Tower kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 (Errors) Dec 12 09:21:11 Tower kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc (Errors) Dec 12 09:21:11 Tower kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 (Errors) Dec 12 09:21:11 Tower kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 (Errors) Dec 12 09:21:11 Tower kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 (Errors) Dec 12 09:21:11 Tower kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Dec 12 09:21:11 Tower kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 (Errors) Dec 12 09:21:11 Tower kernel: [<c1048c43>] ? unlock_page+0x18/0x1b (Errors) Dec 12 09:21:11 Tower kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da (Errors) Dec 12 09:21:11 Tower kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 (Errors) Dec 12 09:21:11 Tower kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 (Errors) Dec 12 09:21:11 Tower kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 (Errors) Dec 12 09:21:11 Tower kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 (Errors) Dec 12 09:21:11 Tower kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac (Errors) Dec 12 09:21:11 Tower kernel: [<c129f124>] ? schedule+0x691/0x72f (Errors) Dec 12 09:21:11 Tower kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 (Errors) Dec 12 09:21:11 Tower kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Dec 12 09:21:11 Tower kernel: ---[ end trace 4eaa2a86a8e2da24 ]--- How serious is this? Everything seems to be working fine.

So what's the verdict on the WD20EARS? I'll be building a 4-8 HDD system soon; I've been burned on Seagate's before, so are the WD Green Drivers just going to cause more problems? Should I be looking into Samsung?