JorgeB

Moderators
  • Posts

    60402
  • Joined

  • Last visited

  • Days Won

    630

JorgeB last won the day on March 25

JorgeB had the most liked content!

Retained

  • Member Title
    On vacation, back in a week or so

Converted

  • Gender
    Male

Recent Profile Visitors

43879 profile views

JorgeB's Achievements

Grand Master

Grand Master (14/14)

7.4k

Reputation

3.1k

Community Answers

  1. Were those disks unmountable before? Disk3 is filling up the log with ATA errors, try swapping cables with another disk to confirm if it's really failing and post new diags.
  2. Log does not show the array starting, so not much we can see, try starting the array in maintenance mode, if it still crashes it's likely hardware related.
  3. If OK then convert the pool to raid1, once done you can remove the device and the pool will automatically be converted to single.
  4. Try re-starting the array, the pool should mount now.
  5. If I understood correctly both devices were assigned to the array, in the array, each device is a separate filesystem, you only need that one. P.S. based on the pool name that disk was initially disk2, not disk1.
  6. AFAIK this is fatal, no way to recover the pool, you will need to destroy and recreate from a backup, or use a file recovery tool like UFS explorer to see if it can recover the data.
  7. Type N and enter to keep the signature, then type write followed by enter, post new output of btrfs fi show
  8. This is not correct, the OS boots from a separate device, though you can use a redundant mirror.
  9. Type sfdisk /dev/nvme1n1 then type 2048 and enter, post the results
  10. No estoy seguro de lo que quieres decir, la paridad no tiene un sistema de archivos
  11. Mar 28 21:06:01 Sunraid elogind-daemon[1159]: Power key pressed. Mar 28 21:06:01 Sunraid elogind-daemon[1159]: Powering Off... Mar 28 21:06:01 Sunraid elogind-daemon[1159]: System is powering down.. Mar 28 21:06:01 Sunraid shutdown[12235]: shutting down for system halt Mar 28 21:06:01 Sunraid init: Switching to runlevel: 0 Did you press the power key?
  12. Disk was already disabled at boot so we can't see what happened, if it happens again grab the diags before rebooting, also it may be worth replacing/swapping cables to rule that out in case it happens again.
  13. Check filesystem on the emulated disks 9 and 12, also post the complete diagnostics.
  14. Please post the diagnostics