JorgeB

Moderators
  • Posts

    61363
  • Joined

  • Last visited

  • Days Won

    644

Community Answers

  1. JorgeB's post in Advice for extension was marked as the answer   
    For the moment, and between the two, I would recommend btrfs for the array, since there's a known performance issue with zfs writes, this does not affect zfs pools.
  2. JorgeB's post in Disks Keep Disabling was marked as the answer   
    It's not logged as a disk problem and SMART looks fine, do the disks share anything? Like a power splitter? If not I would swap cables/slots with other disks and see where the problem follows.
  3. JorgeB's post in Unraid 6.12.9 - Issues browsing smb shares was marked as the answer   
    Upgrade to 6.12.10
  4. JorgeB's post in Upgraded H/W - ASUS B560-Plus reboots into BIOS - not Unraid was marked as the answer   
    Put the flash drive in a PC and
     
  5. JorgeB's post in Array has 2 failed devices after unclean shutdown was marked as the answer   
    Yes, the GPU must be installed, you then select it in the VM config, click the VM and then edit.
  6. JorgeB's post in How to re add a cache drive that had a failed cable? was marked as the answer   
    It shouldn't matter is it was a previous pool device, it will be wiped first, there will be a "all data on this device will be deleted" when you add it to the pool.
     
    It's easy, but btrfs raid5/6 is not really recommend, I would recommend using zfs raidz instead, of course that would require that you backup and re-format the pool.
  7. JorgeB's post in 2 drives not showing as installed, please help recover was marked as the answer   
    Both disks look mostly OK, most likely it was a power connection issue, if the emulated disks are still mounting and contents look correct, you can rebuild on top:
     
    https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself
     
     
  8. JorgeB's post in Three servers on 6.12.9 drives no longer sleep after upgrade from 6.12.8 was marked as the answer   
    Try disabling and re-enabling spin down, if it doesn't do anything it suggests something is keeping the drives up, so it never tries to spin them down.
  9. JorgeB's post in Can't change server name in unraid connect was marked as the answer   
    Log out from Connect and then log back in.
  10. JorgeB's post in Ooof, This doesn’t look good and not quite sure what to do. Multiple drives “lost” was marked as the answer   
    If you mean to then rebuild disk12, there's a way, but it will only work if parity is still valid, it won't hurt to try though:
     
    -Tools -> New Config -> Retain current configuration: All -> Apply
    -Check all assignments and assign any missing disk(s) if needed, including the new disk12, 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 disk12
    -Start array (in normal mode now) and post new diags.
  11. JorgeB's post in Unraid 6.12.8 Checking for tg3 driver and IOMMU enabled was marked as the answer   
    This is a non issue since 6.10.3
  12. JorgeB's post in My VM Disk is stored on my main ZFS pool despite setting it to cache? was marked as the answer   
    Choose cache as primary and then change mover action from array to cache, it's in the link above.
  13. JorgeB's post in After rebuild from unmountable disk, data was not restored; major data loss. (v6.12.9) was marked as the answer   
    Unmountable disk is usually fixed by check filesystem, not by replacing the disk, that will just rebuild another unmountable disk, but I don't see any unmountable disk in your diags, did you format it?
  14. JorgeB's post in Uh oh, disk3 has read errors... was marked as the answer   
    It's not logged as a disk problem, and SMART looks fine, a lot of CRC UDMA errors so the SATA cable would be the main suspect.
     
    P.S. lots of OOM errors logged, they appear to be caused by Frigate.
  15. JorgeB's post in Appdata not a dataset even though it's on a ZFS cache pool drive was marked as the answer   
    That won't create a dataset, it would have if you had used the mover for example, like you mentioned the plugin can convert it to a dataset for you, or use the mover to move to the array, then back to cache.
  16. JorgeB's post in 2 Disks went DSBL at the same time was marked as the answer   
    Due to all the log spam the start of the problem is missing, but looks like a HBA problem, reboot and post new diags after array start.
  17. JorgeB's post in [6.12.8] Log full of "SATA link down (SStatus 0 SControl 310)" on ATA1 "Flash Boot USB" was marked as the answer   
    ATA1 is not the flash drive, it should be the device connected to first motherboard SATA port.
  18. JorgeB's post in SysDrives issue was marked as the answer   
    Known issue, v6.12.10 should be out soon with a fix.
  19. JorgeB's post in Help needed with unclean shutdowns was marked as the answer   
    Yes, that's fine, unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  20. JorgeB's post in Data Migration Crashing was marked as the answer   
    Looks like a NIC problem:
     
    Apr  1 11:55:05 EasternEXT kernel: atlantic 0000:06:00.0 eth0: failed to kill vid 0081/1  
    Do you have a different NIC you could test with?
  21. JorgeB's post in 6.13 Beta question "Hybrid ZFS pools" - what does it mean? was marked as the answer   
    It means supporting zfs pools with cache, logs, dedup, special and/or spare vdevs.
  22. JorgeB's post in Missing Shares and VM/Dockers after multiple forced shut downs. was marked as the answer   
    If you still have appdata you can recreate the image:
    https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
    Also see below if you have any custom docker networks:
    https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
  23. JorgeB's post in 6.12.8 - Mysterious network error was marked as the answer   
    You may have a network problem, you can try deleting/renmaming /boot/config/network.cfg to go back to default DHCP and re-rest, it may also be a good idea to re-start your router, if the same it basically can only be a router or network/internet problem.
  24. JorgeB's post in SSH and WebUI not accessible after couple days was marked as the answer   
    Unfortunately there's nothing relevant logged in the latest syslog, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  25. JorgeB's post in how to check a usb stick for unraid license was marked as the answer   
    Usually the key is named for the license type, i.e.: Basic.key, Plus.key or Pro.key.