Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,765

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Feb 19 17:59:48 DroidUnRaid kernel: ata1.01: HPA detected: current 976771055, native 976773168
  2. JorgeB
    SMR drives can get quite slow writing, no experience with that specific model but I do have some Toshiba P300 SMR and those can get as slow as 5MB/s for a few minutes, so keep that in mind.
  3. JorgeB
    zip doesn't unpack.
  4. JorgeB
    You should also post that.
  5. JorgeB
    The pool is completely full, this is what btrfs is reporting, and it will be correct: Pool: cache Used: 931.00GiB Free (estimated): 2.84MiB (min: 2.84MiB) Free (statfs, df): 0.00B Something is using that space, as for the mover not working shares use cache setting might not be correctly configured, or there could be other issues, you can take a look here for some common ones, but until you free up some space pool won't work.
  6. JorgeB
    Best bet is to use the appropriate container support thread/forum, you can find by clicking on it:
  7. JorgeB
    You can either rebuild the disks (assuming the emulated disks are mounting) or do a new config and resync parity, it will take about the same time.
  8. JorgeB
    Also drives will spin down on shutdown dependent on the controller connected, if for example you have 6 drives connected to an Intel SATA controller and the rest to an LSI HBA on power down you'll hear the 6 drives on the Intel controllers powering down/spinning down one by one and then the computer will power off shutting down the remaining ones on the LSI while running, either way never found it an actual issue or reliability problem.
  9. JorgeB
    Yep, since there are also issues with disks connected to the onboard SATA controller.
  10. JorgeB
    Yes, already posted that above, CSM boot must be enable.
  11. JorgeB
    You won't be able to mount the storage spaces volume with UD, you can mount the SMB Windows share and transfer the data by LAN, assuming the Windows server and Unraid server are two different computers.
  12. JorgeB
    That shouldn't be a problem, since nothing should be written to or update the MBR area.
  13. JorgeB
    OK, that controller is usually fine, firmware is also latest, for there to be an invalid partition layout error it means the MBR was changed, that's the very beginning of the disk, outside the partition to where data gets written to, so that should never happen just because of a power cut, but you're not the first, not sure what the problem is, disk or controller would be the main suspects.
  14. JorgeB
    More likely to get an answer if you use the existing docker support thread, you can go there by clicking on the docker then support:
  15. JorgeB
    Just out of curiosity what controller is that disk connected to? You can also post the diagnostics if you don't know, because what happened should never happen with just a power loss.
  16. JorgeB
    Cache2 is showing some SMART issues but should be fine for now, you can run an extended SMART test to confirm, main problem is that the pool is completely full, you need to move/delete some data from there, avoid completely filling up any COW filesystem, like btrfs or zfs.
  17. JorgeB
    I don't use encryption but it has been known to happen when there's a missing/upgraded disk. Disks are not being detected, also some issues with disk7 in this boot, so likely you have a power/connection problem, should also update the LSI firmware since it's very old. These show errors on two disks connected to the onboard SATA controller, again suggesting a power/connection problem.
  18. JorgeB
    SAS3 is backwards compatible with SAS2.
  19. JorgeB
    It's difficult to say for sure, but look for used server pulls, more likely to be genuine than for example a new one from China.
  20. JorgeB
    I already posted in this thread before, it's an elusive issue and one that I can't replicate, so don't really have anything new to add.
  21. JorgeB
    See below:
  22. JorgeB
    Feb 18 15:20:27 Marlin emhttpd: mount_pool: ERROR: superblock checksum mismatch Feb 18 15:20:27 Marlin emhttpd: mount_pool: ERROR: cannot scan /dev/sdb1: Input/output error Superblock in one of the devices is corrupt, try the recovery options here, if they don't work you might try mounting the pool with the above device disconnected, assuming it was a redundant pool.
  23. JorgeB
    If the one device drops trasn id will be out of sync, if it's a raid1 pool it will sync with a scrub, but of course that should not be a regular occurrence, or other issues might occur, the problem here is is that the superblock is also damaged, if any the recovery options work, yes, best bet is to backup and re-format the pool.
  24. JorgeB
    Disk dropped offline so there's no SMART report, but based on the log looks like a power/connection problem, and if there were CRC errors coming from that disk it's likely the SATA cable.
  25. JorgeB
    Yep.
×
×
  • Create New...