Everything posted by Xenu
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
Sorry missed this reply! Finally got some time to try and resolve this. The USB drive is soldiered so I don't have the ability to shuck the drive and connect this way. Can you advice please if there's ANY way I can recover the contents of the pool and shift it to a new single 2TB SSD drive I have?
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
root@box:~# fdisk -l /dev/sdd Disk /dev/sdd: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: Tech Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
Do you want to remove the signature? [Y]es/[N]o: N /dev/sdd1 : 64 1000215215 (476.9G) Linux /dev/sdd2: write New situation: Disklabel type: dos Disk identifier: 0x9030fbc4 Device Boot Start End Sectors Size Id Type /dev/sdd1 64 1000215215 1000215152 476.9G 83 Linux The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. root@box:~# btrfs fi show Label: none uuid: 94418e24-71a8-4933-a795-612a5f71ebf5 Total devices 1 FS bytes used 412.00KiB devid 1 size 2.00GiB used 228.75MiB path /dev/loop2 warning, device 2 is missing warning, device 2 is missing ERROR: cannot read chunk root Label: none uuid: adb84329-04d6-471b-afbd-2443872bcda4 Total devices 2 FS bytes used 1.88TiB devid 1 size 1.82TiB used 1.82TiB path /dev/sdi1 *** Some devices missing
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
Sorry, attempting to multitask. >>> 64 Created a new DOS disklabel with disk identifier 0x1aa2d23b. Created a new partition 1 of type 'Linux' and of size 476.9 GiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o:
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
root@box:~# sfdisk /dev/sdd Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdd: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: Tech Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>>
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
Thank you again for your time! root@box:~# fdisk -l /dev/sdd Disk /dev/sdd: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: Tech Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Yes, one of the drives has always been connected via USB. I've been meaning to migrate back to one cache drive, internal SSD. If it's the USB one that's causing problems/damaged, would you be able to offer advice on how to migrate the data over and remove the USB drive from the pool, please? If I can get the array back online, I'll gladly just moved everything off the cache for time being.
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
Hello Jorge, thank you again! I left the scrub running overnight and immediately it was finding bad bits. It did however abort the scrub by itself overnight and attempting the scrub again simply does nothing (pressing the srub button had the page pending for a second or two, but nothing more happened). I powed off the server. Booting it back up today, the cache pool has also reverted to how it looked at the start of this thread. I had a go at bringing the cache pool back online using your steps above, as the terminal response from each step was the same, however after reaching this step: - I'm presented with this: root@box:~# btrfs fi show Label: none uuid: 94418e24-71a8-4933-a795-612a5f71ebf5 Total devices 1 FS bytes used 412.00KiB devid 1 size 2.00GiB used 228.75MiB path /dev/loop2 warning, device 2 is missing warning, device 2 is missing ERROR: cannot read chunk root Label: none uuid: adb84329-04d6-471b-afbd-2443872bcda4 Total devices 2 FS bytes used 1.88TiB devid 1 size 1.82TiB used 1.82TiB path /dev/sdi1 *** Some devices missing Am I right to assume one of the drives needs replacing, as it's damaged/on it way out? Is there any way to identify what drive of the two might be the cause? And if so, is there anyway to shift the cache from one drive onto the other, or both cache drives content onto the non-cache drives until I can replace the cache drives? Let me know if you feel I need to make a new thread for this! box-diagnostics-20241022-1236.zip
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
Running it now, already started making corrections. Thank you again!
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
Many many thanks, Jorge! Popped you a little beer money your way!
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
You genius, functioning again! Thank you! I manually stopped Docker in case there's any ongoing issues. box-diagnostics-20241021-1609.zip
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
Do you want to remove the signature? [Y]es/[N]o: N /dev/sdd1 : 64 1000215215 (476.9G) Linux /dev/sdd2: write New situation: Disklabel type: dos Disk identifier: 0xcc0341ce Device Boot Start End Sectors Size Id Type /dev/sdd1 64 1000215215 1000215152 476.9G 83 Linux The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. root@box:~# btrfs fi show Label: none uuid: adb84329-04d6-471b-afbd-2443872bcda4 Total devices 2 FS bytes used 1.88TiB devid 1 size 1.82TiB used 1.82TiB path /dev/sdi1 devid 2 size 476.94GiB used 476.94GiB path /dev/sdd1
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
root@box:~# sfdisk /dev/sdd Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdd: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: Tech Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 64 Created a new DOS disklabel with disk identifier 0xcc0341ce. Created a new partition 1 of type 'Linux' and of size 476.9 GiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o:
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
Thank you. root@box:~# sfdisk /dev/sdd Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdd: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: Tech Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 2048 Created a new DOS disklabel with disk identifier 0x7ad5d360. Created a new partition 1 of type 'Linux' and of size 476.9 GiB. /dev/sdd1 : 2048 1000215215 (476.9G) Linux /dev/sdd2: Looks like it's awaiting another input?
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
root@box:~# fdisk -l /dev/sdi Disk /dev/sdi: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: CT2000MX500SSD1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdi1 2048 3907029167 3907027120 1.8T 83 Linux root@box:~# fdisk -l /dev/sdd Disk /dev/sdd: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: Tech Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes I notice the two drives are now also showing under historical devices:
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
No idea. Nothing was tinkered with/changed, just happened overnight. Checked cables, all fine there.
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
Thank you for the reply. This is the response: root@box:~# btrfs fi show Label: none uuid: 94418e24-71a8-4933-a795-612a5f71ebf5 Total devices 1 FS bytes used 412.00KiB devid 1 size 2.00GiB used 228.75MiB path /dev/loop2 warning, device 2 is missing warning, device 2 is missing ERROR: cannot read chunk root Label: none uuid: adb84329-04d6-471b-afbd-2443872bcda4 Total devices 2 FS bytes used 1.88TiB devid 1 size 1.82TiB used 1.82TiB path /dev/sdi1 *** Some devices missing This is with the array online and both cache drives assigned.
-
(SOLVED) Cache pool: "Unmountable: Unsupported or no file system"
I hope someone can help, please? I woke up this morning to find my cache pool of 2 devices were no longer mounted. I've tried stopping the array, un-assign both cache devices. Start array. Stop array, reassign both cache devices. Start array. = Same error. Please advice! box-diagnostics-20241020-1546.zip
-
rsync webdav drive breaks Plex & unraid
Unraid Server Version#: 6.11.5 Plex Server Version#: 1.31.2.6810 Docker Version: Tested on official, binhex and linuxserver Whenever I mount my webdav drive which appears to Plex as any other local directory, Plex begins to scan through the files, detecting credits, updating metadata, etc. After several minutes it locks up gets stuck in a ‘ERROR - Waited over 10 seconds for a busy database; giving up.’ loop and never progresses. I’ve completely wiped the container and tried again and again. It breaks every time I add this folder to the library after several minutes of scanning. Previously the container also messes with Unraid a lot. It becomes impossible to stop or remove through the GUI, as well as through the terminal using the kill command. Further Unraid refuses to shutdown. The only way to stop and remove the container is to ensure it isn't set to auto-start on boot, and then forcibly shutdown the server, and then power back up. The container can then be removed. Attempting to do anything with container throws the error, likely given it can't stop the container?: docker: Error response from daemon: Conflict. The container name "/Plex-Media-Server" is already in use by container "d86a32cb08a6240307d266349cbfe0556fb55105af5185b25d5f156db634b5f4". You have to remove (or rename) that container to be able to reuse that name. Please advise. Plex logs: https://1drv.ms/u/s!AlGB_asRP_nthJcx_HFVObuzW-NUjw Unraid logs: https://1drv.ms/u/s!AlGB_asRP_nthJc2bjH5gqENCvhnAg
-
[Support] Josh5 - Steam (Headless)
Have you tried: In the Steam game library, search for Cyberpunk 2077 and right-click on it with the mouse. In the right-click menu, select “Properties” to access the game’s properties. Inside the properties window, locate “Compatibility.” Then, check “Force the use of a specific Steam Play compatibility tool.”
-
[Support] Josh5 - Steam (Headless)
Sadly not. I just don't understand it. No high CPU usage, no high RAM and no high disk usage. Sometimes disk usage shows 0 activity... when it should be loading a game?!
-
Stop Unraid from seeing iLO as a mount
I'm running Unraid on my HP Proliant Gen8 Microsever. For whatever reason Unraid is seeing iLO as a unassigned drive. Because of this, this extra 'mount' (HP_iLO_LUN_00_Media_0_000002660A01-0:0) is bringing me 1 over my drive limit for my Unraid license, preventing my array from auto starting. Each boot I have to use the Unassigned Devies (/Plus) plugin to unmount this mount before being able to start the array. Is there any way I can stop this from happening? box-diagnostics-20221106-1017.zip
-
[Support] Josh5 - Steam (Headless)
How do we enable Neko, please?
-
[Support] Josh5 - Steam (Headless)
Thank you both for your replies. My games are stored on my cache. I'll give an unassigned drive a go!
-
[Support] Josh5 - Steam (Headless)
Thank you for this amazing project!! I have noticed that there is a huge audio lag when accessing Steam via noVNC. Is there any way to resolve this? I've also noticed a number of games do not launch. Some without an error, or in the case of Portal: Any ideas why this might be?
-
Docker memory/utilisation at 100%
My Docker memory has been slowly creeping up as I add containers. It was last hovering around 90% until I just added the Steam Headless container. How can I troubleshoot what is causing this? I've currently 27 live containers + 39 not running. I've stopped the Docker service for the time being as I can't imagine this is doing any good. Please advise. Edit: As per the attached screenshot, I tried upping the vdisk size from 30GB to 40GB. It was still at 100%. Further, the Docker service is refusing to start now. Is there any way I can start the Docker service without it starting any containers so I can begin troubleshooting? box-diagnostics-20220924-1515.zip