footballmad

Damnnnnnnnnn, thanks so much Jorge, it worked on disk21 I'll do the same on the other disks. You really know your stuff and I can't thank you enough.

At the time of starting the array, I was sitting in front of the console and this appeared. Don't know if that can help in any way.

OK, I'll look into that if we can manage to recover the others.

This is the result for disk21 root@MSSTORAGE:~# fdisk -l /dev/sdac The primary GPT table is corrupt, but the backup appears OK, so that will be used. Disk /dev/sdac: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors Disk model: ST3000DM001-1ER1 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: 205CED32-7A0F-4E32-81F6-36E483C5065F Device Start End Sectors Size Type /dev/sdac1 64 5860533134 5860533071 2.7T Linux filesystem Then I started the array and the error remains.

Because the disk was failing. I'll post the results once home.

It's not something I really use, so I guess it's best to uninstall?

I know what a lot of it is for, I guess the only reason is being a wannabe nerd, trying to learn as much as I can. I appreciate your time too trurl

Thanks for taking a look Jorge msstorage-diagnostics-20210812-2015.zip

I'd love people's ideas on if there's a possible recovery and how to proceed.

Yes and all these disks are connected tot the old card as before, when I did that I was hoping that UNRAID would see them as before and that it was possibly a "bug" with the Adaptec ASR-5405 card.

Oh no, not what I wanted to hear. Would you recommend using the -L flag? From another post here, what's your opinion on this? Do you think the fact that I tried a different expansion card could've caused this? Any ideas on how to attempt recovery?

I'm not home right now but I believe it's the 4 disks you mention. I did this from the webUI, I forgot to mention in my previous posts, these disks are encrypted.

I ran this sgdisk command and these are the results. root@MSSTORAGE:~# sgdisk -v /dev/sdc Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Main header: OK Backup header: ERROR Main partition table: OK Backup partition table: ERROR Invalid partition data! Verification may miss some problems or report too many! Caution: The CRC for the backup partition table is invalid. This table may be corrupt. This program will automatically create a new backup partition table when you save your partitions. Warning! Mismatched GPT and MBR partition! MBR partition 1, of type 0x83, has no corresponding GPT partition! You may continue, but this condition might cause data loss in the future! Identified 2 problems! Does this information help anyone that knows more than me about this?

Hi, Since a week or so, I've been having problems with my server, disk 17 and 19 were reporting errors. I wanted to replace disk 17 with a new disk so shutdown the server and changed disks. Upon reboot there were more errors on other disks, all using the same icybox bay (5xhdds) and breakout cable, so I changed cables and no change, thinking it was maybe the card I plugged in an old Adaptec ASR-5405 I had lying around and connected the bay to this card and restarted, I then had the error "mount error: Unsupported partition layout" on 4 of the disks. Thinking that maybe the card wasn't compatible with UNRAID (yes I should have checked first), I disconnected the card and reconnected as before but the error remains on all these drives. I tried a xfs_repair (first with -n then without) and no change. I searched on the forum and found this thread that mentions the Adaptec ASR-5405 and mount error: Unsupported partition layout errors, so I tried connecting one of the drives directly to the motherboard through SATA and still no change. I also wanted to try mounting the drive using Unassigned devices but instead of "mount" it wants a format, so obviously I stopped there. Can anyone please help me recover these drives please? msstorage-diagnostics-20210806-1936.zip

So no risk for the encrypted disks in s potentially wrong slot?

The 5 five disks on my system are encrypted, if I don't put the disks in their previous configuration, is there any risk to data?

Hello, After updating to version 6.9.2 and rebooting, all disks were unassigned and a "Stale Configuration" message was displayed in the bottom left corner. I haven't yet started the array. What are the risks of assigning the disks back to how they were before (I have some old screenshots) but potentially assigning a previous disk to the wrong slot, i.e. Previously Disk 1 to Disk 2 ?? I'm 99% sure that the 2 parity disks are as they were before and have assigned these but have the warning, "All existing data on this device will be OVERWRITTEN when array is Started" Any advice is very welcome and any ideas as to why this happened also welcome. EDIT: Changed "invalid" to "Stale" msstorage-diagnostics-20210502-1021.zip

Thanks for your reply, so I can forget it for docker containers then.

So what's the point in isolating cores? Sorry if I've misunderstood.

Thanks for the reply, I guess it was this part of the video I must have misunderstood. My question now is, is there any way at all to pin multiple cpu cores exclusively for docker applications? Thanks

More info that should be useful. The error stated above says that Plex "will only execute on a single isolated core" As you can see here, I pinned 10-15,26-31 for Plex. On the dashboard I have this, clearly showing one core at 100% Did I misunderstand advanced tweaks from @SpaceInvaderOne ???? Many thanks

After reading what I wrote I would like to clarify, If I understand correctly, I could pin Plex to 4 cores but it will only ever use one? Is that correct?

Hi, After watching many of the excellent videos by SpaceInvader One, I decided to isoloate some cpus from UNRAID and the pin them to one VM and my Plex docker. However since doing this I have this error message from the "fix common problems" plugin, ERRORS FOUND SUGGESTED FIX Docker Application plex has multiple CPUs pinned to isolated CPUs Unless you know exactly what you are doing, pinning a docker application to multiple isolated CPUs will only allow the application to execute on a single isolated core and adjust either the Isolated CPUs or the application's CPU pinning I upgraded to Version 6.6.0 the other day without issue. Here's the line I added, isolcpus=4-15,20-31 and wanted to pin 4 or 6 cores to Plex. https://youtu.be/p0iPpPyebUw?t=517 Any advice please?

Thanks for all these userful docker containers, 90% of mine are from you guys. I know this is not a question related specifically to this container (as it installs and works without any visible problems) but could someone please point me in the right direction for documentation in setting kodi up once installed. I mean I've used Kodi for years but always with a GUI so setup that way is simple and something I've done many times. This is what I've tried so far. Added a mediasources.xml with this format <mediasources> <network> <location id="0">smb://myusername:mypassword@myserver/Movies</location> <location id="1">smb://myusername:mypassword@myserver/TV Series</location> <location id="2">smb://myusername:mypassword@myserver/Music</location> </network> </mediasources> I've also added a sources.xml with this format <sources> <programs> <default pathversion="1"></default> </programs> <video> <default pathversion="1"></default> <source> <name>TV Series</name> <path pathversion="1">smb://10.0.0.50/TV Series/</path> <allowsharing>true</allowsharing> </source> I've then connected (successfully) with YATSE app from my android and send the "update video" command but no updates to the library occur. Any advice is welcome. Thanks