hinton

Yep... Thankfully all important personal data is constantly backed up with rsync. Media can be replaced. Thanks for the resources here. Not making this mistake again 😝

Thanks, JorgeB. I never created a new configuration when I had disk issues last year, due to ignorance of how arrays really work. Good learning opportunity here. I think it was only media on this disk - I hope it was only media.

So my parity is useless because of this other disk that's never even been a part of the array? There's nothing else I can do here?

Ah, yes, Disk 5 was messed with, and I guess disabled(?), when I experienced a drive being read as another serial number. It's not really a part of the array and was disabled before parity was began. How do I move forward with that being the case?

Hi Unraid forums, I've got a machine with an HBA card hosting 7 HDDs for the array + 1 HDD for parity. It experienced a sudden power loss, and upon powering back up, one of the drives is dead. It makes a loud clicking noise and is not recognized by Unraid when plugged in. Note, I have not checked if it's recognized in BIOS because I'm assuming it's toast due to the sound. Despite that being the only missing drive, I'm receiving the "Too many wrong and/or missing disks!" message and cannot start the array. What do I do here to salvage data that was on this drive, considering I have parity? prodesk-diagnostics-20231129-2125.zip

What did you end up deciding? I use docker-compose everywhere else on my home network except Unraid, am starting to need to use docker-compose on Unraid, and am undecided whether to use Portainer or the Docker Compose plugin for it... The plugin seems a bit unwieldy so far, but I've only just started diving in.

Thanks again, Jorge

Rebuilding is only possible with parity, though, yes? I don't actually have parity right now, and was only just going to add it now that I have more drives. Considering that this disk in question is my largest disk and will become the parity drive, is my best bet then to manually copy the files over from the disk into the array, and then reformat for use as parity? Assuming I'm understanding rebuilding as a parity-only option correctly...

Thank you for the help! root@Prodesk:~# fdisk -l /dev/sdj The backup GPT table is not on the end of the device. Disk /dev/sdj: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: WDC WD80EMAZ-00W Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 8AC5ECEF-6945-4CFD-8CF1-3408CD26491B Device Start End Sectors Size Type /dev/sdj1 64 15628052446 15628052383 7.3T Linux filesystem

Diagnostics are attached. I'm not sure what details you want about the disk in question. It is Disk 4, an 8Tb WD drive shucked from an EasyStore case. WDC WD80EMAZ-00W as seen in lsscsi.txt Unraid shows it's XFS partitioned, lets me mount, and explore files, when it's in Unassigned Devices, but bring it into the Array and nope, "Unmountable: Unsupported partition layout" prodesk-diagnostics-20211220-0701.zip

Hey there, I just switched to a new machine, shucked one of the drives that was previously in an external USB enclosure, added it internally in the new case, and found that the UUID had changed from doing so, disallowing me from starting my array. So, I went to Tools -> New Config, reset my config, re-added the disk afterwards, and found that the disk is showing FS auto (rather than XFS), and Unmountable. So, I ran the xfs_repair tool via Unraid console on the disk, which appeared to show no errors or issues at all, really. And, when mounted as an Unassigned Device, all my files are still there. What gives? From the past two hours of reading I've been doing, the xfs_repair should be the ticket. But, nothing changes. I just added a bunch of new drives to the array as well (this issue was occurring before adding the new drives to the array, they were sitting in Unassigned Devices when I first tried New Config, etc.) so I'm debating just copying everything over from the drive to another one, but I'd much rather just get this working, instead.

I'm on Unraid 6.9.2 and am not having any issues with configuration persistence post-container restart. Although, I have not checked downloaded file privileges, yet. Also, the container was unbootable and gave errors in logs unless I used /data/* for the container paths, as shown in the docker-cli example in the repository, as quoted below: docker run -d --name soulseek --restart=always \ -v "/persistent/appdata":"/data/.SoulseekQt" \ -v "/persistent/downloads":"/data/Soulseek Downloads" \ -v "/persistent/logs":"/data/Soulseek Chat Logs" \ -e pgid=1000 \ -e puid=1000 \ -e resize=scale \ -e resolution=1280x720 \ -p 6080:6080 \ realies/soulseek Installation Instructions: Unraid -> Docker -> Add Container Toggle Advanced View in upper right Name: Soulseek Repository: realies/soulseek Docker Hub URL: https://hub.docker.com/r/realies/soulseek/ Icon URL: https://d36jcksde1wxzq.cloudfront.net/be7833db9bddb4494d2a7c3dd659199a.png WebUI: http://localiphere:6080 Network Type: Bridge Console Shell Command: Shell Port 1: Container Port: 6080 Host Port: 6080 (or whatever port you want to access container from) Path 1: Container Path: /data/.SoulseekQt Host Path: /mnt/user/appdata/soulseek Path 2: Container Path: /data/Soulseek Chat Logs Host Path: /mnt/user/appdata/soulseek/chatlogs Path 3: Container Path: /music Host Path: /mnt/user/music/ Variable 1: Name: PUID key: puid value: 99 Variable 2: Name: PGID key: pgid value: 100 Variable 3: Name: Resolution key: resolution value: 1600x900