skimmilk5

Members
  • Posts

    6
  • Joined

  • Last visited

skimmilk5's Achievements

Noob

Noob (1/14)

0

Reputation

  1. On the Dashboard, under the Array section, a critical error is displayed stating "Array has N failed device" if the parity is invalid (where N is the number of parity disks), regardless of the device's actual health. On an initial parity sync of a new array, the error message should be that the parity is invalid, not that a device has failed. A failed device insinuates a drive has failed. Steps to recreate the issue: 1. Configure a new Unraid installation as default. This particular installation case has four drives: two 3TB drives and two 2TB drives. 2. Under the Main tab, configure one of the 3TB drives as the parity drive. Configure the other three drives as data drives. 3. Start the array. (The parity drive will be formatted at this point, as expected.) 4. Confirm disk formatting and format the data disks. 5. When the disk formatting completes, start the first parity sync operation. 6. Go to the Dashboard and find the Array section. Parity status reads "invalid," and a critical error message stating that the array has 1 failed device is displayed in red. SMART status for the disk reads "healthy." Expected behavior: 1. Configure a new Unraid installation as default, configure the parity drives and the data drives, start the array, and format the data drives. 2. When the drive formatting completes, start the first parity sync operation. Confirm that the parity drive is in a vulnerable state (amber exclamation next to that disk). 3. Go to the Dashboard and find the Array section. Parity status should read "invalid", and a warning message stating that the array is vulnerable is displayed in amber. SMART status for the disk reads "healthy."
  2. I'd like to bond some ports over LACP. I have a two-port NIC, and each port operates at 1GbE. Both ports go to a HP ProCurve switch. I'd like to use LACP to bond these two ports together, but I don't know what setting would be best to use in unraid. Currently, the ports are set active-backup (1), which gives me a maximum of 1Gb. I've already bonded the ports on the switch side by trunking them together and setting the bonding mode to LACP. I'm not sure whether I should use balance-rr, 802.3ad, balance-tlb, or balance-alb. I've been suspecting 802.3ad, since I'm working with a switch with LACP, but can someone explain if my thinking is flawed?
  3. I recently upgraded one of my drives from a 3TB to an 8TB drive according to Unraid's documentation. When I went to start the parity rebuild, I saw that my speeds were absolutely awful (10-20 days estimated)! What's going on? pikachu-diagnostics-20200201-0705.zip
  4. Awesome, so I can just move over the storage drives, move over the cache drives, move over the boot stick, and bipity-boppity-boop, everything should just work?
  5. I was wondering (it might already be answered) if I need to do anything special before or after I migrate my data from one server to another. Here's the story. I'm currently using a HP Microserver Gen7, and I'm planning to migrate the drives (all four storage drives, the cache drive, and the boot USB drive) over to a new server. I know that the license key is stored based on the USB drive's identifier itself, but I don't know about whether the drives are in any particular order or whether I need to run any special operations before or after I move everything over. I know that I'll be running a parity check afterwards, though. Thanks!