Jump to content

johnnie.black

Moderators
  • Content Count

    20972
  • Joined

  • Last visited

  • Days Won

    253

johnnie.black last won the day on January 13

johnnie.black had the most liked content!

Community Reputation

2258 Hero

About johnnie.black

Converted

  • Gender
    Male

Recent Profile Visitors

6698 profile views
  1. Diags are after rebooting so we can't see what happened, check that the emulated disk is mounting correctly and if yes you can rebuild on top, or if you want to play it safer rebuild to a new disk in case something goes wrong. Before doing it it's a good idea to swap cables/slot with another disk to rule that out in case it happens again with the same disk, also good idea to update LSI firmware to latest since it's on a very old one.
  2. Disk looks perfectly healthy, please post the complete diags: Tools -> Diagnostics
  3. Like mentioned if you have Windows 10 you can copy with explorer from the array to the UD device directly, it won't use the network, just copy/paste normally.
  4. Simply overwrite them with the ones form the v6.7.2 zip and reboot.
  5. Both parity and disk1 are failing, so you can't do a standard replacement, are system notifications enable? Not usual for two disks to fail at the same time, especially on such a small array. IMHO best bet is to use ddrescue to clone disk1 and then do a new config with a new parity disk. P.S. you should also run an extended SMART test on disk3, it's showing some issues on SMART, though they appear to be old errors.
  6. Diags are just after rebooting, see here to try and catch the problem.
  7. Unraid can't spin down SAS devices, and every attempt generates the error spamming the log, disable spin down for all SAS devices (set to "never").
  8. Likely a flash drive problem, backup flash's config folder, redo flash drive and restore config folder.
  9. You can also try downgrading Unraid, different kernel, older or newer, might make a difference, if still the same with a release that was working previously there could be something wrong with the NIC.
  10. If you read above you can see we already found out what's causing the problem, Intel NIC using the igb driver, doesn't mean that everyone using it will crash, but AFAIK everyone that is having issues is using one.
  11. First NIC isn't initializing correctly, second one is: Jan 23 14:59:37 catan kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k Jan 23 14:59:37 catan kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation. Jan 23 14:59:37 catan kernel: e1000e 0000:04:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Jan 23 14:59:37 catan kernel: e1000e: probe of 0000:04:00.0 failed with error -2 Jan 23 14:59:37 catan kernel: e1000e 0000:04:00.1: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Jan 23 14:59:37 catan kernel: e1000e 0000:04:00.1 eth0: (PCI Express:2.5GT/s:Width x4) 00:30:48:62:4e:f1 Jan 23 14:59:37 catan kernel: e1000e 0000:04:00.1 eth0: Intel(R) PRO/1000 Network Connection Jan 23 14:59:37 catan kernel: e1000e 0000:04:00.1 eth0: MAC: 5, PHY: 5, PBA No: 2050FF-0FF No idea on the reason, try updating to v6.8.1, also look for a BIOS update if available.
  12. Please post the diagnostics: Tools -> Diagnostics
  13. It is, assuming you're copying large file(s), check that write cache is enable on the disk, also might try a different copy program, if you're using Windows8/10 you can copy with Windows explorer and copy will be made locally bypassing network.