January 24, 20233 yr Good morning all, Hope you are well. Earlier this morning I attempted to remove a cache drive from my pool, and then re-added it but after doing so I see the following error: Unmountable: No pool uuid Any help would be greatly appreciated, as I don't want to attempt any further steps which might create an even bigger issue. root@Phobos:~# btrfs-select-super -s 1 /dev/nvme1n1 No valid Btrfs found on /dev/nvme1n1 ERROR: open ctree failed root@Phobos:~# btrfs-select-super -s 1 /dev/nvme0n1 No valid Btrfs found on /dev/nvme0n1 ERROR: open ctree failed root@Phobos:~# Thank you for your time! phobos-diagnostics-20230124-0951.zip Edited January 24, 20233 yr by MatSalamon Added new information
January 24, 20233 yr Community Expert Post the output of btrfs-select-super -s 1 /dev/nvme1n1p1 and after that one btrfs fi show
January 24, 20233 yr Author Hi @JorgeB, thanks for the prompt response, please see outputs below: root@Phobos:~# btrfs-select-super -s 1 /dev/nvme1n1p1 warning, device 2 is missing using SB copy 1, bytenr 67108864 root@Phobos:~# btrfs fi show warning, device 2 is missing Label: none uuid: 26e0b887-b92c-4df2-ae99-87f56a96103b Total devices 2 FS bytes used 79.43GiB devid 1 size 465.76GiB used 138.03GiB path /dev/nvme1n1p1 *** Some devices missing root@Phobos:~#
January 24, 20233 yr Community Expert Did you also wipe the other device? Logs only show the one above, post output of: btrfs-select-super -s 1 /dev/nvme0n1p1 and then btrfs fi show
January 24, 20233 yr Author I certainly don't recall wiping any the the devices, they were removed from the cache pool, and then re-added without formatting. root@Phobos:~# btrfs-select-super -s 1 /dev/nvme0n1p1 using SB copy 1, bytenr 67108864 root@Phobos:~# btrfs fi show Label: none uuid: 26e0b887-b92c-4df2-ae99-87f56a96103b Total devices 2 FS bytes used 79.43GiB devid 1 size 465.76GiB used 138.03GiB path /dev/nvme1n1p1 devid 2 size 1.82TiB used 138.03GiB path /dev/nvme0n1p1 root@Phobos:~#
January 24, 20233 yr Community Expert Solution Pool appears to be reset but to make sure, stop array, unassign all pool devices, start array, stop array, re-assign all pool devices, start array, pool should mount now P.S. note that you can only remove a device from a redundant pool, and base don the data usage that is not one.
January 24, 20233 yr Author Fantastic, thank you @JorgeB, this has resolved my issue. Appreciate your support here very much!
August 16, 20232 yr I am having the same issue. Label: none uuid: b82a5048-9361-4567-b9c5-6d7d68dadbc1 Total devices 3 FS bytes used 2.18TiB devid 1 size 1.82TiB used 1.03TiB path /dev/nvme2n1p1 devid 2 size 1.82TiB used 1.03TiB path /dev/nvme0n1p1 *** Some devices missing When removing all pool drives do you click yes on the following? Does that mean I will need to create the pool again? Will the data still be in tack?
August 16, 20232 yr Community Expert 51 minutes ago, MenacingMight said: When removing all pool drives do you click yes on the following? Yes.
August 16, 20232 yr Will I need to format the drives when adding them back in? Will that result in data lose?
August 16, 20232 yr Community Expert 1 minute ago, MenacingMight said: Will I need to format the drives when adding them back in? Will that result in data lose? If you are doing a pool reset (and there's a valid pool there) the previous pool will be imported, no data will be deleted.
August 16, 20232 yr Unraid log Aug 16 09:23:05 menacingmight winbindd[5409]: [2023/08/16 09:23:05.428760, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Aug 16 09:23:05 menacingmight winbindd[5409]: Got sig[15] terminate (is_parent=0) Aug 16 09:23:05 menacingmight wsdd2[5238]: terminating. Aug 16 09:23:05 menacingmight rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="6386" x-info="https://www.rsyslog.com"] start Aug 16 09:23:07 menacingmight root: Starting Samba: /usr/sbin/smbd -D Aug 16 09:23:07 menacingmight root: /usr/sbin/nmbd -D Aug 16 09:23:07 menacingmight root: /usr/sbin/wsdd2 -d -4 Aug 16 09:23:07 menacingmight wsdd2[6604]: starting. Aug 16 09:23:07 menacingmight root: /usr/sbin/winbindd -D Aug 16 09:23:07 menacingmight emhttpd: shcmd (103): /etc/rc.d/rc.avahidaemon restart Aug 16 09:23:07 menacingmight root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Aug 16 09:23:07 menacingmight avahi-dnsconfd[5305]: read(): EOF Aug 16 09:23:07 menacingmight root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Aug 16 09:23:07 menacingmight avahi-daemon[6646]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Aug 16 09:23:07 menacingmight avahi-daemon[6646]: Successfully dropped root privileges. Aug 16 09:23:07 menacingmight avahi-daemon[6646]: avahi-daemon 0.8 starting up. Aug 16 09:23:07 menacingmight avahi-daemon[6646]: Successfully called chroot(). Aug 16 09:23:07 menacingmight avahi-daemon[6646]: Successfully dropped remaining capabilities. Aug 16 09:23:07 menacingmight avahi-daemon[6646]: Loading service file /services/sftp-ssh.service. Aug 16 09:23:07 menacingmight avahi-daemon[6646]: Loading service file /services/smb.service. Aug 16 09:23:07 menacingmight avahi-daemon[6646]: Loading service file /services/ssh.service. Aug 16 09:23:07 menacingmight avahi-daemon[6646]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.217. Aug 16 09:23:07 menacingmight avahi-daemon[6646]: New relevant interface br0.IPv4 for mDNS. Aug 16 09:23:07 menacingmight avahi-daemon[6646]: Network interface enumeration completed. Aug 16 09:23:07 menacingmight avahi-daemon[6646]: Registering new address record for 192.168.1.217 on br0.IPv4. Aug 16 09:23:07 menacingmight emhttpd: shcmd (104): /etc/rc.d/rc.avahidnsconfd restart Aug 16 09:23:07 menacingmight root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Aug 16 09:23:07 menacingmight root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Aug 16 09:23:07 menacingmight avahi-dnsconfd[6655]: Successfully connected to Avahi daemon. Aug 16 09:23:07 menacingmight emhttpd: shcmd (120): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 Aug 16 09:23:07 menacingmight kernel: loop2: detected capacity change from 0 to 2097152 Aug 16 09:23:07 menacingmight kernel: BTRFS: device fsid 6dcac20a-ec9e-401e-bad8-88f107098f71 devid 1 transid 574 /dev/loop2 scanned by mount (6700) Aug 16 09:23:07 menacingmight kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm Aug 16 09:23:07 menacingmight kernel: BTRFS info (device loop2): using free space tree Aug 16 09:23:08 menacingmight root: Resize device id 1 (/dev/loop2) from 1.00GiB to max Aug 16 09:23:08 menacingmight emhttpd: shcmd (122): /etc/rc.d/rc.libvirt start Aug 16 09:23:08 menacingmight root: Starting virtlockd... Aug 16 09:23:08 menacingmight root: Starting virtlogd... Aug 16 09:23:08 menacingmight root: Starting libvirtd... Aug 16 09:23:08 menacingmight kernel: tun: Universal TUN/TAP device driver, 1.6 Aug 16 09:23:08 menacingmight emhttpd: nothing to sync Aug 16 09:23:08 menacingmight unassigned.devices: Mounting 'Auto Mount' Remote Shares... Aug 16 09:23:08 menacingmight unassigned.devices: Using Gateway '192.168.1.1' to Ping Remote Shares. Aug 16 09:23:08 menacingmight unassigned.devices: Waiting 5 secs before mounting Remote Shares... Aug 16 09:23:08 menacingmight dnsmasq[6874]: started, version 2.89 cachesize 150 Aug 16 09:23:08 menacingmight dnsmasq[6874]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfile Aug 16 09:23:08 menacingmight dnsmasq-dhcp[6874]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Aug 16 09:23:08 menacingmight dnsmasq-dhcp[6874]: DHCP, sockets bound exclusively to interface virbr0 Aug 16 09:23:08 menacingmight dnsmasq[6874]: reading /etc/resolv.conf Aug 16 09:23:08 menacingmight dnsmasq[6874]: using nameserver 208.67.222.222#53 Aug 16 09:23:08 menacingmight dnsmasq[6874]: read /etc/hosts - 3 names Aug 16 09:23:08 menacingmight dnsmasq[6874]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 names Aug 16 09:23:08 menacingmight dnsmasq-dhcp[6874]: read /var/lib/libvirt/dnsmasq/default.hostsfile Aug 16 09:23:08 menacingmight kernel: mpt3sas 0000:08:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM Aug 16 09:23:08 menacingmight avahi-daemon[6646]: Server startup complete. Host name is menacingmight.local. Local service cookie is 2898035200. Aug 16 09:23:09 menacingmight avahi-daemon[6646]: Service "menacingmight" (/services/ssh.service) successfully established. Aug 16 09:23:09 menacingmight avahi-daemon[6646]: Service "menacingmight" (/services/smb.service) successfully established. Aug 16 09:23:09 menacingmight avahi-daemon[6646]: Service "menacingmight" (/services/sftp-ssh.service) successfully established. Logs from drives log1 Aug 16 09:22:14 menacingmight kernel: nvme2n1: p1 Aug 16 09:22:14 menacingmight kernel: BTRFS: device fsid b82a5048-9361-4567-b9c5-6d7d68dadbc1 devid 1 transid 23447 /dev/nvme2n1p1 scanned by udevd (1042) Aug 16 09:22:26 menacingmight emhttpd: Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0W124072X (nvme2n1) 512 3907029168 Aug 16 09:22:26 menacingmight emhttpd: import 33 cache device: (nvme2n1) Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0W124072X Aug 16 09:22:26 menacingmight emhttpd: read SMART /dev/nvme2n1 Aug 16 09:23:02 menacingmight emhttpd: /sbin/btrfs filesystem show /dev/nvme2n1p1 2>&1 Aug 16 09:23:02 menacingmight emhttpd: devid 1 size 1.82TiB used 1.03TiB path /dev/nvme2n1p1 Aug 16 09:23:02 menacingmight kernel: BTRFS info (device nvme2n1p1): using crc32c (crc32c-intel) checksum algorithm Aug 16 09:23:02 menacingmight kernel: BTRFS info (device nvme2n1p1): allowing degraded mounts Aug 16 09:23:02 menacingmight kernel: BTRFS info (device nvme2n1p1): using free space tree Aug 16 09:23:02 menacingmight kernel: BTRFS warning (device nvme2n1p1): devid 3 uuid a924bc51-3d8c-4f2c-8c1b-f9c23cf01411 is missing Aug 16 09:23:02 menacingmight kernel: BTRFS warning (device nvme2n1p1): couldn't read tree root Aug 16 09:23:02 menacingmight kernel: BTRFS error (device nvme2n1p1): open_ctree failed log2 Aug 16 09:22:14 menacingmight kernel: nvme0n1: p1 Aug 16 09:22:14 menacingmight kernel: BTRFS: device fsid b82a5048-9361-4567-b9c5-6d7d68dadbc1 devid 2 transid 23447 /dev/nvme0n1p1 scanned by udevd (1042) Aug 16 09:22:26 menacingmight emhttpd: Samsung_SSD_970_EVO_Plus_2TB_S59CNM0W610905R (nvme0n1) 512 3907029168 Aug 16 09:22:26 menacingmight emhttpd: import 34 cache device: (nvme0n1) Samsung_SSD_970_EVO_Plus_2TB_S59CNM0W610905R Aug 16 09:22:26 menacingmight emhttpd: read SMART /dev/nvme0n1 Aug 16 09:23:02 menacingmight emhttpd: devid 2 size 1.82TiB used 1.03TiB path /dev/nvme0n1p1 Aug 16 09:23:02 menacingmight root: mount: /mnt/vm: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. log3 Aug 16 09:22:26 menacingmight emhttpd: Sabrent_Rocket_4.0_1TB_0546070C1AF388365524 (nvme1n1) 512 1953525168 Aug 16 09:22:26 menacingmight emhttpd: import 35 cache device: (nvme1n1) Sabrent_Rocket_4.0_1TB_0546070C1AF388365524 Aug 16 09:22:26 menacingmight emhttpd: read SMART /dev/nvme1n1 Edited August 16, 20232 yr by MenacingMight
August 16, 20232 yr Community Expert 28 minutes ago, MenacingMight said: Ok I did that, but I don't think it worked. That's only for a pool reset, your pool has one or more missing devices, do you have it/them?
August 16, 20232 yr I dont know what drive it is talking about. All 3 drives are added. This problem started off similar to MatSalamon. I removed a drive from my pool and later tried to add it, but the pool wasn't working. Is there a data corruption? Edited August 16, 20232 yr by MenacingMight
August 16, 20232 yr Community Expert I assume this was a non-redundant pool? Post the output of: btrfs-select-super -s 1 /dev/nvme1n1p1
August 16, 20232 yr root@menacingmight:~# btrfs-select-super -s 1 /dev/nvme1n1p1 ERROR: mount check: cannot open /dev/nvme1n1p1: No such file or directory ERROR: cannot check mount status: No such file or directory This is the drive I removed and tried to readd. Edited August 16, 20232 yr by MenacingMight Added more info
August 16, 20232 yr Community Expert The partition is gone, type sfdisk /dev/nvme1n1 then type 2048 and hit enter, post a screenshot of the result.
August 17, 20232 yr I am kinda new to this, but does this mean that my superblock is corrupted? Because fdisk is saying that the drive contains btrfs sig, but the drive is unmountable.
August 17, 20232 yr Community Expert Sorry, missed your previous reply, what's missing is the partition, if you are still on the previous step, or do it again, when it asks to remove the signature type N, then type write and hit enter, then post output of btrfs fi show
August 17, 20232 yr Would you mind explaining how you knew it was a partition issue? Thank you for your help btw. Update: Writing the partition fixed it. I just rebooted and now my drives are mounted. Thank you. Again if you could explain how you knew it was a partition issue that would be really appreciated. Edited August 17, 20232 yr by MenacingMight Fix typo
August 17, 20232 yr Community Expert 17 minutes ago, MenacingMight said: if you could explain how you knew it was a partition issue 22 hours ago, MenacingMight said: root@menacingmight:~# btrfs-select-super -s 1 /dev/nvme1n1p1 ERROR: mount check: cannot open /dev/nvme1n1p1: No such file or directory This error means that the partition didn't exist, likely it was wiped by Unraid with wipefs when you were trying to replace/remove it, suggesting there was a misstep somewhere.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.