Tom_808DE

Thanks, and I do appreciate that. I was just documenting what I learned in case someone in the future has the same issue.

Thanks for the reply. You make an excellent point that there are more than just drive failure modes, I hadn't considered that. Actually this is scary, a system controller failure could take out multiple drives. But as I've read on this board, unraid isn't a substitute for backups, which is why I eventually want a second unraid system just for backups. Still, a parity error says that a bit is wrong -- but parity doesn't tell you which bit or drive, there has to be some other mechanism to point to the failure. Which was my question, I assume drives just never fail to write a bit correctly unless there is some kind of failure?

I actually figured this one out on my own eventually. I was hot swapping drives / adding drives. It seems that if there is not drive attached to a SATA when the computer is booted then the port is 'asleep'. But if there is a drive when it's boot, I can change drives as much as I want. That makes it easier load up my drives into the array incase anyone is wondering why that's needed.

I'm sure this is documented or answered somewhere but I couldn't find it. It seems that parity protection requires a hard drive failure with some kind of detected error, otherwise there's no way to repair the error. So are drives today just that reliable that they never have an undetected error?

1. Is this a forever license or just till 7.0 is released? 2. If I get a second server, can the licenses be swapped? Or even just moved? 3. If I get a second server, is it eligible for a trial license ( thinking I'd want to burn it in and then migrate) I'm all over the place in what I might do in the future, I'm pretty sure I need some sort of backup server. I might want to get a less powerful machine to be strictly a backup server, or I might get a more powerful machine and use this one as a backup server. The answers will drive what size license I will buy. Thanks!

Newbie Starting uraid on a HP Z620 server. The Z620 has 10 SATA ports, but only 6 work. How can I tell if it's a hardware issue or a driver? What seems especially odd, there seems to be 2 SATA controller chips, one labeled SCU with ports that all work, and another AHCI SATA chip with 4 3Gb/s an 2 6 Gb/s -- But its 2 of the 4 Gb/s that are working. And, I guess I'm mixing topics here a bit, but would I get noticeable performance to add a card that supports 6 Gb/s -- just thinking about the parity overhead? I originally posted that I couldn't find the logs, but here it is: (sorry for the bad format, any tips on how to fix?) an 12 13:31:07 TowerZ620 kernel: random: 7 urandom warning(s) missed due to ratelimiting Jan 12 13:31:07 TowerZ620 kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input8 Jan 12 13:31:07 TowerZ620 kernel: ACPI: Power Button [PWRB] Jan 12 13:31:07 TowerZ620 kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input9 Jan 12 13:31:07 TowerZ620 kernel: ACPI: Power Button [PWRF] Jan 12 13:31:07 TowerZ620 kernel: i801_smbus 0000:00:1f.3: enabling device (0101 -> 0103) Jan 12 13:31:07 TowerZ620 kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt Jan 12 13:31:07 TowerZ620 kernel: ahci 0000:00:1f.2: version 3.0 Jan 12 13:31:07 TowerZ620 kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k Jan 12 13:31:07 TowerZ620 kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation. Jan 12 13:31:07 TowerZ620 kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Jan 12 13:31:07 TowerZ620 kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x21 impl SATA mode Jan 12 13:31:07 TowerZ620 kernel: ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst Jan 12 13:31:07 TowerZ620 kernel: scsi host1: ahci Jan 12 13:31:07 TowerZ620 kernel: RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 163840 ms ovfl timer Jan 12 13:31:07 TowerZ620 kernel: scsi host2: ahci Jan 12 13:31:07 TowerZ620 kernel: RAPL PMU: hw unit of domain pp0-core 2^-16 Joules Jan 12 13:31:07 TowerZ620 kernel: scsi host3: ahci Jan 12 13:31:07 TowerZ620 kernel: RAPL PMU: hw unit of domain package 2^-16 Joules Jan 12 13:31:07 TowerZ620 kernel: scsi host4: ahci Jan 12 13:31:07 TowerZ620 kernel: RAPL PMU: hw unit of domain dram 2^-16 Joules Jan 12 13:31:07 TowerZ620 kernel: scsi host5: ahci Jan 12 13:31:07 TowerZ620 kernel: scsi host6: ahci Jan 12 13:31:07 TowerZ620 kernel: ata1: SATA max UDMA/133 abar m2048@0xef44c000 port 0xef44c100 irq 35 Jan 12 13:31:07 TowerZ620 kernel: ata2: DUMMY Jan 12 13:31:07 TowerZ620 kernel: ata3: DUMMY Jan 12 13:31:07 TowerZ620 kernel: ata4: DUMMY Jan 12 13:31:07 TowerZ620 kernel: ata5: DUMMY Jan 12 13:31:07 TowerZ620 kernel: ata6: SATA max UDMA/133 abar m2048@0xef44c000 port 0xef44c380 irq 35 Jan 12 13:31:07 TowerZ620 kernel: isci: Intel(R) C600 SAS Controller Driver - version 1.2.0 Jan 12 13:31:07 TowerZ620 kernel: isci 0000:02:00.0: driver configured for rev: 5 silicon Jan 12 13:31:07 TowerZ620 kernel: isci 0000:02:00.0: Unable to obtain EFI var data for OEM parms Jan 12 13:31:07 TowerZ620 kernel: isci 0000:02:00.0: OEM parameter table found in OROM Jan 12 13:31:07 TowerZ620 kernel: isci 0000:02:00.0: OEM SAS parameters (version: 1.1) loaded (platform) Jan 12 13:31:07 TowerZ620 kernel: cryptd: max_cpu_qlen set to 1000 Jan 12 13:31:07 TowerZ620 kernel: isci 0000:02:00.0: SCU controller 0: phy 3-0 cables: {short, short, short, short} Jan 12 13:31:07 TowerZ620 kernel: scsi host7: isci Jan 12 13:31:07 TowerZ620 kernel: AVX version of gcm_enc/dec engaged. Jan 12 13:31:07 TowerZ620 kernel: AES CTR mode by8 optimization enabled