danob312 Posted June 11, 2024 Posted June 11, 2024 I'm currently facing some issues with my Unraid setup and need your help. My array devices and pool devices are showing as unmountable with errors. Despite this, I can access the data on these pools. Below are the details: Array Devices: DEVICE IDENTIFICATION TEMP. READS WRITES ERRORS FS SIZE USED FREE Disk 1 Samsung_Flash_Drive_FIT_0362223040007072-0:0 - 128 GB (sdb) * 1 0 0 xfs Unmountable: Unsupported partition layout Pool Devices: DEVICE IDENTIFICATION TEMP. READS WRITES ERRORS FS SIZE USED FREE Backup Samsung_SSD_990_PRO_2TB_S73WNJ0TC03752F - 2 TB (nvme2n1) 120 F 5862 1664 0 auto Unmountable: Unsupported or no file system Additional Pool Devices: DEVICE IDENTIFICATION TEMP. READS WRITES ERRORS FS SIZE USED FREE Dob Samsung_SSD_990_PRO_2TB_S73WNJ0W531995P - 2 TB (nvme1n1) 111 F 54,029 8726 0 zfs Unmountable: Unsupported or no file system Dob 2 Samsung_SSD_990_PRO_2TB_S6Z2NJ0TB37533J - 2 TB (nvme0n1) 106 F 54,764 8552 0 - Unmountable: Unsupported or no file system Pool of two devices 109 F 108,793 17,278 0 - - - - More Pool Devices: DEVICE IDENTIFICATION TEMP. READS WRITES ERRORS FS SIZE USED FREE Testicle Samsung_SSD_870_EVO_2TB_S6PNNJ0RB16574D - 2 TB (sdc) 77 F 315 614 0 zfs Unmountable: Unsupported or no file system Testicle 2 Samsung_SSD_870_EVO_2TB_S6PNNS0W321387Y - 2 TB (sdd) 75 F 211 598 0 - Unmountable: Unsupported or no file system Pool of two devices 76 F 526 1212 0 - - - - Steps Taken: 1. Attempted to unmount and export the ZFS pools using zfs unmount -a and zpool export. 2. Verified the status of the ZFS pools and the mount points. 3. Performed a filesystem check and repair on the XFS filesystem using xfs_repair -v /dev/sdb. Despite these steps, the disks remain unmountable and show errors related to unsupported partition layouts or file systems. Additional Information: - The data on these pools is accessible despite the errors. - Attached is the Unraid diagnostics file for further analysis: [diagnostics.zip](link_to_diagnostics_file). Request for Assistance: Could anyone guide me on how to resolve these unmountable disk issues? Any specific steps or commands that might help in recognizing and mounting these disks correctly? Thank you in advance for your assistance! tower-diagnostics-20240611-0641.zip Quote
JorgeB Posted June 11, 2024 Posted June 11, 2024 Some devices are reporting busy, reboot and post new diags after array start. Quote
danob312 Posted June 11, 2024 Author Posted June 11, 2024 tower-diagnostics-20240611-0814.zip okay here it is Quote
Solution JorgeB Posted June 11, 2024 Solution Posted June 11, 2024 I see that disk1 is a flash drive, I assume there's nothing important there? Regarding the pools, they are being imported in the go file, you must remove all that and reboot, to let Unraid import all the pools. Quote
danob312 Posted June 11, 2024 Author Posted June 11, 2024 here is what was in the go file. I rebooted the server with the default go file and attached the diag. All the pools are still saying the same thing. And yes disk one is just so I can have the zpools. Thanks! #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & # Import and mount the dob ZFS pool zpool import -a zfs mount -a #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & modprobe i915 chmod -R 777 /dev/dri # Bind mount for ZFS dataset mkdir -p /mnt/user/master mount --bind /mnt/z2/master /mnt/user/master # Bind mounts for ZFS datasets mkdir -p /mnt/user/Docker mount --bind /mnt/dob/Docker /mnt/user/Docker mkdir -p /mnt/user/appdata mount --bind /mnt/dob/appdata /mnt/user/appdata mkdir -p /mnt/user/appdata/Nginx_Proxy_Manager mount --bind /mnt/dob/appdata/Nginx_Proxy_Manager /mnt/user/appdata/Nginx_Proxy_Manager mkdir -p /mnt/user/appdata/bazarr mount --bind /mnt/dob/appdata/bazarr /mnt/user/appdata/bazarr mkdir -p /mnt/user/appdata/kometa mount --bind /mnt/dob/appdata/kometa /mnt/user/appdata/kometa mkdir -p /mnt/user/appdata/overseerr mount --bind /mnt/dob/appdata/overseerr /mnt/user/appdata/overseerr mkdir -p /mnt/user/appdata/sabnzbd mount --bind /mnt/dob/appdata/sabnzbd /mnt/user/appdata/sabnzbd mkdir -p /mnt/user/appdata/tautulli-1 mount --bind /mnt/dob/appdata/tautulli-1 /mnt/user/appdata/tautulli-1 mkdir -p /mnt/user/appdata/threadfin mount --bind /mnt/dob/appdata/threadfin /mnt/user/appdata/threadfin mkdir -p /mnt/user/plex_bot mount --bind /mnt/dob/plex_bot /mnt/user/plex_bot mkdir -p /mnt/user/vaultwarden mount --bind /mnt/dob/vaultwarden /mnt/user/vaultwarden # Bind mount Docker data directory mkdir -p /var/lib/docker mount --bind /mnt/dob/appdata/docker /var/lib/docker tower-diagnostics-20240611-0940.zip Quote
JorgeB Posted June 11, 2024 Posted June 11, 2024 cannot import '10658759146814266625': no such pool available Post the output of zpool import Quote
danob312 Posted June 11, 2024 Author Posted June 11, 2024 Thank you that was it... I thought I look that line out. Any idea why I can't change the zize of any of my shares? I also can't create any new shares Quote
danob312 Posted June 11, 2024 Author Posted June 11, 2024 (edited) here are my updated diagnostics and also the go config tower-diagnostics-20240611-1313.zipgo_script.txt Edited June 11, 2024 by danob312 Quote
JorgeB Posted June 11, 2024 Posted June 11, 2024 5 minutes ago, danob312 said: Any idea why I can't change the zize of any of my shares? What do you mean change the size? Do you mean the floor? Quote
JorgeB Posted June 11, 2024 Posted June 11, 2024 There's something creating mount points on /mnt/user before the array starts, you must disable this or it will cause issues with the user shares: Jun 11 10:55:21 Tower emhttpd: error: malloc_share_locations, 7199: Operation not supported (95): getxattr: /mnt/user/Docker Jun 11 10:55:21 Tower emhttpd: error: malloc_share_locations, 7199: Operation not supported (95): getxattr: /mnt/user/appdata Jun 11 10:55:21 Tower emhttpd: error: malloc_share_locations, 7199: Operation not supported (95): getxattr: /mnt/user/master Jun 11 10:55:21 Tower emhttpd: error: malloc_share_locations, 7199: Operation not supported (95): getxattr: /mnt/user/plex_bot Jun 11 10:55:21 Tower emhttpd: error: malloc_share_locations, 7199: Operation not supported (95): getxattr: /mnt/user/vaultwarden Quote
danob312 Posted June 11, 2024 Author Posted June 11, 2024 (edited) Its all in here... what should be in this file because I also had to add a delay to get docker to work on reboot go_script.txt #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & echo "Started Management Utility" >> /boot/go.log modprobe i915 echo "Loaded i915 module" >> /boot/go.log chmod -R 777 /dev/dri echo "Set permissions for /dev/dri" >> /boot/go.log # Bind mount for ZFS dataset mkdir -p /mnt/user/master mount --bind /mnt/z2/master /mnt/user/master echo "Mounted /mnt/z2/master to /mnt/user/master" >> /boot/go.log # Bind mounts for ZFS datasets mkdir -p /mnt/user/Docker mount --bind /mnt/dob/Docker /mnt/user/Docker echo "Mounted /mnt/dob/Docker to /mnt/user/Docker" >> /boot/go.log mkdir -p /mnt/user/appdata mount --bind /mnt/dob/appdata /mnt/user/appdata echo "Mounted /mnt/dob/appdata to /mnt/user/appdata" >> /boot/go.log mkdir -p /mnt/user/appdata/Nginx_Proxy_Manager mount --bind /mnt/dob/appdata/Nginx_Proxy_Manager /mnt/user/appdata/Nginx_Proxy_Manager echo "Mounted /mnt/dob/appdata/Nginx_Proxy_Manager to /mnt/user/appdata/Nginx_Proxy_Manager" >> /boot/go.log mkdir -p /mnt/user/appdata/bazarr mount --bind /mnt/dob/appdata/bazarr /mnt/user/appdata/bazarr echo "Mounted /mnt/dob/appdata/bazarr to /mnt/user/appdata/bazarr" >> /boot/go.log mkdir -p /mnt/user/appdata/kometa mount --bind /mnt/dob/appdata/kometa /mnt/user/appdata/kometa echo "Mounted /mnt/dob/appdata/kometa to /mnt/user/appdata/kometa" >> /boot/go.log mkdir -p /mnt/user/appdata/overseerr mount --bind /mnt/dob/appdata/overseerr /mnt/user/appdata/overseerr echo "Mounted /mnt/dob/appdata/overseerr to /mnt/user/appdata/overseerr" >> /boot/go.log mkdir -p /mnt/user/appdata/sabnzbd mount --bind /mnt/dob/appdata/sabnzbd /mnt/user/appdata/sabnzbd echo "Mounted /mnt/dob/appdata/sabnzbd to /mnt/user/appdata/sabnzbd" >> /boot/go.log mkdir -p /mnt/user/appdata/tautulli-1 mount --bind /mnt/dob/appdata/tautulli-1 /mnt/user/appdata/tautulli-1 echo "Mounted /mnt/dob/appdata/tautulli-1 to /mnt/user/appdata/tautulli-1" >> /boot/go.log mkdir -p /mnt/user/appdata/threadfin mount --bind /mnt/dob/appdata/threadfin /mnt/user/appdata/threadfin echo "Mounted /mnt/dob/appdata/threadfin to /mnt/user/appdata/threadfin" >> /boot/go.log mkdir -p /mnt/user/plex_bot mount --bind /mnt/dob/plex_bot /mnt/user/plex_bot echo "Mounted /mnt/dob/plex_bot to /mnt/user/plex_bot" >> /boot/go.log mkdir -p /mnt/user/vaultwarden mount --bind /mnt/dob/vaultwarden /mnt/user/vaultwarden echo "Mounted /mnt/dob/vaultwarden to /mnt/user/vaultwarden" >> /boot/go.log # Delay to ensure all services are up sleep 30 echo "Delayed for 30 seconds" >> /boot/go.log # Bind mount Docker data directory mkdir -p /var/lib/docker mount -o loop /mnt/dob/appdata/docker.img /var/lib/docker if mount | grep -q '/var/lib/docker'; then echo "Mounted /mnt/dob/appdata/docker.img to /var/lib/docker" >> /boot/go.log # Start Docker service /etc/rc.d/rc.docker start if /etc/rc.d/rc.docker status | grep -q 'running'; then echo "Docker service started successfully" >> /boot/go.log else echo "Failed to start Docker service" >> /boot/go.log echo "Output of Docker status command:" >> /boot/go.log /etc/rc.d/rc.docker status >> /boot/go.log fi else echo "Failed to mount /mnt/dob/appdata/docker.img to /var/lib/docker" >> /boot/go.log echo "Output of mount command:" >> /boot/go.log mount | grep '/mnt/dob/appdata/docker.img' >> /boot/go.log echo "Output of dmesg command:" >> /boot/go.log dmesg | tail -n 20 >> /boot/go.log fi echo "Finished go script" >> /boot/go.log Edited June 11, 2024 by danob312 Quote
JorgeB Posted June 12, 2024 Posted June 12, 2024 Remove all those lines from the go file, revert to the stock one. Quote
danob312 Posted June 12, 2024 Author Posted June 12, 2024 I've done that and I'm unable to create shares or see any of my shares My go file: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & tower-diagnostics-20240612-0756.zip I also have to run this to get docker working- mkdir -p /var/lib/docker mount -o loop /mnt/dob/appdata/docker.img /var/lib/docker /etc/rc.d/rc.docker start Quote
JorgeB Posted June 12, 2024 Posted June 12, 2024 I don't even see the docker service trying to start, reboot to undo the manual docker start, start the array, then go to Settings - Docker, disable the docker service, click apply, set the docker image to an appropriate size, it's currently set to 1TB, usually 20 or 30GB are enough for most cases, re-enable, click apply again, post new diags. Quote
danob312 Posted June 12, 2024 Author Posted June 12, 2024 okay I did that, here are the new diags. also a screenshot /mnt/user/appdata does not exist. this again starts it right up mkdir -p /var/lib/docker mount -o loop /mnt/dob/appdata/docker.img /var/lib/docker /etc/rc.d/rc.docker start tower-diagnostics-20240612-1002.zip Quote
JorgeB Posted June 12, 2024 Posted June 12, 2024 I still don't see the docker serice trying to start, that is very strange, since you were messing around with go the file, there could be other changes, recommend redoing the flash drive with a stcock install, then copy inky your key and re-import the volumes. Quote
Recommended Posts
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.