i repeat, dont use the test-repo for production.
developers state its only for testing-purposes and not for production-use as evidenced by my screenshot from their own wiki.
you ignoring this is purely on you and on noone else.
you could have run...
Anyone experience better results on the newer kernels are we all still pinning to the older ones? With that bug report, I got one request for logs, but then silence since.
I wish I stayed on pve8 longer. After this issue, I pinned to 6.8.12-20-pve from 6.17.13-2-pve and have been stable since. Sadly, the original issue corrupted my zfs pool during a scrub, so I’ve been slowly restoring/rebuilding things from older...
I see this thread from 2021 and didn't want to necro it in case this is a different issue with the same result.
In my syslog, I get dozens of these messages at a time. Is this expected? From the prior thread, it sounded like a coder at some...
@wuselfaktor , fyi that I submitted https://bugzilla.proxmox.com/show_bug.cgi?id=7505 per a recommendation from @fiona in another thread about a different 6.17 kernel issue. I put a link to this thread in the bug report. Thank you again for your...
Just an FYI that since I uninstalled mdadm, I do not have that alert anymore. I sadly fell into another problem, but I've now gotten stable using steps outlined in that thread. I wouldn't be surprised if that problems was contributing to seeing...
OMG Thank you! I am seeing the same issue and keep suffering zfs pool corruption the last few days. I just pinned back to 6.8.12-20-pve from 6.17.13-2-pve to see if it helps. I have a Raptor Lake (i5-13500) processor. I will try pinning to the...
I don't ever recall explicitly installing mdadm (but I could have just forgotten), but no, I've never used a software raid until I defined the zfs inside TrueNAS. When I do an apt remove mdadm, I do see the following list of packages to be...
And the spinners look good too, if I'm reading this right.
When I spin up the VM again, I get these messages:
Apr 05 18:22:36 <node> kernel: md/raid1:md126: Disk failure on sda1, disabling device.md/raid1:md126: Operation continuing on 2...
I removed the startup option on TrueNAS, rebooted the host, and ran smartctl to check for things:
nvme0n1 is the boot SSD, so ignoring that drive.
So the NVMe look good, right? Spinners in the next post due to character limits.
I need some help understanding the alert I received today. I'll give some background, but I'll hide it as a spoiler in case the extra detail isn't relevant.
Today I received the following alert:
DegradedArray event detected on md device...