BurntTech

I attached an image of what appears to be same number of errors across 6 out of 8 drives on this backplane. I'm running 24 drive bay with 3 of these 8 drive backplanes. I been second guessing this since SAS cable is SFF-8087 to SFF-8087 are 4 channels each and the disk 7 and 8 are running with out errors. Disks 7 and 8 are Different brand and model. Smart errors attached also show non medium errors pointing to issues other then the drives. I'm going to check if I have a backup backplane and SAS cables. I have some larger drives I was debating on doing a "test" upgrade to see if the new drive is having the same issue. Anyone seen only part of the SAS channels having issues before? SDE-Log.txt

nas-diagnostics-20220812-1631.zip So the only thing I can think of is there some weird bios setting. Since the RAID cards won't start because it looks like post halts unless you do something with the USB stick. Here are some of the options that been tested. I think I'm down to dumping BIOS options or creating a new USB install. If I move the USB to any port that isn't the one that it last booted from it works until the next reboot. if I remove the drive completely it boots but you need to plug the usb drive back in. If you just power off or restart the same post halt happens and just a black screen. It is a rendered black screen as the monitor stays lit until you power off. Is there an option for using a SSD instead of this USB drive yet? 🙂

Diag might not work so well since the System doesn't boot/post. I fear this is Bios Related or USB stick? This used to work I thought but is there any UNRaid ways to valid USB Stick? M/B: Micro-Star International Co., Ltd. PRO Z690-A DDR4(MS-7D25) Version 1.0 BIOS: American Megatrends International, LLC. Version 1.00. Dated: 09/14/2021 CPU: 12th Gen Intel® Core™ i5-12400 @ 2475 MHz

I'm dealing with same issue should I create my own thread or use this one? The current fix is for me to boot without USB stick then put the USB stick in and boots just fine

Ya I'm struggling with not wanting to run another type of VM host. I already have docker swarm cluster for fail-over and need a fail-over supported VM setup. Add this too the list as this is my number #1 as I already have two unraid servers

I hope RC is stable enough 🙂 Looks like its appearing I'll have to do some testing. ls -l /dev/dri/ total 0 drwxrwxrwx 2 root root 80 Mar 5 12:54 by-path/ crwxrwxrwx 1 root video 226, 0 Mar 5 12:54 card0 crwxrwxrwx 1 root video 226, 128 Mar 5 12:54 renderD128

Oh sorry about that I am running 6.9.2. I didn't have a i915.conf file do I need to create one of those? I did already installed the plugin from CA for intel top.

Should I see a message even if I put in 4692 this time? I can try again with 4690 too. cat /var/log/syslog | grep i915 Mar 5 11:33:11 NAS kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot i915.force_probe=4692 Mar 5 11:33:11 NAS kernel: Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot i915.force_probe=4692 [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS UEFI

I have the 12500 but with that force probe it wasn't working. Looking in the hardware page I saw my references 4692? I tried the force probe for that device too but no /dev/dri/. Anything else I should check? [8086:4692] 00:02.0 VGA compatible controller: Intel Corporation Device 4692 (rev 0c) default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot i915.force_probe=4692 label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest

Is there any reason why disk 14 didn't trigger failed disk with the errors during SMART test? For a failed disk can SMART fail due to a bad controller or cable?

Here it is! Thanks nas-diagnostics-20211009-1331.zip

The drive HUA says its being emulated? I couldn't find any log messages about this happening. It appears there is a section in the log attached " 0x03 0x028 4 1502 --- Read Recovery Attempts" Is this the issue my searches didn't come up with much this error. Second drive ST33 shows it has SMART errors and an issue in disk location plugin but the main dashboard shows healthy? I'm guessing disk location checked the smart errors but even the drive page says there is errors so why would this drive not get marked as failed? This one looks like a bunch of corrected errors that might be cable issue that is correctable and won't get marked as failed? This is a newer install, thanks for any advice! Hitachi_HUA723030ALA640_MK0331YHH44GZA-20211009-1030.txt ST33000650SS_B1_Z292JYVJ000092407XJF_35000c5004194216b-20211009-1051.txt