Jump to content

JorgeB

Moderators
  • Posts

    67,797
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. It's running out of RAM, you'll need to limit resources or add more RAM.
  2. Try with just one DIMM at a time and see if those hardware errors go away.
  3. Since both disks are still reporting disk problems on the onboard SATA suggest you run an extended SMART test on both, quite weird but looks like both disks failed.
  4. No, that's an impossible speed, likely the check is just accounting for the last time it an, but considering the full parity size for the speed average.
  5. You can use a Windows PC, just copy all the contents, though what really matters is the config folder.
  6. Make sure board has the latest BIOS, also if booting UEFI try CSM, or vice versa.
  7. Not a network guy but pretty sure you should only have one gateway, remove the gateway from eth1 and try again.
  8. That's usually a flash drive problem, backup current one and recreate it manually or using the USB tool.
  9. That's the correct way forward, but depending on the controller used with the Dell there might also be issues with the partitions, especially if it was a raid controller, you can still do it, but if the disks don't mount due to an "invalid partition" error don't do anything else and post the diagnostics.
  10. That error is not about the key, please post the diagnostics.
  11. Both disks are reporting a problem, though SMART looks healthy, they are connected to a controller with a SATA port multiplier, and it's a Marvell, two things that can cause issues on their own, worse when they are together, connect those 2 disks and disks 2, 5 and 7 (the other ones connected to the port multiplier) to the Intel SATA ports which are not being used and post new diags.
  12. As long as it doesn't start crashing again you don't need to do anything, all disks should mount except disk4 that will need to be formatted, if they don't post new diags.
  13. There's a failing NOW attribute (reallocated sector count), that would be reason enough to replace, but there are also other bad attributes: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 5 Reallocated_Sector_Ct PO--CK 140 140 140 NOW 1785 196 Reallocated_Event_Count -O--CK 176 176 000 - 24 197 Current_Pending_Sector -O--CK 200 200 000 - 2 198 Offline_Uncorrectable ----CK 200 200 000 - 2 200 Multi_Zone_Error_Rate ---R-- 197 197 000 - 1318
  14. Yes, SMART looks real bad, before it wasn't visible since the disk dropped but I should have asked for a SMART report after rebooting, in any case you need to replace that disk.
  15. You'll need to replace the flash drive, to get the array up see here: https://wiki.unraid.net/Manual/Changing_The_Flash_Device#What_to_do_if_you_have_no_backup_and_do_not_know_your_disk_assignments
  16. Virtualizing Unraid is not officially supported, doesn't mean you cannot do it, but some things might not work as expected, I missed you were doing it, though I didn't know it would interfere with udev.
  17. Some strange crashes, including the Unraid driver, rebooting should fix the problem for now.
  18. Could be either, if issues persist after replacing the cables it could also be be a PSU/controller problem.
  19. If the server power downs it's likely a hardware problem, possibly temp or PSU related.
  20. Jul 3 14:23:37 Tower kernel: e1000e: probe of 0000:00:19.0 failed with error -3 NIC is failing to initialize, try updating to v6.10.3 to see if there's any difference.
  21. Usually it won't be detected, you can post the diagnostics to check.
  22. Btrfs restore already looks for super backups, but likely all the superblocks will have the same problem in this case.
  23. Diskspeed is read only test, best to just test form another PC, assuming you have 10GbE or better.
×
×
  • Create New...