Jump to content

JorgeB

Moderators
  • Posts

    67,582
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Both layouts exist, sould be fine, assuming it's genuine, but the same goes for the first one.
  2. Though I guess it could be okay if you use the two ports not from the same port multiplier, but never tested that, and it can't be any two ports.
  3. That is expected, once a disk gets disabled it needs to be rebuilt. The latter, if you can get one soon I'd hold off on the rebuild until then.
  4. That suggests a hardware issue, one other thing you can try it to boot the server in safe mode with all docker/VMs disable, 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.
  5. That's not normal, unless you're using reisefs and it was replaying the journal.
  6. Boot using the GUI mode and check your network settings, if you can't find problem grab and post diagnostics.
  7. That controller is just 2 ports with SATA port multipliers, you should get rid of rid or you'll have constant issues with it, see here for a list of recommended ones. Diags only show disk1 as disable, and Unraid never disables more disks than parity devices (exception is if one disk fails during the rebuild of another), reboot and post new diags.
  8. The usual recommendation is 24H, though in most cases if there's a problem a few hours are usually enough to find it.
  9. Basically yes, I guess because it was raid0 and if the device wasn't always available during the balance there might have some leftover data, but it would be partial and incomplete data.
  10. I don't see how that can be, but if you can access that data you can try to copy it elsewhere, there's no way I know of to re-add that device to the pool without deleting any data there. Yes, but the metadata is raid1, and system should be the same, you can correct that at any time.
  11. From the log the NVMe device was removed form the pool (and the pool rebalanced): Feb 19 20:30:15 wahkiacusspart kernel: BTRFS info (device nvme0n1p1): device deleted: /dev/nvme0n1p1 That device now has no pool data, you want to add that device back? Also and strangely system profile is not running in raid1, only single, you should re-balance to raid1 btrfs balance start -sconvert=raid1 /mnt/cache
  12. So what does this mean? Snapshots are not automatic, and for now there's no way to do it using the GUI, only manually.
  13. Feb 17 21:02:41 Schirmer-NAS kernel: usb 3-4: USB disconnect, device number 3 Feb 17 21:02:41 Schirmer-NAS emhttpd: error: get_key_info, 542: No such file or directory (2): opendir: /boot/config Feb 17 21:02:41 Schirmer-NAS emhttpd: Unregistered - missing key file (ENOKEYFILE2) Feb 17 21:02:41 Schirmer-NAS kernel: usb usb3-port4: couldn't allocate usb_device Flash drive dropped, if using a USB 3.0 port try a 2.0 instead, could also be a failing drive.
  14. New config won't preserve any data in the emulated drive, if you don't want to rebuild that drive with a different disk first move all the data from the emulated disk to others then do the new config (you'll need to re-sync parity).
  15. Try this and then post that log after a crash.
  16. If you stop the plex docker does the CPU go back to normal?
  17. Like mentioned above array start and unmountable disks are completely unrelated, you can start the array with all disks unmountable, in fact you can only format a disk after array start, so when you format it the array must have been running.
  18. Also run memtest, multiple programs are segfaulting.
  19. Formatting would never be the thing to do but did you format that device outside the pool or the pool itself? If you still dind't reboot after that please post the diagnostics. Where were you storing the snapshots?
  20. Yeah, just remove that attribute form the ones that are monitored for that device.
  21. Like mentioned the old disk can only be re-assigned after the new config, rest of the steps are correct.
  22. That issue is not exclusive to shucked drives, it's the SATA PWDIS feature, which can be present in some newer disks.
×
×
  • Create New...