March 24, 20242 yr Hello, I was working to replace my cache drive to upgrade it to a larger size, I stopped the array and added the second cache drive after I went to start the array again and got his error. UNMOUNTABLE: UNSUPPORTED OR NO FILE SYSTEM Mar 24 15:21:35 Trouble emhttpd: shcmd (538): mkdir -p /mnt/cache Mar 24 15:21:35 Trouble emhttpd: shcmd (539): mount -t xfs -o noatime,nouuid /dev/sdb1 /mnt/cache Mar 24 15:21:35 Trouble root: mount: /mnt/cache: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. I have attached my system Diag. trouble-diagnostics-20240324-1543.zip
March 25, 20242 yr Author 17 hours ago, JorgeB said: btrfs fi show Label: none uuid: 08eee0be-7acb-4342-926b-3a54cf7cf730 Total devices 2 FS bytes used 195.96GiB devid 1 size 238.47GiB used 238.47GiB path /dev/sdb1 *** Some devices missing
March 25, 20242 yr Community Expert Unassign the pool device, set pool slots to two, re-assign the pool device, there's a device missing, but if the pool was redundant it will mount with the remaining one, if it doesn't post new diags.
March 25, 20242 yr Author Okay that fixed the issue, I see what was the problem, I was trying to replace the drive and set the pool to 2 drives. I think I did this wrong I will get it all backed up off the Cache and rebuild the cache drives.
March 25, 20242 yr Author I am seeing a ton of errors now, SMBus is busy, can't use it! I have attached my diag again. trouble-diagnostics-20240325-1253.zip
March 25, 20242 yr Community Expert Try booting in safe mode and/or this: https://forums.unraid.net/topic/71918-i801_smbus-0000001f3-smbus-is-busy-cant-use-it/?do=findComment&comment=1074683
March 25, 20242 yr Author Fixed the SMBUS issue now having an issue with the cache still. I'm really just trying to turn it into a raid 1 so I can mirror the data and pull the old 256GB Drive. Docker Service wont start. Mar 25 16:12:11 Trouble kernel: BTRFS info (device sdb1: state A): chunk_block_rsv: size 0 reserved 0 Mar 25 16:12:11 Trouble kernel: BTRFS info (device sdb1: state A): delayed_block_rsv: size 0 reserved 0 Mar 25 16:12:11 Trouble kernel: BTRFS info (device sdb1: state A): delayed_refs_rsv: size 3670016 reserved 0 Mar 25 16:12:11 Trouble kernel: BTRFS: error (device sdb1: state A) in __btrfs_free_extent:3075: errno=-28 No space left Mar 25 16:12:11 Trouble kernel: BTRFS info (device sdb1: state EA): forced readonly Mar 25 16:12:11 Trouble kernel: BTRFS error (device sdb1: state EA): failed to run delayed ref for logical 2817023393792 num_bytes 16384 type 176 action 2 ref_mod 1: -28 Mar 25 16:12:11 Trouble kernel: BTRFS: error (device sdb1: state EA) in btrfs_run_delayed_refs:2149: errno=-28 No space left Mar 25 16:12:11 Trouble kernel: BTRFS: error (device sdb1: state EA) in btrfs_create_pending_block_groups:2472: errno=-28 No space left Mar 25 16:12:11 Trouble emhttpd: shcmd (412): mount -o remount,discard=async /mnt/cache Mar 25 16:12:11 Trouble kernel: BTRFS: error (device sdb1: state EA) in btrfs_create_pending_block_groups:2484: errno=-28 No space left Mar 25 16:12:11 Trouble kernel: BTRFS: error (device sdb1: state EA) in add_block_group_free_space:1390: errno=-28 No space left Mar 25 16:12:11 Trouble kernel: BTRFS info (device sdb1: state EMA): allowing degraded mounts Mar 25 16:12:11 Trouble kernel: BTRFS info (device sdb1: state EMA): turning on async discard Mar 25 16:12:11 Trouble emhttpd: /mnt/cache: autotrim setxattr error: Read-only file system Mar 25 16:12:11 Trouble emhttpd: /mnt/cache: compression setxattr error: Read-only file system Mar 25 16:12:11 Trouble emhttpd: shcmd (413): /sbin/wipefs -af /dev/nvme1n1p1 Mar 25 16:12:11 Trouble emhttpd: shcmd (414): /sbin/blkdiscard /dev/nvme1n1p1 Mar 25 16:12:12 Trouble emhttpd: shcmd (415): /sbin/btrfs device add -f /dev/nvme1n1p1 /mnt/cache Mar 25 16:12:14 Trouble root: ERROR: error adding device '/dev/nvme1n1p1': Read-only file system Mar 25 16:12:14 Trouble root: WARNING: Multiple block group profiles detected, see 'man btrfs(5)' Mar 25 16:12:14 Trouble root: WARNING: System: single, dup Mar 25 16:12:14 Trouble root: Performing full device TRIM /dev/nvme1n1p1 (465.76GiB) ... Mar 25 16:12:14 Trouble emhttpd: shcmd (415): exit status: 1 Mar 25 16:12:14 Trouble emhttpd: shcmd (416): /sbin/btrfs device delete missing /mnt/cache && /sbin/btrfs balance start --full-balance /mnt/cache & Mar 25 16:12:20 Trouble kernel: BTRFS info (device loop2): first mount of filesystem fe63c179-fef7-4a64-b409-1b380b22e89c Mar 25 16:12:20 Trouble kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm Mar 25 16:12:20 Trouble kernel: BTRFS info (device loop2): using free space tree Mar 25 16:12:20 Trouble kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Mar 25 16:12:20 Trouble kernel: BTRFS info (device loop2): enabling ssd optimizations Mar 25 16:12:20 Trouble root: ERROR: unable to resize '/var/lib/docker': Read-only file system Mar 25 16:12:20 Trouble root: Resize device id 1 (/dev/loop2) from 75.00GiB to max Mar 25 16:12:20 Trouble emhttpd: shcmd (447): /etc/rc.d/rc.docker start Mar 25 16:12:20 Trouble root: starting dockerd ... Mar 25 16:12:21 Trouble avahi-daemon[32830]: Server startup complete. Host name is Trouble.local. Local service cookie is 1813167402. Mar 25 16:12:22 Trouble avahi-daemon[32830]: Service "Trouble" (/services/ssh.service) successfully established. Mar 25 16:12:22 Trouble avahi-daemon[32830]: Service "Trouble" (/services/smb.service) successfully established. Mar 25 16:12:22 Trouble avahi-daemon[32830]: Service "Trouble" (/services/sftp-ssh.service) successfully established. Mar 25 16:12:43 Trouble nmbd[32761]: [2024/03/25 16:12:43.010079, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Mar 25 16:12:43 Trouble nmbd[32761]: ***** Mar 25 16:12:43 Trouble nmbd[32761]: Mar 25 16:12:43 Trouble nmbd[32761]: Samba name server TROUBLE is now a local master browser for workgroup WORKGROUP on subnet 10.1.20.2 Mar 25 16:12:43 Trouble nmbd[32761]: Mar 25 16:12:43 Trouble nmbd[32761]: ***** Mar 25 16:12:50 Trouble emhttpd: shcmd (449): umount /var/lib/docker Mar 25 16:12:50 Trouble kernel: BTRFS info (device loop2): last unmount of filesystem fe63c179-fef7-4a64-b409-1b380b22e89c Mar 25 16:12:50 Trouble emhttpd: nothing to sync Mar 25 16:12:50 Trouble unassigned.devices: Mounting 'Auto Mount' Remote Shares... Mar 25 16:12:50 Trouble unassigned.devices: Using Gateway '10.1.20.1' for Remote Shares. Mar 25 16:12:50 Trouble unassigned.devices: Waiting 5 secs before mounting Remote Shares... Mar 25 16:22:00 Trouble root: Fix Common Problems Version 2024.03.09 Mar 25 16:22:00 Trouble root: Fix Common Problems: Warning: Share appdata set to cache-only, but files / folders exist on the array Mar 25 16:22:00 Trouble root: Fix Common Problems: Warning: Share media set to not use the cache, but files / folders exist on the cache drive Mar 25 16:22:03 Trouble root: Failed to write /mnt/cache/809538006.tmp Mar 25 16:22:03 Trouble root: Fix Common Problems: Error: Unable to write to cache Thanks for all your help. trouble-diagnostics-20240325-1616.zip Edited March 25, 20242 yr by TroubleMedia
March 26, 20242 yr Community Expert 12 hours ago, TroubleMedia said: No space left It's going read-only due to not enough space, the filesystem is fully allocated and it still has a missing device, move some data of the pool, then balance and see if it can remove the missing device.
March 26, 20242 yr Author I've tried to change the shares to the array and evoke Mover but it is not doing anything. There is also 43 GB free on the cache drive currently. I just really want to backup the cache drive and replace it with a new drive. But changing the shares to Array the mover does not move the files. Edited March 26, 20242 yr by TroubleMedia
March 26, 20242 yr Community Expert 27 minutes ago, TroubleMedia said: I've tried to change the shares to the array and evoke Mover but it is not doing anything. Mover won't work on a read-only filesystem. 27 minutes ago, TroubleMedia said: There is also 43 GB free on the cache drive currently. Yes, but it's fully allocated, this is a btrsf quirk, nothing else can be written until that's fixed, though if it goes ready only right after array start you won't be able to move some data to fix that.
March 26, 20242 yr Author I don't have any missing Pool drives now. Still stuck in read only, I have tried to perform a balance but this has not worked. Could you please suggest the best way to get some Data off the drive since it keeps getting stuck in read only. I appreciate your help. I have attached my diag again. trouble-diagnostics-20240326-1405.zip
March 26, 20242 yr Community Expert You should try to Copy (not move) what you can. Dynamix File Manager can be used for that.
March 26, 20242 yr Author 9 minutes ago, itimpi said: You should try to Copy (not move) what you can. Dynamix File Manager can be used for that. Okay so just copy everything over and then wipe the cache and rebuild the pool and then copy back?
March 26, 20242 yr Community Expert 1 minute ago, TroubleMedia said: Okay so just copy everything over and then wipe the cache and rebuild the pool and then copy back? Yes. Note that this means wipe and then rebuild the pool in case this was not clear.
March 26, 20242 yr Community Expert 50 minutes ago, TroubleMedia said: I don't have any missing Pool drives now. You still do, btrfs is unable to delete the missing device, because the balance is failing due to the not enough space issue: Data Metadata System System Id Path single single single DUP Unallocated Total Slack -- --------- --------- -------- -------- ------- ----------- --------- ----- 1 /dev/sdb1 235.43GiB 3.01GiB 32.00MiB 4.00MiB 1.05MiB 238.47GiB - 2 missing - - - - 465.76GiB 465.76GiB - -- --------- --------- -------- -------- ------- ----------- --------- ----- Total 235.43GiB 3.01GiB 32.00MiB 2.00MiB 465.76GiB 704.24GiB 0.00B Used 194.75GiB 1.21GiB 48.00KiB 0.00B Note also the unallocated value of just 1MiB, that's what I mean by the filesystem being fully allocated, there's a thing you could try, but easiest way forward might be to just copy anything important you have on the pool to the array and then re-format.
March 27, 20242 yr Author Thank you everyone. I copied the data off and then rebuilt the cache using the new drive its working flawlessly now.
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.