xokia

I have a cache drive for writes the data gets written to the cache. Doesnt write back to the array until the end of the day.

Drive was never used to store any data on it I was purely looking at the encryption features. I dont want to thrash the 100TB worth of drives for a full 24 hours just to take a drive out. Its spun down and wont get used so I'll just wait until the next scheduled parity sync in 3 months then remove it. Annoying but nothing that is a major concern. I set a reminder to notify me to remove the drive. No data should be added to it since I dont use the drives like a normal "array" 1 large storage location. I dont like to spin up a bunch of drives just to get access to data. So I put specific data on specific drives and only the drive that is needed for the specific task gets spun up when writing/reading. So most of the time only a single drive is spun up and the rest stay spun down. Even writing back to the parity drive is a scheduled daily task so it also sits spun down.

Thanks I'll schedule it to be removed the next parity check in 3 months. If I could get passphrase + keyfile to work then I'd like to use encrypted drives. But currently they are mutually exclusive in the SW. Looks like LUKS supports it but unraid only uses a single key slot.

Thanks I dont want to do a parity sync as my drives are 20TB and it takes 24 hours. It would seem unraid should automate this if you zero a drive or have never put anything on the drive it should be easier to remove a drive without having to run parity again or go through a convoluted dance. I should be able to select a drive choose remove from array then it does what it needs to do to remove that drive. Obviously gives warning that any data would be wiped. But the process is very manual and error prone. Unraid LOVES to restart parity checks. I tried option 2 but failed at step 1 so I assumed maybe the instructions were out of date Start the array in maintenance mode, click on the disk you want to remove, and then click Erase. This erases the file system from the device while maintaining parity, then stop the array. I do not see an "Erase" Feature after selecting the drive in maintenance mode.

I am running 7.3.2 I installed a new drive and encrypted it. I was just trying out unraids drive encryption features. I now want to remove this drive from the array. Nothing was placed on this drive. How do I remove this drive without affecting my parity?

No luck?

docker run -d --name='romm' --net='romm' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="hidden" -e HOST_CONTAINERNAME="romm" -e 'DB_HOST'='192.168.0.12' -e 'DB_PORT'='3306' -e 'DB_NAME'='romm' -e 'DB_USER'='romm' -e 'DB_PASSWD'='hidden' -e 'ROMM_AUTH_SECRET_KEY'='hidden' -e 'IGDB_CLIENT_ID'='' -e 'IGDB_CLIENT_SECRET'='' -e 'SCREENSCRAPER_USER'='' -e 'SCREENSCRAPER_PASSWORD'='' -e 'MOBYGAMES_API_KEY'='' -e 'STEAMGRIDDB_API_KEY'='hidden' -e 'RETROACHIEVEMENTS_API_KEY'='' -e 'REFRESH_RETROACHIEVEMENTS_CACHE_DAYS'='' -e 'LAUNCHBOX_API_ENABLED'='false' -e 'PLAYMATCH_API_ENABLED'='false' -e 'HASHEOUS_API_ENABLED'='false' -e 'FLASHPOINT_API_ENABLED'='false' -e 'HLTB_API_ENABLED'='false' -e 'ROMM_DB_DRIVER'='mariadb' -e 'DB_QUERY_JSON'='' -e 'REDIS_HOST'='' -e 'REDIS_PORT'='' -e 'REDIS_USERNAME'='' -e 'REDIS_PASSWORD'='' -e 'REDIS_DB'='' -e 'REDIS_SSL'='' -e 'DISABLE_CSRF_PROTECTION'='false' -e 'DISABLE_DOWNLOAD_ENDPOINT_AUTH'='false' -e 'DISABLE_USERPASS_LOGIN'='false' -e 'SESSION_MAX_AGE_SECONDS'='' -e 'KIOSK_MODE'='false' -e 'OIDC_ENABLED'='false' -e 'OIDC_PROVIDER'='' -e 'OIDC_CLIENT_ID'='' -e 'OIDC_CLIENT_SECRET'='' -e 'OIDC_REDIRECT_URI'='' -e 'OIDC_SERVER_APPLICATION_URL'='' -e 'OIDC_TLS_CACERTFILE'='' -e 'WEB_SERVER_CONCURRENCY'='' -e 'WEB_SERVER_KEEPALIVE'='' -e 'WEB_SERVER_MAX_REQUESTS'='' -e 'WEB_SERVER_MAX_REQUESTS_JITTER'='' -e 'WEB_SERVER_TIMEOUT'='' -e 'WEB_SERVER_WORKER_CONNECTIONS'='' -e 'FORCE_COLOR'='' -e 'NO_COLOR'='' -e 'DISABLE_EMULATOR_JS'='false' -e 'DISABLE_RUFFLE_RS'='false' -e 'YOUTUBE_BASE_URL'='' -e 'UPLOAD_TIMEOUT'='' -e 'SCAN_TIMEOUT'='' -e 'SCAN_WORKERS'='' -e 'TASK_TIMEOUT'='' -e 'TASK_RESULT_TTL'='' -e 'SEVEN_ZIP_TIMEOUT'='' -e 'ENABLE_RESCAN_ON_FILESYSTEM_CHANGE'='false' -e 'RESCAN_ON_FILESYSTEM_CHANGE_DELAY'='' -e 'ENABLE_SCHEDULED_RESCAN'='false' -e 'SCHEDULED_RESCAN_CRON'='' -e 'ENABLE_SCHEDULED_UPDATE_SWITCH_TITLEDB'='false' -e 'SCHEDULED_UPDATE_SWITCH_TITLEDB_CRON'='' -e 'ENABLE_SCHEDULED_UPDATE_LAUNCHBOX_METADATA'='false' -e 'SCHEDULED_UPDATE_LAUNCHBOX_METADATA_CRON'='' -e 'ENABLE_SCHEDULED_CONVERT_IMAGES_TO_WEBP'='false' -e 'SCHEDULED_CONVERT_IMAGES_TO_WEBP_CRON'='' -e 'ENABLE_SCHEDULED_RETROACHIEVEMENTS_PROGRESS_SYNC'='false' -e 'SCHEDULED_RETROACHIEVEMENTS_PROGRESS_SYNC_CRON'='' -e 'LOGLEVEL'='INFO' -e 'SENTRY_DSN'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]' -l net.unraid.docker.icon='' -p '8383:8080/tcp' -v '/mnt/user/pool5/games/Arcade/':'/romm/library/':'ro' -v '/mnt/user/appdata/romm/resources':'/romm/resources/':'rw' -v '/mnt/user/appdata/romm/assets':'/romm/assets/':'rw' -v '/mnt/user/appdata/romm/config':'/romm/config/':'rw' -v '/mnt/user/appdata/romm/redis-data':'/redis-data':'rw' -v '/mnt/user/pool6/games':'/romm/library2':'ro' 'rommapp/romm:latest'Nothing fancy You only need a single directory of files to replicate roms are located here: - "library/Nintendo 64/roms" - "libary/Nintendo 64/Europe" all other systems are similar or flat atari would be flat "library/Atari 2600/"

This is pretty easy to duplicate and test emulatorjs: cache_limit: null controls: {} debug: false disable_auto_unload: false disable_batch_bootup: false netplay: enabled: false ice_servers: [] settings: {} I have a bunch of excludes dont think its relevant for this discussion. filesystem: firmware_folder: bios roms_folder: library #this picks up all 27 specified platforms but 0 roms system: platforms: Nintendo 64: n64 versions: {} roms are located here: - "Nintendo 64/roms" - "Nintendo 64/Europe" It's entirely possible a skill issue but everything I can find points to a rigid file structure requirement. Run a scan 0 are picked up The "ERRORs" also point to the same file structure issue. ERROR: [RomM][scan][2026-05-10 00:28:44] ROMs not found for platform Nintendo 64. Check RomM folder structure here: https://docs.romm.app/latest/Getting-Started/Folder-Structure/ for more details INFO: [RomM][scan][2026-05-10 00:28:44] Found 27 platforms in the file system INFO: [RomM][scan][2026-05-10 00:28:44] Folder n64[Nintendo 64] identified as Nintendo 64 🎮 WARNING: [RomM][scan][2026-05-10 00:28:44] ⚠️ No firmware found for Nintendo 64[Nintendo 64] ERROR: [RomM][scan][2026-05-10 00:28:44] ROMs not found for platform Nintendo 64. Check RomM folder structure here: https://docs.romm.app/latest/Getting-Started/Folder-Structure/ for more details The only way I can get it to semi work is to change. roms_folder: roms -> does not actually exist I also specified 27 platforms and it only picks up 8. Then it will pick up - "Nintendo 64/roms" but not - "Nintendo 64/Europe" It does not like to be told what files to look in for a specific system. I even tried to enable debug to see if it would tell me the directories it was looking in and debug does nothing. scan: debug: true autodetect: true export_gamelist: false I thought this might be a cool way to download files to my AYN thor so I only set up the platforms that I have on my AYN thor and excluded all the other platforms. But nope unfortunately this doesnt appear to presently possible unless I am willing to change my entire directory structure.

Looks like it's a terms of service issue. You must accept the terms of service, I can post on my phone I got the pop up but not a pc web browser. I get no pop up for terms of service on the PC. I am not going to try an type out the issue on a phone. This app RomM app isn't worth the hassle. They have chosen a rigid file structure with their "new" rollout. You used to be able to give it a path. n64: paths: - "Nintendo 64/roms" - "Nintendo 64/Europe" For whatever reason they abandoned that and went with this new rigid structure which is inflexible. Some of my rom directories have no "roms" folder at all and are just flat. nes: paths: - "Nintendo Entertainment System" This would also violate their current folder structure requirement since you must have one or the other. I spent a day trying to get it to work. If you are just starting out and you are ok with their rigid file structure then this app will probably work fine. If you have an already established collection or roms/emulators then this app in its current form will not work.

there documentation is pretty clear they expect a rigid file structure. So you must bend to the will of the tool and not use the folder structure you want. You must use the folder structure they want you to use. https://docs.romm.app/latest/Getting-Started/Folder-Structure/?utm_source=copilot.com#folder-organization I dont know the magic dance required to post a question. Like I said getting support is not easy for this app

Same problem I had. Support appears to be non existent

Dont know how many folks have tried using this. It seems like a cool idea but it lacks execution. It expects you to name the folder the way it wants you to. If you have a different folder structure then it expect good luck getting this to work. I have spent hours on the stupid config.yml file filesystem: firmware_folder: bios roms_folder: library n64: paths: - "Nintendo 64/roms" - "Nintendo 64/Europe" system: platforms: Nintendo 64: n64 ERROR: [RomM][scan][2026-05-10 00:28:44] ROMs not found for platform Nintendo 64. Check RomM folder structure here: https://docs.romm.app/latest/Getting-Started/Folder-Structure/ for more details INFO: [RomM][scan][2026-05-10 00:28:44] Found 27 platforms in the file system INFO: [RomM][scan][2026-05-10 00:28:44] Folder n64[Nintendo 64] identified as Nintendo 64 🎮 WARNING: [RomM][scan][2026-05-10 00:28:44] ⚠️ No firmware found for Nintendo 64[Nintendo 64] ERROR: [RomM][scan][2026-05-10 00:28:44] ROMs not found for platform Nintendo 64. Check RomM folder structure here: https://docs.romm.app/latest/Getting-Started/Folder-Structure/ for more details Although if I go look for the roms they exist in the docker container If I change roms_folder: to something that doesnt exits It will kind of work it will find 8 platforms and all the roms under those 8 platforms. This is extremely buggy software. I cant recommend this one unless your starting from scratch and willing to use the folder structure/names they appear to have hard coded into the system.

just here to report the same. Fails with 7.2.5 I will also need to roll back 7.2.4 as I use this quite a bit

Think you might have a minor bug debug="{defaultDebug}" should be debug="${defaultDebug}"

I believe unraid previously used port 22 to SSH to do USB backup if that failed it would fall back to 443? I block outbound port 22 on my network and with 7.2.0 it fails USB backup because it cant get to port 22. Is there a way to divert to 443? Or is there something extra I need to configure to get it to use 443?