Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,125

  • Joined

  • Last visited

  • Days Won

    703

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    IIRC hdparm can't spin down SAS disks, you need sdparm, not currently included with Unraid.
  2. JorgeB
    Not currently, it's a known issue, they might in the future.
  3. JorgeB
    That's weird, try rebooting, if still the same post diags, maybe something visible there.
  4. JorgeB
    From what I gather most believe that's a non issue, while possible, both for zfs and btrfs, you'd need to have hash collision for that, and the chances of that happening are extremely low, see for example here: http://jrs-s.net/2015/02/03/will-zfs-and-non-ecc-ram-kill-your-data/ I use and strongly recommend ECC for anyone who cares about data integrity, but you're still better protected against data corruption with zfs or btrfs without ECC that would be on a non checksummed filesystem.
  5. JorgeB
    It's a btrfs limitation with raid5/6, used spaced will show correctly, available space will not account for parity, but since it still decreases with used space not much of a problem, also note that while you can use raid5/6, I use it myself, it's still less stable than other profiles, and a UPS is strongly recommended because of the the write hole issue that affects most raid5/6 implementations.
  6. JorgeB
    Looks more like a connection problem with the SSD, replace cables, if problems persist it could be the SSD.
  7. JorgeB
    The netbook I had the same problem also had little RAM, just can't be certain now if it was 1 or 2GB, but most likely only 1GB also.
  8. JorgeB
    Don't ask me how it works, I can only tell you that it worked for me on a netbook that without that wouldn't boot any release after 6.4
  9. JorgeB
    Try this, it worked for me for an identical error, on the flash drive edit syslinux/syslinux.cfg and add root=sda to the boot option you're using after initrd=/bzroot, e.g.: label Unraid OS menu default kernel /bzimage append initrd=/bzroot root=sda
  10. JorgeB
    This should have been posted on the general support forum since it's not v6.6.6 related, disks look fine, looks more like a connection issue, you're also using IDE mode which can cause problems, change the controller to AHCI in the bios, check/replace cables and rebuild the disabled disk.
  11. JorgeB
    That's likely the best way, you can also keep -a and just add the --no-perms flag, e.g.: rsync -av --no-perms etc
  12. JorgeB
    Trying to add a cache device to the pool after doing a new config and couldn't change cache slots, had to reboot. P.S. I did it again to confirm it's a bug and it works fine after a new config where all assignments are retained, it doesn't after a new config with no assignments retained.
  13. JorgeB
    The problem isn't Unraid, the problem is that you can have memory errors if overclocking the RAM with Ryzen CPUs, several cases on the forum where users were having sync errors on the parity check because of that, IMO, if you care about the data on the server, limit you RAM speeds to max officially supported without overclocking:
  14. JorgeB
    Do you have an older non UEFI computer you could use? That's what I do for all my flashing, if not wait for someone with UEFI flash experience to help.
  15. JorgeB
    Are you on latest releases? v6.6.6? If not upgrade.
  16. JorgeB
    Yes
  17. JorgeB
    Maybe the same issue as this one?
  18. JorgeB
    That doesn't mean anything, Samsung supports read zero after trim, Crucial doesn't, so for example the Samsung would work on some LSI controllers, the Crucial won't, but it will work on the onboard SATA ports.
  19. JorgeB
    Likely it's on a controller that doesn't support trim, use the onboard SATA ports for the SSD
  20. JorgeB
    For this to have any meaning you need to disable compression for the pool before testing, zeros are highly compressible.
  21. JorgeB
    Yeah, until there's a functional fsck for btrfs anytime there's fs corruption backup, format, restore should be the default action.
  22. JorgeB
    Basically btrfs --repair should only be used if told so by a btrfs maintainer or somebody else very experienced using it, and I don't consider myself one, if cache is unmountable you can use this to help with backup, reformat and restore, to really try to repair the fs you'd need to ask for help on the btrfs mailing list.
  23. JorgeB
    You should be able to delete the small partition using diskpart (command line in windows)
  24. JorgeB
    AFAIK that was never the problem, the issue is the ZFS licence.
  25. JorgeB
    That attribute wasn't monitored by the older release you were using, just acknowledge it, you only need to worry about it if it keeps increasing.
×
×
  • Create New...