November 10, 20241 yr Hey there, I'm in a bit of a pickle. Just now, I was restarting my server, and during the shutdown, I saw some error: unraid cannot connect to the docker daemon at unix ///var/run/docker.sock. is the docker daemon running? It seemed stuck on this, so I forcefully turned it off. And now, the only drive in my array says: "Unmountable: Unsupported or no file system" Is there any way to "fix" this? unraidserver-diagnostics-20241110-0331.zip Edited November 10, 20241 yr by LeroyLaFontaine
November 10, 20241 yr Community Expert Have you tried the procedure for handling unmountable drives documented here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release.
November 10, 20241 yr Author 4 hours ago, itimpi said: Have you tried the procedure for handling unmountable drives documented here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release. I had not, but I'm trying it now, as per your recommendation, but I'm running into the issue that I cannot see the options that are being described for checking the filesystem. Quote Make sure that you have the array started in the correct mode. If necessary stop the array and restart in the correct mode by clicking/unclicking the Maintenance Mode checkbox next to the Start button. From the Main screen of the WebGUI, click the name of the disk that you want to test or repair. For example, if the drive of concern is Disk 5, then click on Disk 5. If it's the Cache drive, then click on Cache. If in Maintenance mode then The disks will not be mounted but the underlying /dev/mdX type devices that correspond to each diskX in the Unraid GUI will have been created. This is important as any write operation against one of these 'md' type devices will also update parity to reflect that write has happened. You should see a page of options for that drive, beginning with various partition, file system format, and spin down settings. The section following that is the one you want, titled Check Filesystem Status. There is a box with the 2 words Not available in it. This is the command output box, where the progress and results of the command will be displayed. Below that is the Check button that starts the test, followed by the options box where you can type in options for the test/repair command. Step 4.) is where I can't do what is described. I can't check for a file system status, and it appears that UnRaid doesn't know what filesystem was being used. I've followed these steps with the Array stopped, started normally, and started in Maintenance Mode. I'm unsure if this is because I don't have a parity drive, since my Array consists of just one drive. Edited November 10, 20241 yr by LeroyLaFontaine
November 10, 20241 yr Community Expert You are using virtual disks, that is not supported or even recommended, if you want to virtualize Unraid, pass trough the disks or controller.
November 10, 20241 yr Author 17 minutes ago, JorgeB said: You are using virtual disks, that is not supported or even recommended, if you want to virtualize Unraid, pass trough the disks or controller. I'm passing through the disks. Unfortunately, I can't pass through the controller since drives are attached that I need for something outside UnRaid. What I had done, is passthrough two drives, a 16TB HDD (array) and a 256SSD (dockers and VM's). And I passed through a PCIe device (1TB NVMe for Cache). For the sake of troubleshooting, I started UnRaid baremetal. And I get the same results, where I can't do what the manual tells me to do: What I see when I go to Main -> Disk1: https://i.gyazo.com/621f647772e118c5fb852dc396bf4cd3.png I don't see anything about checking the filesystem status (again, no difference if array is not started, started normally, or started in Maintenance Mode. Not sure if that's supposed to make a difference here already). unraidserver-diagnostics-20241110-1412.zip Edited November 10, 20241 yr by LeroyLaFontaine
November 10, 20241 yr Community Expert 26 minutes ago, LeroyLaFontaine said: I'm passing through the disks They are showing up as virtual disks, that's likely going to cause issues, also you are using a RAID controller, also not recommended, both can change the disk's MBR or partitions, post the output from: fdisk -l /dev/sdb and blkid Also, which filesystem were you using?
November 10, 20241 yr Author Just now, JorgeB said: They are showing up as virtual disks, that's likely going to cause issues, also you are using a RAID controller, also not recommended, both can change the disk's MBR or partitions, post the output from: fdisk -l /dev/sdb and blkid Also, which filesystem were you using? They should be showing up now as normal HDD, in that last diagnostics file. root@UnRaidServer:~# fdisk -l /dev/sdb Disk /dev/sdb: 14.55 TiB, 16000900661248 bytes, 31251759104 sectors Disk model: ST16000NE000-2RW Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 68EE1A68-2918-48E8-B09E-01BEA5FAF072 Device Start End Sectors Size Type /dev/sdb1 64 31251759070 31251759007 14.6T Linux filesystem root@UnRaidServer:~# and root@UnRaidServer:~# blkid /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="18F3-0F43" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="ed7a2645-01" /dev/loop1: TYPE="squashfs" /dev/nvme0n1p1: LABEL="cache" UUID="1554510259976988443" UUID_SUB="7566520858075654888" BLOCK_SIZE="4096" TYPE="zfs_member" /dev/sdb1: LABEL="disk1" UUID="5601764256316518606" UUID_SUB="10016781515377418896" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="84035d80-8e40-485d-9b36-59feece5ffb8" /dev/loop0: TYPE="squashfs" /dev/sdc1: UUID="84a8d6c0-d5eb-48ab-937c-937004310c0b" UUID_SUB="d78948b9-8d49-4add-80b8-f8480617dc19" BLOCK_SIZE="4096" TYPE="btrfs" /dev/md1p1: LABEL="disk1" UUID="5601764256316518606" UUID_SUB="10016781515377418896" BLOCK_SIZE="4096" TYPE="zfs_member" /dev/loop2: UUID="a7489dd4-c70f-4f80-ab0e-2a28f5356a4b" UUID_SUB="0055cad2-89ee-43a5-a284-4e6178de1d54" BLOCK_SIZE="4096" TYPE="btrfs" root@UnRaidServer:~# I'm using ZFS on both the HDD in the array, that we're talking about now, and on the nvme cache drive. The SSD storing docker and VM's is using btrfs.
November 10, 20241 yr Author 13 minutes ago, JorgeB said: And output from: zpool import root@UnRaidServer:~# zpool import pool: cache id: 1554510259976988443 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: cache ONLINE nvme0n1p1 ONLINE pool: disk1 id: 5601764256316518606 state: FAULTED status: The pool was last accessed by another system. action: The pool cannot be imported due to damaged devices or data. The pool may be active on another system, but can be imported using the '-f' flag. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-EY config: disk1 FAULTED corrupted data wwn-0x5000c500db1abb61-part1 ONLINE root@UnRaidServer:~# root@UnRaidServer:~# root@UnRaidServer:~# root@UnRaidServer:~# zpool import -f pool: cache id: 1554510259976988443 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: cache ONLINE nvme0n1p1 ONLINE pool: disk1 id: 5601764256316518606 state: FAULTED status: The pool was last accessed by another system. action: The pool cannot be imported due to damaged devices or data. The pool may be active on another system, but can be imported using the '-f' flag. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-EY config: disk1 FAULTED corrupted data wwn-0x5000c500db1abb61-part1 ONLINE root@UnRaidServer:~# I've tried (a few days ago), to add this pool to a TrueNAS server, but since then, added it back to UnRaid, here it was working fine. The error came after a simple UnRaid restart. Edited November 10, 20241 yr by LeroyLaFontaine
November 10, 20241 yr Community Expert 6 minutes ago, LeroyLaFontaine said: The pool cannot be imported due to damaged devices or data. That pool is damaged, likely from using a virtual disk or the RAID controller, you will need to re-format and restore the data from a backup.
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.