Jump to content

JorgeB

Moderators
  • Posts

    67,812
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. It is in a pool, possibly by mistake, but that's what btrfs reports, if you don't have the other device and the pool was redundant you can still mount it manually using the degraded option here, if not to both not much more you can do.
  2. Tools -> New config -> Keep all assignments -> Apply Then start array.
  3. sdj is the existing disk, you're missing the other one, that's the one where you need to run the command, not the one being found.
  4. sdt and sdr are from a different pool: The missing disk should show in 'btrf sfi show' independent of UD, if it doesn't it's not being detected by btrfs scan, IMHO either that disk is not connected or the superblock was delete or is invalid.
  5. You can try this in case it was wiped or the superblock got damage for some reason: btrfs-select-super -s 1 /dev/sdX1 Replace X with correct letter, if the command succeeds post output of btrfs fi show again
  6. You can use for example midnight command (mc on the console), then browse to /mnt/cache
  7. That lists the various btrfs filesystem, last line is that pool, and as you can see there's a device missing, do you know which disk it was? is it connected?
  8. Filesystem is detecting multiple issues, recommend backing up and restoring after re-formatting.
  9. Still missing: Jul 14 13:09:28 Jiraiya kernel: BTRFS error (device sdj1): devid 2 uuid c7264057-941e-45fd-895a-f3329a76976f is missing Post the output of btrfs fi show
  10. Very bad idea, don't recommend more than 4/5 HDDs per cable.
  11. If you mean there are 12 drives using the same cable from the PSU it's likely a problem.
  12. Filesystem went read-only to avoid writing corrupt data, rebooting should fix it but this usually indicates a hardware problem or some other kernel memory corruption.
  13. There is*, but note that the OS will be in a crash consistent state, i.e., if you restore that backup it would be like if the plug was pulled, I take daily snapshots with the VMs running but also try to at least once a week create a snapshot with the VMs off/hibernating, this way I have more options. * Edit to add - not sure if the plugin supports that, but it's possible with btrfs snapshots.
  14. Data is in raid0, probably a btrfs issue, does not always calculate correct spaces for pools with different size devices, but all the space should be usable. Since Unraid supports a lot of pools I would recommend using smaller pools, i.e., I also do some "farming" and have for example 6x1TB, 5x2TB, 3x3TB, 2x8TB, etc, they all have a share called plots, so no need to add each pool separately to Chia and it's much easier to manage, also if there's a disk problem you only lose one pool.
  15. I can't see unassinged devices number in the diags, but since there's only one unassigned disk I assume it's the 6TB Seagate, if yes the disk looks OK, so just mount it UD and if all looks good format disk 14 and copy the data over.
  16. Nothing obvious, some OOM errors and kvm related call traces so you might see if the issue doesn't occur if the VM(s) is(are) not running.
  17. Then probably something went wrong with the rebuild, do you still have the old disk?
  18. Enable the syslog server and post that together with the diagnostics after the next crash.
  19. Anything on cache won't be covered by parity, also note that parity doesn't protect against file system corruption.
  20. Yes, but you'll need to start over. Check filesystem on cache.
×
×
  • Create New...