obesepanda

I ran the first line once then ran both the commands at once, it's prolly why it says '/x' exists. root@UNRAID:~# mkdir /x mount -v /dev/sdag1 /x mkdir: cannot create directory ‘/x’: File exists mount: /x: can't read superblock on /dev/sdag1. dmesg(1) may have more information after failed mount system call.

It looks like it's still showing the same thing Label: none uuid: d5aaad24-9cef-4355-873e-2785ad43db0d Total devices 4 FS bytes used 3.84TiB devid 1 size 1.82TiB used 1.82TiB path /dev/sde1 devid 2 size 1.82TiB used 1.82TiB path /dev/sdc1 devid 3 size 232.88GiB used 232.88GiB path /dev/nvme1n1p1 devid 4 size 232.88GiB used 232.88GiB path /dev/nvme2n1p1 Label: none uuid: d452fc5f-ee99-46fa-9bbe-682ab68e56c2 Total devices 2 FS bytes used 120.68GiB devid 1 size 447.13GiB used 146.01GiB path /dev/sdd1 devid 2 size 447.13GiB used 146.01GiB path /dev/sdf1 Label: none uuid: f55cb54a-2452-494e-9340-9780bde56654 Total devices 1 FS bytes used 10.10GiB devid 1 size 447.13GiB used 15.02GiB path /dev/sdj1 Label: none uuid: 851912fa-e718-4fdd-8c29-7d58c7cfb7bf Total devices 2 FS bytes used 332.00KiB devid 1 size 223.57GiB used 2.03GiB path /dev/sdl1 devid 2 size 223.57GiB used 2.03GiB path /dev/sdk1 Label: none uuid: f67d589a-9d63-4c57-866d-b0508a799559 Total devices 1 FS bytes used 163.14GiB devid 1 size 232.88GiB used 231.02GiB path /dev/nvme0n1p1 Label: none uuid: 89cf4528-ee9b-4964-8291-4bc0331a689b Total devices 1 FS bytes used 17.75GiB devid 1 size 60.00GiB used 35.02GiB path /dev/loop2 Label: none uuid: 63882d78-2006-4da2-85af-93eb4cbb5910 Total devices 1 FS bytes used 2.76MiB devid 1 size 1.00GiB used 238.38MiB path /dev/loop3 warning, device 1 is missing Label: none uuid: 20662da0-afcb-4ae1-bc89-cd6d2cf8e959 Total devices 4 FS bytes used 20.00TiB devid 2 size 2.73TiB used 2.73TiB path /dev/sdx1 devid 3 size 2.73TiB used 2.73TiB path /dev/sdah1 devid 4 size 12.73TiB used 12.67TiB path /dev/sdg1 *** Some devices missing

root@UNRAID:~# btrfs-select-super -s 1 /dev/sdag1 using SB copy 1, bytenr 67108864

I let it run for about five mins and got the following root@UNRAID:~# wipefs /dev/sdag1 DEVICE OFFSET TYPE UUID LABEL sdag1 0x0 xfs d0b9fbf1-53f0-4560-9002-3cef4869bdde sdag1 0x10040 btrfs 20662da0-afcb-4ae1-bc89-cd6d2cf8e959 root@UNRAID:~# dd if=/dev/sdag bs=16M status=progress 2>/dev/null | hexdump -C | grep '_BHRfS_M' 00018040 5f 42 48 52 66 53 5f 4d 9f 3f 01 00 00 00 00 00 |_BHRfS_M.?......| 04008040 5f 42 48 52 66 53 5f 4d 9f 3f 01 00 00 00 00 00 |_BHRfS_M.?......|

root@UNRAID:~# fdisk -l /dev/sdag Disk /dev/sdag: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors Disk model: TOSHIBA HDWD130 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 16773120 bytes Disklabel type: gpt Disk identifier: 31A4A078-D172-40EE-B09B-649E600FEB4E Device Start End Sectors Size Type /dev/sdag1 64 5860533134 5860533071 2.7T Linux filesystemI get the following when running it.

I'm a bit confused. That pool only has 4 drives and are they not all present? UNRAID shows green on them. I'm also not seeing any failed SMART reports for any of the drives.

I believe it was set as RAID 0. I didn't really care about the data. Is it possible to recover it without losing everything?

So one of my drives was acting up, so I stopped the array and then pulled out one of the drives for my other pools by accident. It appears doing so, caused it to get an error message. When running btrfs fi show I get the following Label: none uuid: 20662da0-afcb-4ae1-bc89-cd6d2cf8e959 Total devices 4 FS bytes used 20.00TiB devid 2 size 2.73TiB used 2.73TiB path /dev/sdx1 devid 3 size 2.73TiB used 2.73TiB path /dev/sdah1 devid 4 size 12.73TiB used 12.68TiB path /dev/sdg1 *** Some devices missing I've tried to reboot the server and the issue is still there. Any ideas on how I can recover it without losing any data? unraid-diagnostics-20260101-1913.zip

So I'm trying to get my Unraid Server to join a Wireguard connection that my Omada ER605 is hosting at a remote location. I am able to connect to it with another Windows laptop, so I know the connection is set up correctly. I'm having issues connecting with Unraid. I tried to export the config from the working machine over to Unraid, but that didn't work. I'm able to get Data Sent, but no Data received. I did notice that on the Windows laptop, the Public Key at the top is supposed to placed under Omada's Peer (see third screenshot Public Key). How do I get that Public Key for Unraid? I think if I can find that key I should be all set. Windows Wireguard Settings Omada Settings Unraid Setting

Is it possible to change the profile to "default" or non RAID without losing any data? If so, how?

One of my pools seems to have glitched up and it's saying there's no free space even though the total size is 9TB. It says only 6.69TB is used and I tried to add in another 1TB drive to see if that helps, but it did not. I tried to rebalance it, but that didn't work and deleting the files via Windows "appears" to delete it, but when I confirm with console the file is still there. I also cannot delete or create a folder in console as it gives me a Read-Only file system error. The drive I added doesn't even register as the total size should be 10 TB Overall: Device size: 8.19TiB Device allocated: 6.15TiB Device unallocated: 2.03TiB Device missing: 0.00B Device slack: 10.50KiB Used: 6.08TiB Free (estimated): 2.11TiB (min: 1.09TiB) Free (statfs, df): 0.00B Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 512.00MiB (used: 0.00B) Multiple profiles: no Data Metadata System Id Path RAID0 RAID1 RAID1 Unallocated Total Slack -- ---------- --------- -------- --------- ----------- ------- -------- 1 /dev/sdr1 2.72TiB 7.00GiB 32.00MiB 1.04MiB 2.73TiB 3.50KiB 2 /dev/sdab1 2.72TiB 7.00GiB 32.00MiB 1.04MiB 2.73TiB 3.50KiB 3 /dev/sdaa1 711.49GiB - - 2.03TiB 2.73TiB 3.50KiB -- ---------- --------- -------- --------- ----------- ------- -------- Total 6.14TiB 7.00GiB 32.00MiB 2.03TiB 8.19TiB 10.50KiB unraid-diagnostics-20240103-1444.zip

I ended up hitting shutdown on the GUI and after 5-10 mins the server finally shutdown. I was able to start the array without any issues.

I'm not sure what is happening, but UNRAID cannot stop my array. It looks looping back with this error message. Jun 1 10:15:40 UNRAID emhttpd: Unmounting disks... Jun 1 10:15:40 UNRAID emhttpd: shcmd (1731): umount /mnt/docker Jun 1 10:15:40 UNRAID root: umount: /mnt/docker: target is busy. Jun 1 10:15:40 UNRAID emhttpd: shcmd (1731): exit status: 32 Jun 1 10:15:40 UNRAID emhttpd: Retry unmounting disk share(s)... Jun 1 10:15:45 UNRAID emhttpd: Unmounting disks... Jun 1 10:15:45 UNRAID emhttpd: shcmd (1732): umount /mnt/docker Jun 1 10:15:45 UNRAID root: umount: /mnt/docker: target is busy. Jun 1 10:15:45 UNRAID emhttpd: shcmd (1732): exit status: 32 Jun 1 10:15:45 UNRAID emhttpd: Retry unmounting disk share(s)... unraid-diagnostics-20230601-1018.zip

That was it. I should've turned off my dockers one by one to troubleshoot. Thanks for the help!

I'm not sure what is causing it, but I've noticed that a drive will randomly read itself at full speed, then it will switch off to another drive. It will rinse and repeat between diff drives and I haven't been able to figure out why. I checked the contents in those drives and no apps/users are using it. I've tried to restart the server, and it will be fine then after 5 mins or so, it will start back up. Any ideas? (When I first started to write this) (5 mins later) unraid-diagnostics-20230522-1146.zip