Jump to content

JorgeB

Moderators
  • Posts

    67,681
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. You should post the complete diags, in case there are known issues with that hardware, you can also enable syslog mirror to flash then post that log after a crash.
  2. Array can be online as long as the disks are not actively in use, some reads/writes won't delay the test by much, but it it's being used constantly then it can take much longer.
  3. I would prefer to be on site, but if you have notifications enable to be able to cancel the rebuild if anything goes wrong it should be fine.
  4. The previous SMART test was interrupted, this is not a disk problem, make sure the disk is set to not spin down during the test.
  5. But if the disks are being used it will pause the test.
  6. That's fine, just make sure the current PSU is standard ATX, many Dell computers use a custom PSU.
  7. Agree, rebuild first, then repair filesystem on all the disks that need it, then compare data between the UD disk and disk1.
  8. You should replace/swap cables and rebuild the disabled disk on top, as long as the emulated disk is mounting and contents look correct.
  9. Jul 30 07:44:05 nasofbadi kernel: sd 7:0:7:0: Power-on or device reset occurred ... Jul 30 07:44:48 nasofbadi kernel: sd 7:0:6:0: Power-on or device reset occurred This happened to both basically at the same time, it's usually a connection/power problem, start by checking if those two disks have anything in common, other than the controller.
  10. Can't add much other than it's also enable for me in Unraid, as long as it's enable in the board BIOS.
  11. Disk looks healthy, start the array to see if the emulated disk is mounting and contents look correct, if yes you can rebuild on top, good idea to replace/swap cables just to rule that out if it happens again to the same disk.
  12. I missed you were running without parity, you don't need a new config to add another disk, you can just add it and copy the data from disk2 there, there will likely be at least one file it will fail to copy, possibly more, after that do a new config to remove disk2.
  13. That's expected as mentioned above, and if the disk was rebuilt on top of the old one not much you can do now, you should have canceled the rebuild as soon as there were errors on a different disk. To move forward you need to fix filesystem on those disks, for the disks with a resiser fs that mention this: that's what you need to do, run it again with --rebuild-tree, it's going to take a few hours for each disk.
  14. SMART test failed, so the disk should be replaced.
  15. There's no avoiding that, Unraid needs to format any array/pool drive before use.
  16. Enable syslog mirror to flash then post that log after a crash.
  17. Enable syslog mirror to flash then post that log after a crash.
  18. The quoted syslog mentions that the problem is the fiber module you're using in that port, it's not supported by the NIC.
  19. I moved your earlier post to the correct section: Please don't double post.
  20. v6.8.x should be the same as v6.7.x for that, v6.9.x has has some changes to decrease those writes, one of them requires the pool to be reformatted.
×
×
  • Create New...