February 22, 20233 yr 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
February 22, 20233 yr Community Expert 5 minutes ago, Amagner said: 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. This looks more like a BIOS config problem, it the UEFI flash drive the first boot option when the disks are connected?
February 22, 20233 yr Author 11 minutes ago, JorgeB said: This looks more like a BIOS config problem, it the UEFI flash drive the first boot option when the disks are connected? Yes I can confirm that the bios is set to boot off the usb and in UEFI mode.
February 22, 20233 yr Author 5 minutes ago, JorgeB said: Can you post a photo of the BIOS boot page? Will do Once I am home thanks for the quick replys I will drop it in here 7 Hours
February 23, 20233 yr Author 9 hours ago, JorgeB said: Can you post a photo of the BIOS boot page? 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.
February 23, 20233 yr Community Expert Oh, I remember that from another user before, that's not about the flash drive, it's telling you one of the drives has a corrupt partition, boot Unraid and post the output of fdisk -l /dev/sdX for all drives
February 23, 20233 yr Author 14 hours ago, JorgeB said: Oh, I remember that from another user before, that's not about the flash drive, it's telling you one of the drives has a corrupt partition, boot Unraid and post the output of fdisk -l /dev/sdX for all drives 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.
February 24, 20233 yr Community Expert No need for maintenance mode, it can be done with the array stopped. 9 hours ago, Amagner said: just type exactly that? fdisk -l /dev/sdX Replace X with correct letter for each disk connected to the onboard SATA controller, usually sdb, sdc, sdd, etc, if you don't you can post the diags so we can check.
February 25, 20233 yr Author On 2/24/2023 at 4:02 AM, JorgeB said: No need for maintenance mode, it can be done with the array stopped. fdisk -l /dev/sdX Replace X with correct letter for each disk connected to the onboard SATA controller, usually sdb, sdc, sdd, etc, if you don't you can post the diags so we can check. 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
February 25, 20233 yr Community Expert The command is meant to be run by opening a Console session to get to the linux command line (started by the >_ icon at the top right of the GUI), not from the repair section of the GUI
March 1, 20233 yr Author On 2/24/2023 at 4:02 AM, JorgeB said: No need for maintenance mode, it can be done with the array stopped. fdisk -l /dev/sdX Replace X with correct letter for each disk connected to the onboard SATA controller, usually sdb, sdc, sdd, etc, if you don't you can post the diags so we can check. 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?
March 1, 20233 yr Community Expert Solution You could have separated the output by disk better but unless I'm missing something no GPT errors detected, you'll need to connect one disk at a time to see which one the board is having issues with.
March 4, 20233 yr Author 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
March 22, 20233 yr Author On 3/1/2023 at 3:47 AM, JorgeB said: You could have separated the output by disk better but unless I'm missing something no GPT errors detected, you'll need to connect one disk at a time to see which one the board is having issues with. 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.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.