JorgeB

Moderators
  • Posts

    35280
  • Joined

  • Last visited

  • Days Won

    411

Community Answers

  1. JorgeB's post in BTRFS Errors was marked as the answer   
    Btrfs check --repair should be used with much care, it might make things even worse, a btrfs filesystem can quickly go bad with RAM issues, Ryzen with overclocked RAM is known to corrupt data, you should fix data and if it were me I would then backup and recreate that filesystem.
  2. JorgeB's post in "Disk Size too small"-error with same size drive was marked as the answer   
    Unraid has the partitions starting on sector 2048 for SSDs vs 64 for disks, so there's a little less space and you can't direct replace a disk with an SSD of the same capacity, you can create a new array and manually copy the data though.
  3. JorgeB's post in Docker Service failed to start - Troubleshooting Help? was marked as the answer   
    Docker image is corrupt, delete and re-create:
    https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
     
  4. JorgeB's post in How to migrate btrfs pools between unraid installs ? was marked as the answer   
    If you mean use an existing pool in a new server you just need to assign all the pool members and start the array, existing pool will be imported.
  5. JorgeB's post in Slow read speeds over the network (but not write speeds) was marked as the answer   
    So that confirms the problem is network related, could be NIC, cable, NIC driver, etc.
  6. JorgeB's post in Disk Failure? Help needed was marked as the answer   
    It's logged more like a connection/power issue, but since it failed in a different slot it's likely a disk problem.
  7. JorgeB's post in 10gb direct connection troubles was marked as the answer   
    Jan 12 09:08:43 BadWolf kernel: mlx4_en: eth1: Link Down Jan 12 09:08:43 BadWolf kernel: mlx4_en: eth1: Link Up Jan 12 09:08:52 BadWolf kernel: mlx4_en: eth1: Link Down Jan 12 09:08:53 BadWolf kernel: mlx4_en: eth1: Link Up Jan 12 09:09:26 BadWolf kernel: mlx4_en: eth1: Link Down Jan 12 09:09:26 BadWolf kernel: mlx4_en: eth1: Link Up Jan 12 09:09:26 BadWolf kernel: mlx4_en: eth1: Link Down Jan 12 09:09:26 BadWolf kernel: mlx4_en: eth1: Link Up Jan 12 09:26:04 BadWolf kernel: mlx4_en: eth1: Link Down Jan 12 09:26:05 BadWolf kernel: mlx4_en: eth1: Link Up Jan 12 09:26:05 BadWolf kernel: mlx4_en: eth1: Link Down Jan 12 09:26:05 BadWolf kernel: mlx4_en: eth1: Link Up  
    10GbE link is constantly going up/down, try with a different cable, also note that max cable length for direct attach active cables is 10m (about 33feet).
  8. JorgeB's post in new build/status errors " Array Started•Starting services...", "docker failed to start service", cant create shares, vms: "Libvirt Service failed to start." was marked as the answer   
    You need to format the assigned devices before use, next to array start/stop button.
  9. JorgeB's post in Unmountable: Too many missing/misplaced devices: Every time... was marked as the answer   
    I can't why some devices are losing the assignments, is the log from a boot right after just moving the M.2 card?
     
    Still as a workaround you can do this:
     
    Stop the array, if Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices, re-enable Docker/VMs if needed, start array.
     
    Alternatively you can also do a new config and reassign all devices, then check parity is already valid before starting the array.
     
  10. JorgeB's post in Docker/Cache goes Read Only after 1-2 weeks uptime was marked as the answer   
    Btrfs is detecting data corruption:
     
    Jan 16 08:50:46 ZEUS kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 52, gen 0 Jan 16 08:50:46 ZEUS kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 56, gen 0  
    This is usually a RAM issue, start by running memtest.
  11. JorgeB's post in Replacing drive in a single drive array and no SATA slots left was marked as the answer   
    You can just power off, replace devices, when you power back on that pool will be empty, assign new device, start array, format new device.
  12. JorgeB's post in Storage Used was marked as the answer   
    2.2TiB = 2.42TB
     
    Not necessarily:
     
    https://github.com/shundhammer/qdirstat/blob/master/README.md
     
     
  13. JorgeB's post in Loads of errors on cache drive...how to proceed? was marked as the answer   
    Those are the monitored SMART attributes.
  14. JorgeB's post in Server boots to bios with unraid but straight to OS with windows on new hardware. Help was marked as the answer   
    Make sure you've enabled UEFI support in Unraid, either when using the USB tool or by manually renaming EFI- to EFI in the flash drive.
  15. JorgeB's post in Help understanding errors in syslog was marked as the answer   
    Those ATA errors usually mean a connection problem, but since it's both disks on a Marvell controller could also be that.
  16. JorgeB's post in Cache drive placed in unassigned devices after Unraid hang and reboot was marked as the answer   
    Just re-assign it.
  17. JorgeB's post in Adding new encrypted drive was marked as the answer   
    Not sure why you did a new config, that's not used to rebuild drives, starting the array in maintenance mode won't auto-start the rebuild but you could click on "sync" or just start in normal mode, for the encryption key you'd need to use the existing one.
     
    Now, and if parity is still valid you can do this (I never used encryption so not sure when it will ask for the key, but when it does use the old one):
     
    -You already did a new config so we continue after that
    -Check all assignments and assign any missing disk(s) if needed, including the new disk you want to rebuild, replacement disk should be same size or larger than the old one
    -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked)
    -Stop array
    -Unassign the disk you want to rebuild
    -Start array (in normal mode now), ideally the emulated disk will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk
    -If the emulated disk mounts and contents look correct stop the array
    -Re-assign the disk to rebuild and start array to begin.
     
     
  18. JorgeB's post in 6.9.2 - (n00b) Drive unmountable and reporting superblock read failed after installing 2 new drives was marked as the answer   
    Disk1 dropped offline, this is usually a connection problem but since it dropped there's no SMART report, power down, check/replace cables and post new diags after array start.
  19. JorgeB's post in (SOLVED) Slow Parity-Sync/Data rebuild roughly 300KB/sec to 1.2MB/sec was marked as the answer   
    Constant ATA errors for parity, check/replace cables.
  20. JorgeB's post in Speed issues after several hours of service was marked as the answer   
    Unraid driver crashed, try updating to v6.10-rc2
  21. JorgeB's post in Cache Poole Size Reports Correct/ Free+Used Incorrect? was marked as the answer   
    It's a known btrfs issue, it happens when there's an odd number of devices in raid1.
  22. JorgeB's post in Drive is suddenly unmountable and 2 others emulated. was marked as the answer   
    Check filesystem on disk2, then you can re-sync parities.
  23. JorgeB's post in Replacing multiple disks in array with 1 larger disk. was marked as the answer   
    This is the Unraid default for disks, parity partition starts on sector 2048, it means it was partitioned outside Unraid, recently Unraid started supporting that starting sector for SSDs so it doesn't complain, but because of that there are a few less sectors available, to resolve this you'd need to wipe that partition then let Unraid repartition it and re-sync parity.
     
     
  24. JorgeB's post in Question re Drive Assignment + Unmountable Disk Issue was marked as the answer   
    Parity can't help with filesystem corruption, the rebuilt disk would look the same.
     
    Filesystem corruption can be the result of for example an unclean shutdown or some hardware issue, like bad RAM, or just a bit flip in the wrong place, it's important to always have backups of anything important.
  25. JorgeB's post in NVME drives throwing errors, filling logs instantly. How to resolve? was marked as the answer   
    You try the below, if it doesn't help look for a BIOS update or try using different PCIe slots if possible.