0edge

It works, it’s the UNRAID UI that displays it weird. My mirror says “this is a pool of 2 drives”, but the RAIDZ1 just shows the single sdh drive and the other 3 show up under “unassigned”

I need to know if it’s enough for all of them to go by-partuuid before I replace the sdh drive with my spare to force it to be by-partuuid from the beginning. This will take time and resilvering. I suspect that’s the only thing that would work, if Unraid doesnt fix this bug. The offlining does not work because at the very least the replace command leads to a resilver, and i’m not resilvering 3 drives instead of just the 1 to make it by-partuuid like the others.

You get an error that you can’t replace a drive with itself, like I said. However, are you saying Unraid will simply not detect any drive that does not go by /dev/sdX? I’m starting to think that’s the case (i thought surely if they were all the same aka by partuuid, unraid would not be confused). This is pretty shortsighted, especially since /dev/sdX is not actually recommended and people may be migrating their ZFS pools from elsewhere. Unraid should detect all drives as provided by the zpool status command…

I tried offlining sdh and replacing with itself with its by-partuuid like the others. It said you can’t replace a drive with itself. Sdh is different because it is the drive that failed and i had to replace back under 6.11.5 i did a manual replace with another disk and it ended up going by dev/sdh instead of partuuid. i can’t recreate the whole pool. Should be possible to remove the drive and add it back as a new drive but by its by-partuuid. It would have to resilver all over again. Would that work, Does unraid just want them all by partuuid?

I've upgraded from 6.11.5 to 7.0, and after a lot of debugging here is what I see is happening. Everything works, but the UI shows my 4-drive RAIDZ1 incorrectly. The reason is because it maps the /dev/sdh1 drive in the UI but not the /by-partuuid/ drives. In the syslog, the zfs import command only includes /dev/sdh1 . You can see for the "hddm-storage" mirror import command it includes both /dev/sdc1 and /dev/sdb1 . I figured out that it simply needs to import the pool like this "zpool import -d /dev/disk/by-id <pool-name>" but it doesn't and i can't force it to. The best I was able to do was start a new config with just the hddm-storage and not the hdd-storage 4-drive RAIDZ1, and manually import hdd-storage with "-d /dev/disk/by-id" , THEN add the pool, and THEN the UI shows all 4 drives BUT to the right it says "unable to mount this pool" so it's bugged THAT way instead. How can I make it import the hdd-storage pool with "by-id" or at least all uniformly so that one drive (sdh1) isn't different from the others which then confuses the UI reporting?

Thanks, tried 6.12 this morning (also interested in the newer kernel for my quicksync issues), but it detected my ZFS mirror but not my RADIZ1. I selected the 4 drives, and identified it as a RAIDZ1 but wouldn't work. So i updated the BIOS as you pointed out and back on 6.11.5 re-running scrubs. I will try memtest at some point too thanks.

I underclocked it to 3200mhz, it's a 3600mhz kit.

I opened up the PC and reseated RAM, lowered RAM from 3600mhz to 3200mhz, reseated HBA card, replaced HBA card SATA cables and moved cables to other slot. I have the RAIDZ4 on the LSI HBA card, and the mirror on the motherboard SATA, all with brand new cables. Why do I keep getting CKSUM errors? Every time it's a different random file with an error. Also the mirror should be rock solid running off the mobo (even if HBA is bad) and brand new cables and barely used drives. What is going on here?

Ugh i also had a weird situation where radarr could not copy a movie over from my downloads folder due to some "IO error", it would fail at 13gb copied every time. I had to delete the file. These are 4x14tb in RAIDZ1 ( Western Digital Ultrastar DC HC530 WUH721414ALE6L4 0F31284 14TB ). here's some more info I deleted the file and a scrub is running. This 4x14tb RAIDZ1 array is the only 4 disks running off a 9211-8i 6Gbps LSI HBA. Disks are all at 33-34C with fans in their face, the HBA does not have a dedicated fan but I do have a fan on the side panel which should be hitting it....

Got home to a false degraded pool error and lots of "ereport.fs.zfs.deadman" in the logs. Restarted and everything is fine. Also been having a lot of the ACPI error. This is a brand new 12700k system, any input? Mar 14 15:06:22 GUNRAID kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Mar 14 15:06:22 GUNRAID kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) Mar 14 15:06:22 GUNRAID kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP.\_DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529) Mar 14 15:06:47 GUNRAID zed[21232]: Diagnosis Engine: error event 'ereport.fs.zfs.deadman' Mar 14 15:06:47 GUNRAID zed[21232]: Diagnosis Engine: error event 'ereport.fs.zfs.deadman'

It was my own stupidity, another IOT device in my network was grabbing the same IP as my unraid box, it's solid smooth now! Please close this thread.

Bump

I'm running Unraid on this new system below and every once in a while I am unable to connect to the Unraid UI or docker containers (lasts 10-20 seconds) in the browser. I have attached my logs, the issue had just happened (UI hung and came back) when I downloaded them. I was watching corefreq-cli when it froze so I know exactly when it happened. I don't know what triggers the issue or how often it happens. I also had the syslog open which doesn't seem to show anything when the hangs happen. Is there any known issues with the intel 2.5gb nic in the Z690 TUF? Anyone using this motherboard? Any help appreciated. gunraid-diagnostics-20230311-0952.zip

Anyone getting slowdowns where UI becomes unresponsive and won't reload, same with containers, and even the terminal won't respond for 10-30 seconds? I just put this system together, any input appreciated. I even disabled e-cores. What settings are you guys using in the bios with regards to over/underclocking, power states etc? Is there maybe some incompatibility with c-states or something?