Mezhom

So i waited for 7.2.0 to be released. Did the update and no issues. Smooth transition.

Updated from 6.12.14 to 7.0.1 pretty sure i have 24 disk devices total. Updated docker and plugins. Then went to update unraid. waited 45 min, no boot. Hooked up a monitor. Kept hanging at different spots in the boot. tried about 7 boots. One with hot swap bays pulled. One as a safe boot. Manually rolled back my usb boot to 6.12.14 and worked fine. Time for issues in my log would've been between 9:15 and 10:30. After 10:30 i rolled back and managed to get back up and running rolled back. Any input before i try to update later on? Thank you! mserver-diagnostics-20250322-2244.zip

I moved from the sata ssd cache to a NVME cache that has fixed the BTRFS errors. Driver issue also gone. Fixing permissions has fixed docker stability. Reboots seem to work with usb in the 2.0 and the UPS in a usb 3.0. found it odd the UPS would cause it not to boot with both in a 3.0. I knew moving to a different platform would give a few issues but i expected more a UEFI, driver or chipset problem. Thank you for the guidance of pointing out it was an SSD that i had initially missed.

So Drive SDB is a SSD in raid 1 for my app data cache. There would be 4 devices on that cable and backplane, LSI 9305 24i so 6 cables one to each backplane. Each backplane is 4 drives. Drive SDX is the mirror to the drive above. (SDB) one other repeating error since i migrated to a new platform: Apr 10 19:43:52 MServer kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Apr 10 19:43:52 MServer kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Apr 10 19:43:52 MServer kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Apr 10 19:43:52 MServer kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Apr 10 19:43:52 MServer kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Apr 10 19:43:52 MServer kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Apr 10 19:43:52 MServer kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Apr 10 19:43:52 MServer kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Apr 10 19:43:55 MServer kernel: BTRFS error (device sdx1: state EA): parent transid verify failed on logical 2143535104 mirror 2 wanted 1525437 found 1525432 Apr 10 19:43:55 MServer kernel: BTRFS error (device sdx1: state EA): parent transid verify failed on logical 2143535104 mirror 1 wanted 1525437 found 1525432 Apr 10 19:43:55 MServer kernel: BTRFS error (device sdx1: state EA): parent transid verify failed on logical 2143535104 mirror 1 wanted 1525437 found 1525432

Small Update, Updated Motherboard Bios and fixed unraid permissions. I also had the boot USB in a usb 3.0 slot which seemed fine unless the UPS was also plugged in, seems alleviated with having the boot in a 2.0 slot. I will have to wait till tomorrow to check for errors, i will post a diagnostic tomorrow. I have one on boot: Apr 9 22:27:13 MServer kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Apr 9 22:27:13 MServer kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Apr 9 22:27:13 MServer kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Error that still repeats in the log: Apr 9 22:32:43 MServer kernel: sd 1:0:0:0: device reset: FAILED scmd(0x000000003c043558) Apr 9 22:32:43 MServer kernel: scsi target1:0:0: attempting target reset! scmd(0x000000003c043558) Apr 9 22:32:43 MServer kernel: sd 1:0:0:0: [sdb] tag#1928 CDB: opcode=0x2a 2a 08 00 00 08 80 00 00 08 00 Apr 9 22:32:43 MServer kernel: scsi target1:0:0: handle(0x002b), sas_address(0x300062b205f4f152), phy(18) Apr 9 22:32:43 MServer kernel: scsi target1:0:0: enclosure logical id(0x500062b205f4f140), slot(8) Apr 9 22:32:43 MServer kernel: scsi target1:0:0: enclosure level(0x0000), connector name( ) Apr 9 22:32:43 MServer kernel: scsi target1:0:0: target reset: SUCCESS scmd(0x000000003c043558) Apr 9 22:32:44 MServer kernel: sd 1:0:0:0: Power-on or device reset occurred Apr 9 22:32:51 MServer kernel: sd 1:0:0:0: attempting task abort!scmd(0x0000000062bae2ce), outstanding for 7045 ms & timeout 7000 ms Apr 9 22:32:51 MServer kernel: sd 1:0:0:0: [sdb] tag#2020 CDB: opcode=0x12 12 00 00 00 fe 00 Apr 9 22:32:51 MServer kernel: scsi target1:0:0: handle(0x002b), sas_address(0x300062b205f4f152), phy(18) Apr 9 22:32:51 MServer kernel: scsi target1:0:0: enclosure logical id(0x500062b205f4f140), slot(8) Apr 9 22:32:51 MServer kernel: scsi target1:0:0: enclosure level(0x0000), connector name( ) Apr 9 22:32:51 MServer kernel: sd 1:0:0:0: task abort: SUCCESS scmd(0x0000000062bae2ce) Apr 9 22:32:52 MServer kernel: sd 1:0:0:0: Power-on or device reset occurred Apr 9 22:33:27 MServer kernel: sd 1:0:0:0: attempting task abort!scmd(0x00000000b9e4230c), outstanding for 30360 ms & timeout 30000 ms Apr 9 22:33:27 MServer kernel: sd 1:0:0:0: [sdb] tag#1876 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Apr 9 22:33:27 MServer kernel: scsi target1:0:0: handle(0x002b), sas_address(0x300062b205f4f152), phy(18) Apr 9 22:33:27 MServer kernel: scsi target1:0:0: enclosure logical id(0x500062b205f4f140), slot(8) Apr 9 22:33:27 MServer kernel: scsi target1:0:0: enclosure level(0x0000), connector name( ) Apr 9 22:33:27 MServer kernel: sd 1:0:0:0: task abort: SUCCESS scmd(0x00000000b9e4230c) Apr 9 22:33:27 MServer kernel: sd 1:0:0:0: attempting task abort!scmd(0x00000000cbf14f21), outstanding for 30391 ms & timeout 30000 ms Apr 9 22:33:27 MServer kernel: sd 1:0:0:0: [sdb] tag#1875 CDB: opcode=0x2a 2a 08 00 00 08 80 00 00 08 00 Apr 9 22:33:27 MServer kernel: scsi target1:0:0: handle(0x002b), sas_address(0x300062b205f4f152), phy(18) Apr 9 22:33:27 MServer kernel: scsi target1:0:0: enclosure logical id(0x500062b205f4f140), slot(8) Apr 9 22:33:27 MServer kernel: scsi target1:0:0: enclosure level(0x0000), connector name( ) Apr 9 22:33:27 MServer kernel: sd 1:0:0:0: No reference found at driver, assuming scmd(0x00000000cbf14f21) might have completed Apr 9 22:33:27 MServer kernel: sd 1:0:0:0: task abort: SUCCESS scmd(0x00000000cbf14f21)

Im thinking there is something happening that is effecting plex. I can restart the server and plex works. then after being up for a day: Playback Error An error occurred loading items to play Radarr is effected(non responsive, fine after system reboot), sonarr is fine, minecraft server has "read only file errors" so currently updating permissions. But first lets work through the driver issue. mserver-diagnostics-20240409-2011.zip

Just moved from a Supermicro server to an Asus w680. 1: I attached a couple images of what looks like a repeated issue for a driver???? Not sure how to handle that. 2: The other issue is I can’t have my UPS plugged into the server. It won’t boot with it in. I was assuming a bios setting. As soon as I unplug the usb from the ups, it boots. 3: Plex has had stability issues but maybe that’s unrelated. I’d like to fix the first two and maybe Plex will smarten up by then. I am running in EFI.

i am also having the "Plex is not reachable" probably just have to wait it out. Unfortunately i think if we setup a server and host the application on our server why should we have to rely on their servers being up. Maybe just have a occasional authentication for premium subscribers or account stuff. weird thing is: pc app doesnt work browser doesnt work but ios phone app works hmm