Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,416

  • Joined

  • Last visited

  • Days Won

    705

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Screen goes blanc after a few seconds, try pressing a key, if nothing appears you'll need to force a reboot.
  2. JorgeB
    And you're sure no fs corruption was found on that disk? You can post the reiserfsck output, you can also try mounting that disk manually to confirm that is the problem: mkdir /temp mount -o ro /dev/sdX1 /temp Replace X with the correct letter, note the 1 after the device, i.e., sdc1 If it works unmount with umount /temp
  3. JorgeB
    You don't have console access (like keyboard/monitor or IPMI) or console isn't working?
  4. JorgeB
    Diags are after rebooting so we cant see what happened, but disk look fine so you can re-enable the drive , recommend replacing/swapping cables first to rule them out if it happens again.
  5. JorgeB
    Like mentioned if you just started the array it's balancing, wait for cache activity to stop.
  6. JorgeB
    It's showing 240GB usable, so it's not a mirror, or screenshot was just after adding it and it's still balancing, if yes wait for balance to finish.
  7. JorgeB
    Since the LSI has a BIOS check if the disks are being detected there, if they not detected there they also won't be on Unraid, you might need to enable legacy boot on the board for the LSI BIOS to load. Only one NVMe device is being detected, check board manual, using some PCIe slots might disable other functions.
  8. JorgeB
    No. No (assuming the LSI is not a RAID controller) Device names can change but don't matter for Unraid.
  9. JorgeB
    Do you have console access? If yes type "diagnostics" and upload them here.
  10. JorgeB
    I think you already provided enough details, the most important thing is if LT can reproduce it, I for example can't.
  11. JorgeB
    You need to re-enable it: https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  12. JorgeB
    That was a different issue, arrays writes starved reads, it was an easily reproducible problem (see bug report) and it affected everyone, unlike your issue, while it might be a bug it doesn't affect most people so also not easy to reproduce by LT.
  13. JorgeB
    That specif issue was fixed on v6.8.x
  14. JorgeB
    Also see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  15. JorgeB
    Seagate drives use a multibit value for that (and a few others) attribute, you can't just look at the RAW value totals: https://forums.unraid.net/topic/86337-are-my-smart-reports-bad/?do=findComment&comment=800888
  16. JorgeB
    Swap cables (both) or slot with another disk and try again.
  17. JorgeB
    Disk is OK for now, but any more errors I would replace it, run a correcting check now, if there are sync errors run another one after that, if there are still sync errors on the 2nd run post new diags (without rebooting).
  18. JorgeB
    Diags are after rebooting so we can't see what happened, my first guess would be the not so uncommon SATA controller problem with Ryzen based boards. Parity looks fine, so check filesystem on disk2 and re-sync parity, if it happens again make sure to grab diags before rebooting.
  19. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  20. JorgeB
    Looks like a controller problem, It also dropped one of your unassigned disks, Marvell controllers are not recommended, also see here for better pool monitoring.
  21. JorgeB
    You need to have at least one data device assigned to the array, but it can be anything, like a small flash drive.
  22. JorgeB
    Not without the diagnostics, also careful with btrfs check --repair, it should only be used if told to do so, or it might make things even worse.
  23. JorgeB
    Need diags
  24. JorgeB
    If after a correcting check you get more sync errors (without an unclean shutdown) first thing to do is to run memtest.
  25. JorgeB
    If you're sure which drive is parity just check "parity is already valid" before starting the array.
×
×
  • Create New...