Amagner

That was it there was two drives causing this issue, once I replaced them issue is no longer happening thanks again everyone now i got another issue my graphic card settings deletes my plex and I have to redownload it everytime but ill make a new room for that one.

hmmmm thats heavy to do but I will get on that next weekend when im back from vacation thank you so much for the constant help @JorgeB and @itimpi

root@RetroShare-Plex:~# fdisk -l /dev/sdb Disk /dev/sdb: 14.55 TiB, 16000900661248 bytes, 31251759104 sectors Disk model: ST16000NM000J-2T 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: 8B9B98F0-7E6B-438E-BB75-7856D6FFBEAB Device Start End Sectors Size Type /dev/sdb1 64 31251759070 31251759007 14.6T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdm Disk /dev/sdm: 14.55 TiB, 16000900661248 bytes, 31251759104 sectors Disk model: ST16000NM000J-2T 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: CD1194AD-7327-40B2-A92A-26B693B8AA18 Device Start End Sectors Size Type /dev/sdm1 64 31251759070 31251759007 14.6T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdi Disk /dev/sdi: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: ST10000VN0008-2J 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: 563185E3-3A46-4C9A-BAD1-CE8F6C30E94F Device Start End Sectors Size Type /dev/sdi1 64 19532873694 19532873631 9.1T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sde Disk /dev/sde: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: ST8000AS0002-1NA 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: 7E554C3A-8C4A-46D6-989D-072FCEEDAF98 Device Start End Sectors Size Type /dev/sde1 64 15628053134 15628053071 7.3T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdh Disk /dev/sdh: 14.55 TiB, 16000900661248 bytes, 31251759104 sectors Disk model: ST16000NE000-2RW 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: 9E3CFB9D-9377-47F2-80A9-D8027BD9A9D8 Device Start End Sectors Size Type /dev/sdh1 64 31251759070 31251759007 14.6T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdc Disk /dev/sdc: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: ST10000VN0008-2J 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: 1EA3C911-7043-4B65-A683-14B0642764FA Device Start End Sectors Size Type /dev/sdc1 64 19532873694 19532873631 9.1T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdf Disk /dev/sdf: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: ST10000VN0008-2J 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: D3FDA4CA-F050-45A7-8879-34DD1FAE3038 Device Start End Sectors Size Type /dev/sdf1 64 19532873694 19532873631 9.1T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdj Disk /dev/sdj: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: ST10000VN0008-2J 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: C86A282D-9157-41A3-B9F3-E36910520568 Device Start End Sectors Size Type /dev/sdj1 64 19532873694 19532873631 9.1T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdi Disk /dev/sdi: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: ST10000VN0008-2J 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: 563185E3-3A46-4C9A-BAD1-CE8F6C30E94F Device Start End Sectors Size Type /dev/sdi1 64 19532873694 19532873631 9.1T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdd Disk /dev/sdd: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: ST10000VN0004-1Z 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: 5D0A15BE-7853-47D5-9CC2-786DD5994CBC Device Start End Sectors Size Type /dev/sdd1 64 19532873694 19532873631 9.1T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdk Disk /dev/sdk: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: ST10000NE0008-2J 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: 8BFD0268-3EF3-48F6-A554-4DD207D5A093 Device Start End Sectors Size Type /dev/sdk1 64 19532873694 19532873631 9.1T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdg Disk /dev/sdg: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: TOSHIBA HDWG11A 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: AFF02617-580D-4F25-9A8C-A483E384E460 Device Start End Sectors Size Type /dev/sdg1 64 19532873694 19532873631 9.1T Linux filesystem root@RetroShare-Plex:~# fdisk -l /dev/sdg Is this what we were looking for or am I doing this wrong?

I copied and pasted it to this section but its giving me a couple of options but nothing is happening, even put the letter according to what the drive is. not sure if I am doing this right

would i do this in maintenance mode? for each drive? just type exactly that? Just want to make sure where I am putting this and thanks for a swift reply.

Sorry got caught up with extreme adulting today ugh, here are the photos I took, theres times it won't boot up at all and stay black, then it gives me the gpt error and i have to unplug each sata cable, and then even when boot overriding it goes into a loop.

Will do Once I am home thanks for the quick replys I will drop it in here 7 Hours

Yes I can confirm that the bios is set to boot off the usb and in UEFI mode.

Hello, Recently Upgraded my server specs to ASUSTeK COMPUTER INC. TUF GAMING Z690-PLUS WIFI D4 , Version Rev 1.xx Motherboard and better CPU and more. I noticed with this new motherboard It gives me trouble booting to the unraid server. Would give me gpt header corruption and would just cycle to the bios. Only way I can boot to the unraid server is by first unplugging all my drives and leaving them unplugged and then starting it off the usb and then replug each and every drive. I did not have any issues with the server previously like this. I attached the diagnostic file but also I noticed my servers is also not working now and nothing has changed within the network. I have not rebooted the server but I am afraid to because of this GPT issue of booting which I never seen before. Would love if anyone can help open to many suggestions I never seen a motherboard forcefully do this so I am not aware what would be the next step. retroshare-plex-diagnostics-20230222-0918.zip

Alright so far everything is way better now and the parity only took 2 days to be done which is amazing, now the GPU is my problem everytime i try to setup a VM so i can do the passthrough trick it just freezes and then i have to completely restart the server in order to try again its frustrating and i can't get it to work without freezing the server. I also cannot stop it or start it only force stop nothing else works pretty much just impossible.

Yes i tried to setup a gpu to assist with the plex transcoding but im still learning how to do that so far the parity check runs well imma keep an eye on it for a week

Sorry for the long wait on this issue! so I managed to get everything during Amazon Prime day, got new Sata Cables, 3 new 16tb HDDs, and also a New Power supply with straight forward sata cables straight to the power supply no adapters. Cleaned cpu and reapplyed new thermal. Added a rtx 6600 graphic card that I need to setup somehow through VM ware i keep getting a error 127 when trying IDK. and then I also got the asmedia adapter replacing the marvell one. Last I added 3 new fans into the system for more air flow and cleared and cleaned every spot and nook and cranny. So i did all the changes and I am getting less reports on the unraid page and here is a updated diagnostic. I did do a parity test which I will do at 3am until 11am when no one is using the plex. But i think most things are running better if anyone can confirm let me know <3 retroshare-plex-diagnostics-20220722-2054.zip

Hope everyone had a good 4th, So I managed to save up money and I will be buying 2 12tb to replace the parities which will replace disk 2 and 10 that have been having issues but first I will replace the PSU and cables and then add fans then hard drives I will update in the next two weeks thanks for your patience.

Thanks for this information @JorgeB sorry but I am super noob to this and the only one that does maintain it. Constant ATA Errors = ? and seems to be affecting Parity, Disks 4 and Disks 8 I am assuming this is power? or Sata Transfer Cables? Also Marvell is not a good controller for Sata expansion? I do have PCI slots available and Also if possible can get sata 6gb recommendations I am open too. What cables would i need to replace? All sata and power cables? My whole power supply? I just want to make sure I do everything right. I will want to try and switch these drives as soon as possible. I did sit down and studied about switching drives in unraid. I cannot switch the any drive to be higher than the parity. So I would need to replace the parity drives first to 16tb each and then with those two 10's switch the two 8tb or the other drives that are faulting which i need to figure out how to tell. hope that is right as well, Also hope everyone is having a Happy 4th!

Heads up was just curious but completely stopped the array, did the -v to everydrive noticed drive 2 and 10 taking 4/5 minutes while others took 40secs or so. Also when doing the parity out of the array being up its still taking a lifetime.