WCA
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by WCA
-
-
13 hours ago, limetech said:
Posting snippets of stuff doesn't help. Please post diagnostics.zip
Can I post diagnostics.zip from 6.7.2? I'm hesistant to upgrade to RC4 again in fear of data loss
-
1 hour ago, testdasi said:
Did it happen on 6.8.0-rc1? If it didn't then I don't think it's related to 6.8-rc - you might have an actual problem at hand and not just a bug.
I went straight from 6.7.2 to RC2 or RC3 i think
I downgraded back to 6.7.2, issues are gone now. -
Since (atleast) 6.8rc2 I've been getting read errors on multiple disks in my array (across controllers, both on my HBA (Dell H200) and my integrated controller (Intel), I spin down my disks after 4 hours, and the problem seems to only occur when disks are spun down.
It's the same problem this user on reddit seems to have:https://www.reddit.com/r/unRAID/comments/dmxcr5/am_i_playing_with_fire/
My Specs are:
Quotei5 4590
ASRock B85m Pro 4Dell PERC H200 HBA
Seasonic Focus + Gold 550 PSU
32GB DDR3 RAM
Storage consists of the following:Quote[0:0:0:0]disk Samsung Flash Drive 1100 /dev/sda 32.0GB
[1:0:0:0]disk ATA WDC WD40EFRX-68N 0A82 /dev/sdb 4.00TB
[2:0:0:0]disk ATA WDC WD40EFRX-68N 0A82 /dev/sdc 4.00TB
[3:0:0:0]disk ATA Samsung SSD 840 6B0Q /dev/sdd 512GB
[4:0:0:0]disk ATA Samsung SSD 840 6B0Q /dev/sde 512GB
[5:0:0:0]disk ATA WDC WD40EFRX-68N 0A82 /dev/sdf 4.00TB
[6:0:0:0]disk ATA WDC WD40EFRX-68N 0A82 /dev/sdg 4.00TB
[7:0:0:0]disk ATA MB4000GDUPB HPG4 /dev/sdh 4.00TB
[7:0:1:0]disk ATA MB4000GDUPB HPG4 /dev/sdi 4.00TB
[7:0:2:0]disk ATA MB4000GDUPB HPG4 /dev/sdj 4.00TB
[7:0:3:0]disk ATA MB4000GDUPB HPG4 /dev/sdk 4.00TB
And for what it's worth, here is the entire hardware map:Quote[8086:0c00]00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
[8086:0c01]00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
[8086:0412]00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
[8086:8c31]00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
[8086:8c3a]00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
[8086:153b]00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 05)
[8086:8c2d]00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
[8086:8c10]00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
[8086:244e]00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d5)
[8086:8c26]00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
[8086:8c50]00:1f.0 ISA bridge: Intel Corporation B85 Express LPC Controller (rev 05)
[8086:8c02]00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
[8086:8c22]00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
[1000:0072]01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
[1b21:1080]03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)
I will attach logs for the last few hours:
Oct 24 23:46:52 PLEXSCH kernel: blk_update_request: critical medium error, dev sdh, sector 4026569360 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569296 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569304 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569312 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569320 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569328 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569336 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569344 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569352 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569360 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569368 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569376 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569384 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569392 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569400 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569408 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569416 Oct 24 23:47:04 PLEXSCH kernel: blk_update_request: critical medium error, dev sdj, sector 4026569360 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569296 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569304 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569312 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569320 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569328 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569336 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569344 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569352 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569360 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569368 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569376 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569384 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569392 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569400 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569408 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569416 Oct 24 23:47:05 PLEXSCH kernel: blk_update_request: critical medium error, dev sdk, sector 4026569360 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569296 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569304 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569312 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569320 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569328 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569336 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569344 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569352 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569360 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569368 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569376 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569384 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569392 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569400 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569408 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569416
Unraid OS version 6.8.0-rc4 available
-
-
-
-
-
in Prereleases
Posted
I get that, but I think it's safe to say it's a better idea to go back to stable than to keep messing around on a release that potentially corrupts my data right?
I regret having updated to a beta release already, I'm not doing that again. Hoping it will be fixed by the final release. I won't be able to provide diagnostics, so I hope that someone else will be able to provide them.
I'm sorry, but I just don't want to lose any data. If a Limetech employee would confirm that these errors are not destroying any data, I'd be willing to upgrade temporarily to provide the diagnostics though.