sincero

This is a follow up to: I replaced Disk 4 since it was already throwing a ton of errors and reading at 1MB/s. I still have another 12TB drive that I would like to add to the array but I don't want to expand the number of drives (power is one aspect, but there is also the failure rate of having too many drives, plus I don't trust some of these drives anymore), so I would like to replace another drive. I've attached new diagnostics; promathia-diagnostics-20231219-1401.zip I'm thinking disk1 should go as it has had some spurious "errors" (from the dashboard) at times, though the SMART data is clean. tldr; you have to replace one of these drives, which would you choose? I will be draining the disks to swap filesystems later.

All the disks in this machine are from 2014/2015. I figure they're probably going to all be dying over the next few years so I'm considering whether it makes sense to replace them all with 6TBs or 8TBs to get fresh drives and another 5-10 years out of them. Thoughts? My server lately grows at about 1.2TB per year, so I'll need more space eventually anyhow.

Thanks! I'm planning maybe to upgrade over half the disks anyway (or maybe replace them all with 8TB) so I think this should take care of it since they'll have all new filesystems. I'll probably just wait until Black Friday for some of them.

Thanks! So if I understand correctly, I can proceed with a parity swap once I order a new disk?

promathia-diagnostics-20230929-0159.zip

It looks like I should replace Disk 4 which has terrible performance and is barely able to read data from (though, I can.. I did manage to copy a few files off it to test). Disk 2 seems fine from a performance standpoint. unRAID has not marked Disk 4 as bad. However, the syslog has a ton of sector read errors. It has to be replaced, clearly. How should I proceed? Should I manually remove this disk from the array and let parity take over? The disk is not marked as bad. Can I buy a couple 8TB disks to take over? This should give me a bit more room and get some of the ageing disks out of the array. Or should I shut it down and replace them then? I have a full backup at home on another machine, so there is no concern there. But it would be nice to avoid needing to copy all 14TB back over gigabit slowly

FYI this is a bit older but make sure to to the Config in Sab and go to "Special" and scroll down to the bottom. There's a section for a whitelist, make sure it reads "tower" or "Tower" depending on how you are trying to access it (or whatever hostname you use for your Sab box) The case sensitivity is key -- it matters.

Hi all, I've recently been using Huginn for a few things and wanted to share an unRAID Template to use it: http://vaughanhilts.me/blog/2018/04/26/setting-up-huggins-on-unraid-for-automation.html I also wrote a guide on using it under unRAID for those less familar. I also wrote a blog post on how to utilize it for something fun here. I hope the community gets some enjoyment out of it.

^ The above advice is good but first; perform a backup.

It was 100% connected to the internet. Unraid let me know I needed to sync to a time server first, which I then did. Then, I verified the time matched my system clock.

Positive; it wouldn't even let me before. I had to sync it to an NTP server.

Hi all, More of a general frustration post than anything but I just finished upgrading from v5 to v6. It all went smooth but I intended to use the trial key to pilot the docker stuff before transiting into the full v6 upgrade, and decide what version to purchase after that. The trial key did not work. I requested one and got one but when I used it, it said it expired. I requested an extension and was told I could not, as my current key had not expired yet. So, since I had already set aside the time to do this upgrade tonight I went ahead and bought a BASIC license. I hope Lime-Tech can fix this so I can have more confidence upgrading to a larger version in the future.

You guys are the best, awesome community! All the best & happy holidays for those celebrating.

How much suffering are we talking here?

And if it isn't, what else can I use? Just one of my existing drives and let it stay spun up? Otherwise, I'm thinking of trying to jam a SSD on my eSATA port of my HP MicroServer...

How does one diagnose / fix this?

I have a 3TB Seagate drive that it dropping off with write errors. I'm thinking of replacing it but the problem is SMART looks fairly clean and when I reboot to put it back into the array, it actually shows as "No Device". Is it possible that the cabling / my server is losing connections somehow? Every time I reseat it, it works for a week or so and then write errors out again.. It's a HP Microserver G7; the bays are just slide in cages. Releavant outputs: root@Tower:~# ls -l /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 9 2015-12-08 23:52 ata-ST3000DM001-1CH166_Z1F37YED -> ../../sdb lrwxrwxrwx 1 root root 10 2015-12-08 23:52 ata-ST3000DM001-1CH166_Z1F37YED-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2015-12-08 23:52 ata-ST3000DM001-1CH166_Z1F40YWL -> ../../sdc lrwxrwxrwx 1 root root 10 2015-12-08 23:52 ata-ST3000DM001-1CH166_Z1F40YWL-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2015-12-08 23:52 scsi-SATA_ST3000DM001-1CH_Z1F37YED -> ../../sdb lrwxrwxrwx 1 root root 10 2015-12-08 23:52 scsi-SATA_ST3000DM001-1CH_Z1F37YED-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2015-12-08 23:52 scsi-SATA_ST3000DM001-1CH_Z1F40YWL -> ../../sdc lrwxrwxrwx 1 root root 10 2015-12-08 23:52 scsi-SATA_ST3000DM001-1CH_Z1F40YWL-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2015-12-08 23:52 usb-General_USB_Flash_Disk_0354120400059990-0:0 -> ../../sda lrwxrwxrwx 1 root root 10 2015-12-08 23:52 usb-General_USB_Flash_Disk_0354120400059990-0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2015-12-08 23:52 wwn-0x5000c50063af85f3 -> ../../sdb lrwxrwxrwx 1 root root 10 2015-12-08 23:52 wwn-0x5000c50063af85f3-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2015-12-08 23:52 wwn-0x5000c50065298f6e -> ../../sdc lrwxrwxrwx 1 root root 10 2015-12-08 23:52 wwn-0x5000c50065298f6e-part1 -> ../../sdc1 root@Tower:~# Relevant syslog: Dec 3 04:00:26 Tower kernel: md: disk1 write error, sector=2917467848 Dec 3 04:00:55 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:00:55 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:00:55 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:00:55 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:00:55 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 07 10 00 00 00 08 00 00 Dec 3 04:00:55 Tower kernel: end_request: I/O error, dev sdc, sector 2917467920 Dec 3 04:00:55 Tower kernel: md: disk1 write error, sector=2917467856 Dec 3 04:00:56 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:00:56 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:00:56 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:00:56 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:00:56 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 08 70 00 00 00 08 00 00 Dec 3 04:00:56 Tower kernel: end_request: I/O error, dev sdc, sector 2917468272 Dec 3 04:00:56 Tower kernel: md: disk1 write error, sector=2917468208 Dec 3 04:01:55 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:01:55 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:01:55 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:01:55 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:01:55 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 08 78 00 00 00 08 00 00 Dec 3 04:01:55 Tower kernel: end_request: I/O error, dev sdc, sector 2917468280 Dec 3 04:01:56 Tower kernel: md: disk1 write error, sector=2917468216 Dec 3 04:01:56 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:01:56 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:01:56 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:01:56 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:01:56 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 08 80 00 00 00 08 00 00 Dec 3 04:01:56 Tower kernel: end_request: I/O error, dev sdc, sector 2917468288 Dec 3 04:01:56 Tower kernel: md: disk1 write error, sector=2917468224 Dec 3 04:01:56 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:01:56 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:01:56 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:01:56 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:01:56 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 08 88 00 00 00 08 00 00 Dec 3 04:01:56 Tower kernel: end_request: I/O error, dev sdc, sector 2917468296 Dec 3 04:01:56 Tower kernel: md: disk1 write error, sector=2917468232 Dec 3 04:02:26 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:02:26 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:02:26 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:02:26 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:02:26 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 08 90 00 00 00 08 00 00 Dec 3 04:02:26 Tower kernel: end_request: I/O error, dev sdc, sector 2917468304 Dec 3 04:02:26 Tower kernel: md: disk1 write error, sector=2917468240 Dec 3 04:02:26 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:02:26 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:02:26 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:02:26 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:02:26 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 08 98 00 00 00 08 00 00 Dec 3 04:02:26 Tower kernel: end_request: I/O error, dev sdc, sector 2917468312 Dec 3 04:02:26 Tower kernel: md: disk1 write error, sector=2917468248 Dec 3 04:02:26 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:02:26 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:02:26 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:02:26 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:02:26 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 08 d8 00 00 00 08 00 00 Dec 3 04:02:26 Tower kernel: end_request: I/O error, dev sdc, sector 2917468376 Dec 3 04:02:26 Tower kernel: md: disk1 write error, sector=2917468312 Dec 3 04:03:26 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:03:26 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:03:26 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:03:26 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:03:26 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 08 e0 00 00 00 08 00 00 Dec 3 04:03:26 Tower kernel: end_request: I/O error, dev sdc, sector 2917468384 Dec 3 04:03:26 Tower kernel: md: disk1 write error, sector=2917468320 Dec 3 04:03:26 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:03:26 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:03:26 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:03:26 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:03:26 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 08 e8 00 00 00 08 00 00 Dec 3 04:03:26 Tower kernel: end_request: I/O error, dev sdc, sector 2917468392 Dec 3 04:03:26 Tower kernel: md: disk1 write error, sector=2917468328 Dec 3 04:03:26 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:03:26 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:03:26 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:03:26 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:03:26 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 09 40 00 00 00 08 00 00 Dec 3 04:03:26 Tower kernel: end_request: I/O error, dev sdc, sector 2917468480 Dec 3 04:03:27 Tower kernel: md: disk1 write error, sector=2917468416 Dec 3 04:03:56 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:03:56 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:03:56 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:03:56 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:03:56 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 09 48 00 00 00 08 00 00 Dec 3 04:03:56 Tower kernel: end_request: I/O error, dev sdc, sector 2917468488 Dec 3 04:03:56 Tower kernel: md: disk1 write error, sector=2917468424 Dec 3 04:03:57 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:03:57 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:03:57 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:03:57 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:03:57 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 09 50 00 00 00 08 00 00 Dec 3 04:03:57 Tower kernel: end_request: I/O error, dev sdc, sector 2917468496 Dec 3 04:03:57 Tower kernel: md: disk1 write error, sector=2917468432 Dec 3 04:03:57 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 3 04:03:57 Tower kernel: sd 2:0:0:0: [sdc] Dec 3 04:03:57 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 3 04:03:57 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 3 04:03:57 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 ad e5 09 58 00 00 00 08 00 00 Dec 3 04:03:57 Tower kernel: end_request: I/O error, dev sdc, sector 2917468504 Dec 3 04:03:57 Tower kernel: md: disk1 write error, sector=2917468440 Dec 3 09:30:51 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 3 09:30:51 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 3 09:30:51 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 3 20:34:06 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 3 20:34:06 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 3 20:34:06 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 4 07:34:08 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 4 07:34:08 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 4 07:34:08 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 4 18:18:52 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 4 18:18:52 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 4 18:18:52 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 5 05:11:01 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 5 05:11:01 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 5 05:11:01 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 5 16:25:14 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 5 16:25:14 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 5 16:25:14 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 6 03:13:19 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 6 03:13:19 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 6 03:13:19 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 6 14:22:15 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 6 14:22:15 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 6 14:22:15 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 7 00:52:43 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 7 00:52:43 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 7 00:52:44 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 7 11:31:22 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 7 11:31:22 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 7 11:31:22 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 7 22:34:11 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 7 22:34:11 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 7 22:34:11 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 8 09:45:43 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 8 09:45:43 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 8 09:45:43 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 8 21:02:26 Tower dhcpcd[983]: eth0: renewing lease of 192.168.1.217 Dec 8 21:02:26 Tower dhcpcd[983]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Dec 8 21:02:26 Tower dhcpcd[983]: eth0: leased 192.168.1.217 for 86400 seconds Dec 8 23:38:31 Tower in.telnetd[1326]: connect from 192.168.1.160 (192.168.1.160) Dec 8 23:38:32 Tower login[1327]: ROOT LOGIN on '/dev/pts/0' from 'setsuna' Dec 8 23:39:19 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Dec 8 23:39:27 Tower last message repeated 11 times Dec 8 23:39:54 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 8 23:39:54 Tower kernel: sd 2:0:0:0: [sdc] Dec 8 23:39:54 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 8 23:39:54 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 8 23:39:54 Tower kernel: cdb[0]=0x88: 88 00 00 00 00 00 00 00 00 00 00 00 00 80 00 00 Dec 8 23:39:54 Tower kernel: end_request: I/O error, dev sdc, sector 0 Dec 8 23:39:54 Tower kernel: Buffer I/O error on device sdc, logical block 0 Dec 8 23:39:54 Tower kernel: Buffer I/O error on device sdc, logical block 1 Dec 8 23:39:54 Tower kernel: Buffer I/O error on device sdc, logical block 2 Dec 8 23:39:54 Tower kernel: Buffer I/O error on device sdc, logical block 3 Dec 8 23:39:54 Tower kernel: Buffer I/O error on device sdc, logical block 4 Dec 8 23:39:54 Tower kernel: Buffer I/O error on device sdc, logical block 5 Dec 8 23:39:54 Tower kernel: Buffer I/O error on device sdc, logical block 6 Dec 8 23:39:54 Tower kernel: Buffer I/O error on device sdc, logical block 7 Dec 8 23:39:54 Tower kernel: Buffer I/O error on device sdc, logical block 8 Dec 8 23:39:54 Tower kernel: Buffer I/O error on device sdc, logical block 9 Dec 8 23:39:54 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Dec 8 23:39:54 Tower kernel: sd 2:0:0:0: [sdc] Dec 8 23:39:54 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 8 23:39:54 Tower kernel: sd 2:0:0:0: [sdc] CDB: Dec 8 23:39:54 Tower kernel: cdb[0]=0x88: 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Dec 8 23:39:54 Tower kernel: end_request: I/O error, dev sdc, sector 0 Dec 8 23:40:10 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Dec 8 23:41:45 Tower last message repeated 7 times The last bit there is me trying to probe with smartctl (but it was already "dead" I/O errors). Syslog repeats the write errors up there for a bit longer. Reseating it I suspect will make it show up again per usual.

Hmm, I thought of that. I guess I've been focused on just having the minimum amount of drives in the device. Though, with proper backups I guess I should not be worrying so much. I already bought 3 but might return the 3rd.. I guess my best two options are (I have five bays total, but this is due for an upgrade, too): Option 1: 1) 3x4TB 2) 1x3TB Total Usable: 11TB Option 2: 1) 2x4TB 2) 2x3TB Total Usable: 10TB Option 3: 1) 2x4TB 2) 3x3TB Total Usable: 13TB Option 4: 1) 3x4TB 2) 2x3TB Total Usable: 14TB (Is 5 too many drives?) What option would you guys go for the best ratio of price / storage?

This would be a good idea if the 4TB drives didn't cost $100 CAD each. The nearest 8TB in Canada is @ http://www.newegg.ca/Product/Product.aspx?Item=N82E16822178748&cm_re=8TB-_-22-178-748-_-Product Not to mention, these are "archive" drives. Are these drives really safe to be just throwing into an array? I can always return these, that's not the problem. Though, I'd like to see what my other options are for $300CAD in terms of reliability, as well.

50GB free. I figured adding another 2TB (which would be net gain from the 4TB) + one of these 3TB back in should give 5TB total. That should be plenty more (almost double of what I have right now). Anyone else have thoughts on this?

I'm looking to upgrade to unRaid 6 (purchase a basic license), to maybe use one of those 3TB drives as well. If this migration will be easier there, then I'm open to doing that first. I read the wiki and I read that I could just pull a drive -- perform a rebuild and go from there. I would need to do this for each 3TB as I swap it for a 4TB to my understanding. Is there any easy way of doing this in one fell swoop?

Does anyone have any ideas on this?

Syslog is attached, smart reports for drives that are booted right now (one is red balled): root@Tower:~# smartctl -A /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 109 099 006 Pre-fail Always - 24294136 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2103 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 047 045 030 Pre-fail Always - 4857659502476 9 Power_On_Hours 0x0032 082 082 000 Old_age Always - 16201 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 46 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 1 1 1 189 High_Fly_Writes 0x003a 096 096 000 Old_age Always - 4 190 Airflow_Temperature_Cel 0x0022 065 057 045 Old_age Always - 35 (Min/Max 25/38) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 46 193 Load_Cycle_Count 0x0032 081 081 000 Old_age Always - 38314 194 Temperature_Celsius 0x0022 035 043 000 Old_age Always - 35 (0 20 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 3352h+32m+45.793s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 18883194096 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 221884624187 root@Tower:~# root@Tower:~# smartctl -A /dev/sdd smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 108 099 006 Pre-fail Always - 18712744 3 Spin_Up_Time 0x0003 095 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 833 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 052 052 030 Pre-fail Always - 2499759130609 9 Power_On_Hours 0x0032 082 082 000 Old_age Always - 16179 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 45 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 065 058 045 Old_age Always - 35 (Min/Max 32/38) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 45 193 Load_Cycle_Count 0x0032 078 078 000 Old_age Always - 44545 194 Temperature_Celsius 0x0022 035 042 000 Old_age Always - 35 (0 20 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 5662h+53m+08.962s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 46247931720 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 204267771471 root@Tower:~# Thanks for your help! syslog.txt

/usr/bin/tail -f /var/log/syslog Oct 14 18:11:11 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Oct 14 18:11:11 Tower kernel: sd 2:0:0:0: [sdc] Oct 14 18:11:11 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Oct 14 18:11:11 Tower kernel: sd 2:0:0:0: [sdc] CDB: Oct 14 18:11:11 Tower kernel: cdb[0]=0x8a: 8a 00 00 00 00 00 b2 57 99 a8 00 00 00 08 00 00 Oct 14 18:11:11 Tower kernel: end_request: I/O error, dev sdc, sector 2992085416 Oct 14 18:11:11 Tower kernel: md: disk1 write error, sector=2992085352 Oct 14 21:54:20 Tower dhcpcd[982]: eth0: renewing lease of 192.168.1.217 Oct 14 21:54:20 Tower dhcpcd[982]: eth0: acknowledged 192.168.1.217 from 192.168.1.1 Oct 14 21:54:20 Tower dhcpcd[982]: eth0: leased 192.168.1.217 for 86400 seconds This is on Disk #1. Am I having my disk go bad? It seems unlikely all 3 would be going bad at once but I have heard terrible things about these drives...

All I did was switch the SATA port and this happened. Strange.