jay_busacca

Nothing I try or configure causes ROMM to succesfully find roms on an auto scan. I've tried to manually upload one or multiple roms and everytime they fail with an error "there was an error uploading files". I've esured i have the folder structure as advised. I get the platforms showing up as other have, but no roms. Any suggestions on what to check next?

Thank you for the support.

Posted Edit: Also: root@Tower:~# btrfs rescue zero-log /mnt/sdb1 ERROR: mount check: cannot open /mnt/sdb1: No such file or directory ERROR: could not check mount status: No such file or directory tower-diagnostics-20241027-1102.zip

Restarted array. Drives still won't mount.

Looking for help after reading the support docs on what to do when a drive appears to have a corrupted file system. My cache pool is BTRFS and not mounting. I can't run scrub to check for fs errors. I was able to follow a guide and copy the data from the pool to the array. Before I reformat my pool, I'm looking for what's the right thing to do. I'd like a way to mount the drive and run a scrub, but I don't know how. Unraid sees he pool as unmounted. Is there an alternative to potentially fix the filesystem so i don't have to reformat? Since I have a cache pool do I stay with BTRFS if I do have to reformat? Here is an output from btrfs check status: WARNING: filesystem mounted, continuing because of --force [1/7] checking root items [2/7] checking extents data extent[12906602496, 53248] referencer count mismatch (root 5 owner 880 offset 7835267072) wanted 0 have 1 data extent[12906602496, 53248] bytenr mimsmatch, extent item bytenr 12906602496 file item bytenr 0 data extent[12906602496, 53248] referencer count mismatch (root 5 owner 1049456 offset 7835267072) wanted 1 have 0 backpointer mismatch on [12906602496 53248] ERROR: errors found in extent allocation tree or chunk allocation [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sdb1 UUID: 875b6278-0c6e-4008-8238-cbd5f850647c found 88101838848 bytes used, error(s) found total csum bytes: 85604936 total tree bytes: 262356992 total fs tree bytes: 100745216 total extent tree bytes: 46514176 btree space waste bytes: 61443702 file data blocks allocated: 159848906752 referenced 85299896320 tower-diagnostics-20241027-0032.zip

So I fixed mine and it ended up being very simple. I stopped my container, deleted my log.db file, restarted, that was it. The log file was corrupted.

We're you able to fix this? I have the same error since switching repositories.

7 is the first half, 7 cpu and 23 HT, but your point stands. I'm going to isolate 23 as well and see if that solves the issue. Thanks for the idea!

I searched the forums and it seems this may be a known issue, apologies if I missed a fix. i have cores 7, 8-31 pinned to a VM and isolated as well, but my docker containers, mostly Plex, stil hit core 7 all the time. I don't understand what I'm doing wrong. Any help is appreciated.

I'm really treading into "don't know what i'm doing" territory, but i rebooted and my shares came back. Now both cache disked have been disabled by Unraid and emulated, presumably because I interrupted the mover process. Now i have an issue with disabled disks, but i'll read the forums for a solution.

Hi All, I desparately need help as I really think I screwed up: I followed the steps to upgrade my cache pool from two 128gb drives to 2 1tb drives. Set the shares to 'yes', invoked mover, swapped drives, set share preference, mover again. Here's where I f*cked up. I set one share to "prefer" cache when I don't think I should have, as it's a ton of media files. I went to the share and changed the preference, but I didn't stop the mover. Now *all* my shares have disappeared. Currently panicking, not sure how I can fix this. Any help is appreciated.

This would be a great addition to the dashboard!