Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Even if you don't copy /config/shares it will keep your data, but with that it will also keep the share settings.
  2. Try booting in CSM/legacy mode, i.e., no UEFI.
  3. FYI it's been reported that this fixes the 980 temp issue, though not sure why it helps: https://forums.unraid.net/bug-reports/stable-releases/6103-samsung-980-temp-warning-r2007/?do=findComment&comment=20180
  4. Check/replace cables on disk7, both power and SATA to see if those ATA errors go away, disk looks OK.
  5. You are using an Asmedia controller with a SATA port multiplier, those are not recommended, not surprisingly disk4 is connected there, suggest you replace that with a recommended model before attempting any more rebuilds.
  6. Like mentioned post the diags but you should be able to do a new config to make Unraid accept the new disk to rebuild the missing one, as long as parity is valid.
  7. It's the other device this time, and since they are different brands it suggest it's not a device issue. That won't help, this is a hardware related issue, look for a BIOS update for the board, I also usually suggest a different m.2/pcie slot if available, but since both dropped that's also unlikely to help.
  8. I posted above that using just SMB2 enables 2.10 Though because of the 2.002 issue or bug I didn't think 2.02 would work, but glad it does.
  9. Post new diags after rebooting and the output of fdisk.
  10. Dashboard CPU usage includes I/O wait, use htop to see just CPU, it should be lower.
  11. It does work, and is one of the recommend controllers. It should be fine for a basic NAS/dockers Unraid server, it later you'd like to run some VMs you might want to do some upgrades.
  12. That looks correct, please reboot in case there's something still in RAM about the old layout.
  13. Do the movies go directly inside the Movies share or do you have a subfolder, like genre, resolution, etc? If not still check the next one you do if the folder exists there.
  14. Very strange, post again the output of: fdisk -l /dev/nvme1n1
  15. Movies share is set to split level one, split level overrides allocation method, so if the folder already exists on disk8 it will go there.
  16. Possibly, assuming it was using the default raid1 profile, and if yes you can try on just one device, the other one will have the same data.
  17. Now post the output of fdisk -l /dev/nvme1n1
  18. All shares are under /mnt/user, you can rename the shares or move them inside other ones, e.g., appdata could be moved for example inside the system share, and it would then be /mnt/user/system/appdata
  19. No, it's not related at all, no valid btrfs filesystem is being detected on those devices at boot, it means they doesn't exist, because they were wiped or damaged, in this case likely damaged by the RAID controller, which likely damaged the MBR for the devices and destroyed the filesystem superblock that exists in the beginning of the devices.
  20. Run it again with the array stopped and post the output.
  21. With the array stopped completely wipe the device with: blkdiscard -f /dev/nvme1n1 Then start array and re-format, that should fix it.
  22. (path: appdata/plex/Library/Application Support/Plex Media Server/Media/localhost/b/f670656af31cc2920ab8d8918bd81f105ae352a.bundle/Contents/Chapters/chapter3.jpg) This is currently the only corrupt file, delete/restore from backups and the pool should be fine for now, but if you get more corruption there's likely an underlying hardware issue, you can also take a look here for better pool monitoring. .
×
×
  • Create New...