Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,760

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Yes, then you just need to assign the disk with the changed name.
  2. JorgeB
    Enable the syslog server and post that after a crash, it might catch something.
  3. JorgeB
    Looks like a connection problem, and CRC errors usually point to the SATA cables, start by replacing those.
  4. JorgeB
    Assign all disks that have a mount button in UD as data, assign the two that don't have one as parity, start the array to begin a parity sync, since the disks were encrypted Unraid will ask for a new key, enter the old one twice, the disk that was rebuilding will likely show data but some (or a lot) might be corrupt depending on when the rebuild stopped.
  5. JorgeB
    It's not showing up on SMART like it usually does, but looks like the drives are formatted with protection, try re-formatting the devices with sg_utils, more info below: Feb 24 10:42:18 UNRAID01 kernel: blk_update_request: protection error, dev sdb, sector 15362376248 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
  6. JorgeB
    We can force Unraid to enable disk3 to rebuild disk2, but that will only work if parity is still valid, i.e., nothing was written to disk3 once it got disable, if you believe it's still valid you can try to rebuild using a new disk, even if it's not successful it won't make things worse, unless another disk fails during the rebuild.
  7. JorgeB
    You don't, you just need a key (without password) and for that key to exist in both servers, the key you're using has a password.
  8. JorgeB
    Like mentioned you don't need to input any password for rsync with SSH keys (without pass in the keys), I use it everyday.
  9. JorgeB
    Correct. Not possible, because you only have single parity and already have a disable disk, you can use ddrescue on disk2 to recover as much data as possible then do a new config with the clone and the remaining disks to re-sync parity, note that since it's not clear for how long disk3 has been disabled any data written to the emulated disk will be lost after the new config.
  10. JorgeB
    That suggests you created an SSH key with a password, if there's no password and it exists on both servers it won't ask for one. https://phoenixnap.com/kb/setup-passwordless-ssh
  11. JorgeB
    Yeah, but at least we still need to know which one was parity1, parity2 can be synced later if array disk order isn't known.
  12. JorgeB
    Diags are after rebooting, so not much to see, other than filesystem corruption on disks 4 and 9.
  13. JorgeB
    Happy to confirm it's finally fixed.
  14. JorgeB
    We can force Unraid to rebuild the same disk again, but only if you know all the old assignments, and what disk was being rebuilt, if you don't know you can still recover most of the array except the disk being replaced, maybe can still get some data from the old one if not completely dead.
  15. JorgeB
    Not enough info posted, do you known the disk assignments? Single or dual parity? What disk was being replaced? If you know the answer to those then also post the diagnostics.
  16. JorgeB
  17. JorgeB
    This doesn't matter, what does is the test result: SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 47825 - In this case it passed.
  18. JorgeB
    Maybe, it's worth looking at.
  19. JorgeB
    Unraid driver is crashing, this sometimes happens with some hardware/kernel combinations, suggest going back to v6.9.2 then try rc3 when available, since it will use a much newer kernel it might not have the same issue.
  20. JorgeB
    If you mean it's rebooting on its own this is usually hardware related and unlikely to leave a trace in the log, still you can enable the syslog server and post that together with the full diagnostics after it does it.
  21. JorgeB
    I would recommend this.
  22. JorgeB
    No, but a few sync errors after a parity check would be expected if the errors are bad/frequent enough.
  23. JorgeB
    Feb 24 02:08:38 tmedia kernel: BTRFS info (device sdf1): forced readonly Corruption on the cache filesystem, best bet is to backup and re-format.
  24. JorgeB
    Cache filesystem is corrupt, yoy should back up and re-format, but if this keeps happening it could point to a hardware problem. This is the docker image, Unraid can't write to it, just a consequence of the pool filesystem going read-only.
  25. JorgeB
    Yes let that one finish, you can then try with just one of them first, but doing a new config should be enough.
×
×
  • Create New...