Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,831

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Enable the syslog server and post that after a crash.
  2. JorgeB
    Easiest way is to remove the partition with the UD plugin, click on the red x, disk must be unassigned and array started without it first.
  3. JorgeB
    That's fine, no need to change that one, problem is only with parity.
  4. JorgeB
    For parity and just one data drive Unraid uses basically raid1.
  5. JorgeB
    Starting some time ago Unraid uses sector 2048 for flash devices, and from that time if a device, disk or SSD, has a partition starting on sector 2048 it will use, it should create a new one for disks, solution it to wipe the disk/delete the partition and re-sync parity, once it's done you can add the new data disk.
  6. JorgeB
    Mostly likely parity has the partition starting on sector 2048, please post output of: fdisk -l /dev/sdb
  7. JorgeB
    Looks like a disk problem, run an extended SMART test on disk5 to confirm.
  8. JorgeB
    Something else is still reading from that drive.
  9. JorgeB
    Please post the diagnostics.
  10. JorgeB
    Disk4 dropped offline, could be a controller problem, SASLP is not recommended for a long time, but since there's no SMART report power cycle the server (just rebooting might not do it) and post new diags.
  11. JorgeB
    No you cannot, it's as mentioned above.
  12. JorgeB
    This is a board issue, since it's posting in safe mode first thing to try is to reset the BIOS to defaults.
  13. JorgeB
    Once it's disabled it must be re-synced: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  14. JorgeB
    OK for now, just see if it happens again, issue usually happens mostly when the controller is under heavier load.
  15. JorgeB
    You can do this now.
  16. JorgeB
    Same as here: https://forums.unraid.net/topic/111161-pcie-errors/?do=findComment&comment=1013378
  17. JorgeB
    Avoid USB, if you want to do it reliably use a SAS HBA connected to a SAS enclosure/expander.
  18. JorgeB
    Cache2 dropped offline: Aug 23 21:49:46 BIGDADDY kernel: ata1: hard resetting link Aug 23 21:49:51 BIGDADDY kernel: ata1: COMRESET failed (errno=-16) Aug 23 21:49:51 BIGDADDY kernel: ata1: reset failed, giving up Aug 23 21:49:51 BIGDADDY kernel: ata1.00: disabled Aug 23 21:49:51 BIGDADDY kernel: ata1: EH complete And it's not the first time, check/replace cables, then run a scrub and check all errors were corrected, see here for more info and better pool monitoring.
  19. JorgeB
    The link above explain how to get them on the console.
  20. JorgeB
    Yes.
  21. JorgeB
    Just click on the link.
  22. JorgeB
    This is basically useless, only if there's a failing NOW SMART attribute it will show failed.
  23. JorgeB
    No it didn't: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 40% 58360 10844215632 Disk should be replaced
  24. JorgeB
    This appears to be the problem, no link on the NIC, but full diags would have been better.
  25. JorgeB
    Yes, it's automatic.
×
×
  • Create New...