comet424 Posted May 30, 2020 Share Posted May 30, 2020 hi i been experiencing lot of slowness freezing of my windows when accessing my unraid there was soo much warnings i rebooted unraid forgot to save but when i rebooted i got other errors im guessing there is a hard drive error but i dont know which one it doesnt tell me specificlly maybe you can tell me if any of the warnings are normal and which warnings are not normal May 30 09:42:42 Tower kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA May 30 09:42:42 Tower kernel: tsc: Fast TSC calibration failed May 30 09:42:42 Tower kernel: ACPI: Early table checksum verification disabled May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] May 30 09:42:42 Tower kernel: pci 0000:02:02.0: BAR 14: failed to assign [mem size 0x00600000] May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 6: failed to assign [mem size 0x00080000 pref] May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] May 30 09:42:42 Tower kernel: pci 0000:01:00.0: BAR 14: failed to assign [mem size 0x00b00000] May 30 09:42:42 Tower kernel: pci 0000:02:02.0: BAR 14: failed to assign [mem size 0x00600000] May 30 09:42:42 Tower kernel: pci 0000:02:05.0: BAR 14: failed to assign [mem size 0x00100000] May 30 09:42:42 Tower kernel: pci 0000:02:08.0: BAR 14: failed to assign [mem size 0x00200000] May 30 09:42:42 Tower kernel: pci 0000:02:09.0: BAR 14: failed to assign [mem size 0x00100000] May 30 09:42:42 Tower kernel: pci 0000:02:0a.0: BAR 14: failed to assign [mem size 0x00100000] May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] May 30 09:42:42 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] May 30 09:42:42 Tower kernel: pci 0000:04:00.0: BAR 4: failed to assign [mem size 0x00004000 64bit] May 30 09:42:42 Tower kernel: pci 0000:04:00.0: BAR 2: failed to assign [mem size 0x00001000 64bit] May 30 09:42:42 Tower kernel: pci 0000:05:00.1: BAR 0: failed to assign [mem size 0x00100000 64bit] May 30 09:42:42 Tower kernel: pci 0000:05:00.3: BAR 0: failed to assign [mem size 0x00100000 64bit] May 30 09:42:42 Tower kernel: pci 0000:06:00.0: BAR 5: failed to assign [mem size 0x00000800] May 30 09:42:42 Tower kernel: pci 0000:07:00.0: BAR 5: failed to assign [mem size 0x00000800] May 30 09:42:42 Tower kernel: floppy0: no floppy controllers found May 30 09:42:42 Tower kernel: random: 7 urandom warning(s) missed due to ratelimiting May 30 09:42:42 Tower kernel: ccp 0000:0a:00.1: psp initialization failed May 30 09:42:44 Tower rpc.statd[1913]: Failed to read /var/lib/nfs/state: Success May 30 09:42:56 Tower kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20180810/utaddress-204) May 30 09:42:57 Tower root: Interface "tunl0" added. Warning: no bandwidth limit has been set. May 30 09:42:57 Tower root: Interface "ip_vti0" added. Warning: no bandwidth limit has been set. May 30 09:42:57 Tower root: Interface "gretap0" added. Warning: no bandwidth limit has been set. May 30 09:42:57 Tower root: Interface "br0" added. Warning: no bandwidth limit has been set. May 30 09:42:57 Tower root: Interface "gre0" added. Warning: no bandwidth limit has been set. May 30 09:42:57 Tower root: Interface "erspan0" added. Warning: no bandwidth limit has been set. May 30 09:42:57 Tower root: Warning: parse_ini_file(/var/local/emhttp/var.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 56 May 30 09:42:57 Tower root: Warning: Division by zero in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 62 May 30 09:53:10 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:10 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952914432 csum 0xb2de8b91 expected csum 0x2a169799 mirror 1 May 30 09:53:10 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 09:53:11 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:12 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:13 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:14 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:15 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:29 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:30 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:31 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:32 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:33 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:33 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:34 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:35 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:36 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:37 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 09:53:37 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952861184 csum 0x382186e4 expected csum 0x9fb755e0 mirror 1 May 30 09:53:38 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952861184 csum 0x382186e4 expected csum 0x9fb755e0 mirror 1 May 30 09:53:39 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952861184 csum 0x382186e4 expected csum 0x9fb755e0 mirror 1 May 30 09:53:40 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952861184 csum 0x382186e4 expected csum 0x9fb755e0 mirror 1 May 30 09:53:41 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952861184 csum 0x382186e4 expected csum 0x9fb755e0 mirror 1 May 30 09:53:41 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952861184 csum 0x382186e4 expected csum 0x9fb755e0 mirror 1 May 30 09:53:42 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952861184 csum 0x382186e4 expected csum 0x9fb755e0 mirror 1 May 30 09:53:43 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952861184 csum 0x382186e4 expected csum 0x9fb755e0 mirror 1 May 30 09:53:44 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952861184 csum 0x382186e4 expected csum 0x9fb755e0 mirror 1 May 30 09:53:45 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952861184 csum 0x382186e4 expected csum 0x9fb755e0 mirror 1 May 30 09:55:52 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 09:55:53 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 09:55:54 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 09:55:55 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 09:55:56 Tower kernel: BTRFS warning (device sdj1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 tower-diagnostics-20200530-1001.zip Quote Link to comment
comet424 Posted May 30, 2020 Author Share Posted May 30, 2020 i figure it was the cache drive? so i pulled it and stuck on a new cable and i rebooted the server.. and its hanging at "SYSLINUX 6.03 EDD" whatever that means no i cant get back up and running gonna pull everything Quote Link to comment
JorgeB Posted May 30, 2020 Share Posted May 30, 2020 btrfs checksum errors are a sign of data corruption, good idea to run memtest once you get the server back up. Quote Link to comment
comet424 Posted May 30, 2020 Author Share Posted May 30, 2020 (edited) oh ok so far cant get it up and running... i tried different slots to boot wont boot.. i copied the usb to my windows computer and currently downloading the OS again and see if it will boot before i copy back.. so checksum errors are memory? does the logs say anything else i know i should have downloaded logs before teh reboot ... but currently waiting for the unraid to download to usb and go from there would the checksum errors be why i had slowness too? Edited May 30, 2020 by comet424 Quote Link to comment
JorgeB Posted May 30, 2020 Share Posted May 30, 2020 4 minutes ago, comet424 said: so checksum errors are memory? Not necessarily, it means there's that corruption, and memory (when not ECC) is usually the most likely cause. Quote Link to comment
comet424 Posted May 30, 2020 Author Share Posted May 30, 2020 does unraid offer a memtest program or do i need to run memtest86 Quote Link to comment
comet424 Posted May 30, 2020 Author Share Posted May 30, 2020 so i got it back up and running reinstalled unraid to the USB and copied back couple folders i still get errors but ill run memtest86 off another usb... as i changed the sata cable and ran it off my raid card.. as i see it has udma crc error count now ugh.. and its a new ssd.. guess its better to get the m2 candy bar size as it cant go wrong as its screwed to the motherboard right? and here is the errors i got now after the reboot and ill go try running memtest.. and the slowness of unraid in the gui and such is that memory too or cache too May 30 12:46:26 Tower kernel: tsc: Fast TSC calibration failed May 30 12:46:26 Tower kernel: ACPI: Early table checksum verification disabled May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] May 30 12:46:26 Tower kernel: pci 0000:02:02.0: BAR 14: failed to assign [mem size 0x00600000] May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 6: failed to assign [mem size 0x00080000 pref] May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] May 30 12:46:26 Tower kernel: pci 0000:01:00.0: BAR 14: failed to assign [mem size 0x00b00000] May 30 12:46:26 Tower kernel: pci 0000:02:02.0: BAR 14: failed to assign [mem size 0x00600000] May 30 12:46:26 Tower kernel: pci 0000:02:05.0: BAR 14: failed to assign [mem size 0x00100000] May 30 12:46:26 Tower kernel: pci 0000:02:08.0: BAR 14: failed to assign [mem size 0x00200000] May 30 12:46:26 Tower kernel: pci 0000:02:09.0: BAR 14: failed to assign [mem size 0x00100000] May 30 12:46:26 Tower kernel: pci 0000:02:0a.0: BAR 14: failed to assign [mem size 0x00100000] May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] May 30 12:46:26 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] May 30 12:46:26 Tower kernel: pci 0000:04:00.0: BAR 4: failed to assign [mem size 0x00004000 64bit] May 30 12:46:26 Tower kernel: pci 0000:04:00.0: BAR 2: failed to assign [mem size 0x00001000 64bit] May 30 12:46:26 Tower kernel: pci 0000:05:00.1: BAR 0: failed to assign [mem size 0x00100000 64bit] May 30 12:46:26 Tower kernel: pci 0000:05:00.3: BAR 0: failed to assign [mem size 0x00100000 64bit] May 30 12:46:26 Tower kernel: pci 0000:06:00.0: BAR 5: failed to assign [mem size 0x00000800] May 30 12:46:26 Tower kernel: pci 0000:07:00.0: BAR 5: failed to assign [mem size 0x00000800] May 30 12:46:26 Tower kernel: floppy0: no floppy controllers found May 30 12:46:26 Tower kernel: random: 7 urandom warning(s) missed due to ratelimiting May 30 12:46:26 Tower kernel: ccp 0000:0a:00.1: psp initialization failed May 30 12:46:29 Tower rpc.statd[1949]: Failed to read /var/lib/nfs/state: Success May 30 12:46:42 Tower kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20180810/utaddress-204) May 30 12:46:42 Tower root: Interface "tunl0" added. Warning: no bandwidth limit has been set. May 30 12:46:42 Tower root: Interface "ip_vti0" added. Warning: no bandwidth limit has been set. May 30 12:46:42 Tower root: Interface "gretap0" added. Warning: no bandwidth limit has been set. May 30 12:46:42 Tower root: Interface "br0" added. Warning: no bandwidth limit has been set. May 30 12:46:42 Tower root: Interface "gre0" added. Warning: no bandwidth limit has been set. May 30 12:46:42 Tower root: Interface "erspan0" added. Warning: no bandwidth limit has been set. May 30 12:46:42 Tower root: Warning: parse_ini_file(/var/local/emhttp/var.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 56 May 30 12:46:42 Tower root: Warning: Division by zero in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 62 Quote Link to comment
comet424 Posted May 30, 2020 Author Share Posted May 30, 2020 got the memtest86+ running now does memory also corrupt the usb so it couldnt boot? Quote Link to comment
comet424 Posted May 30, 2020 Author Share Posted May 30, 2020 (edited) so ive only done 1 pass so far and no errors gonna do 2 pass;s Edited May 30, 2020 by comet424 Quote Link to comment
comet424 Posted May 30, 2020 Author Share Posted May 30, 2020 (edited) so done 2 pass's no memory isses so rebooting and loading unraid still dont know what vnstatd is as it does some percentages before it gets to the login so i removed the cache drive from the hotswap module and directly from the raid card to my cache and try that for a while see if that fixes it.. sucks i cant pin point things after boot it up its decided to do a parity check now too.. so must have detected an issue Edited May 30, 2020 by comet424 Quote Link to comment
comet424 Posted May 30, 2020 Author Share Posted May 30, 2020 so memory passed the 2 times.. and I getting same errors... and I running like I mentioned the SSD off a raid cable now not on the hot swap I gett these errors and I finding regular hard drive access freezing up etc ay 30 16:24:51 Tower kernel: tsc: Fast TSC calibration failed May 30 16:24:51 Tower kernel: ACPI: Early table checksum verification disabled May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] May 30 16:24:51 Tower kernel: pci 0000:02:02.0: BAR 14: failed to assign [mem size 0x00600000] May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 6: failed to assign [mem size 0x00080000 pref] May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] May 30 16:24:51 Tower kernel: pci 0000:01:00.0: BAR 14: failed to assign [mem size 0x00b00000] May 30 16:24:51 Tower kernel: pci 0000:02:02.0: BAR 14: failed to assign [mem size 0x00600000] May 30 16:24:51 Tower kernel: pci 0000:02:05.0: BAR 14: failed to assign [mem size 0x00100000] May 30 16:24:51 Tower kernel: pci 0000:02:08.0: BAR 14: failed to assign [mem size 0x00200000] May 30 16:24:51 Tower kernel: pci 0000:02:09.0: BAR 14: failed to assign [mem size 0x00100000] May 30 16:24:51 Tower kernel: pci 0000:02:0a.0: BAR 14: failed to assign [mem size 0x00100000] May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] May 30 16:24:51 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] May 30 16:24:51 Tower kernel: pci 0000:04:00.0: BAR 4: failed to assign [mem size 0x00004000 64bit] May 30 16:24:51 Tower kernel: pci 0000:04:00.0: BAR 2: failed to assign [mem size 0x00001000 64bit] May 30 16:24:51 Tower kernel: pci 0000:05:00.1: BAR 0: failed to assign [mem size 0x00100000 64bit] May 30 16:24:51 Tower kernel: pci 0000:05:00.3: BAR 0: failed to assign [mem size 0x00100000 64bit] May 30 16:24:51 Tower kernel: pci 0000:06:00.0: BAR 5: failed to assign [mem size 0x00000800] May 30 16:24:51 Tower kernel: pci 0000:07:00.0: BAR 5: failed to assign [mem size 0x00000800] May 30 16:24:51 Tower kernel: floppy0: no floppy controllers found May 30 16:24:51 Tower kernel: random: 7 urandom warning(s) missed due to ratelimiting May 30 16:24:51 Tower kernel: ccp 0000:0a:00.1: psp initialization failed May 30 16:24:54 Tower rpc.statd[1966]: Failed to read /var/lib/nfs/state: Success May 30 16:25:07 Tower kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20180810/utaddress-204) May 30 16:25:07 Tower root: Interface "tunl0" added. Warning: no bandwidth limit has been set. May 30 16:25:07 Tower root: Interface "ip_vti0" added. Warning: no bandwidth limit has been set. May 30 16:25:07 Tower root: Interface "gretap0" added. Warning: no bandwidth limit has been set. May 30 16:25:07 Tower root: Interface "br0" added. Warning: no bandwidth limit has been set. May 30 16:25:07 Tower root: Interface "gre0" added. Warning: no bandwidth limit has been set. May 30 16:25:07 Tower root: Interface "erspan0" added. Warning: no bandwidth limit has been set. May 30 16:25:07 Tower root: Warning: parse_ini_file(/var/local/emhttp/var.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 56 May 30 16:25:07 Tower root: Warning: Division by zero in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 62 May 30 16:33:09 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952914432 csum 0xb2de8b91 expected csum 0x2a169799 mirror 1 May 30 16:33:09 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 16:33:09 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 16:33:12 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 16:33:13 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 16:33:15 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 16:33:16 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 16:33:17 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 16:33:17 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 16:33:18 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 16:33:19 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 16:33:20 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 16:33:21 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:39:22 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:39:23 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:39:24 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:39:25 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:39:26 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:39:26 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 19:39:27 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 19:39:28 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 19:39:29 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 19:39:30 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952857088 csum 0x9b48269f expected csum 0x3d7debcd mirror 1 May 30 19:41:26 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:41:27 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:41:28 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:41:29 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:41:30 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952824320 csum 0x62424f55 expected csum 0x3e8ef995 mirror 1 May 30 19:42:04 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952918528 csum 0x25c1fe13 expected csum 0x6bf188c8 mirror 1 May 30 19:42:05 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952918528 csum 0x25c1fe13 expected csum 0x6bf188c8 mirror 1 May 30 19:42:06 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952918528 csum 0x25c1fe13 expected csum 0x6bf188c8 mirror 1 May 30 19:42:07 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952918528 csum 0x25c1fe13 expected csum 0x6bf188c8 mirror 1 May 30 19:42:08 Tower kernel: BTRFS warning (device sde1): csum failed root 5 ino 3703059 off 3952918528 csum 0x25c1fe13 expected csum 0x6bf188c8 mirror 1 tower-diagnostics-20200530-1954.zip Quote Link to comment
JorgeB Posted May 31, 2020 Share Posted May 31, 2020 Since it's a single device pool it can't fix data corruption but you can find out which files are corrupt by running a scrub, they will be identified in the syslog, then delete or replace them. Quote Link to comment
comet424 Posted May 31, 2020 Author Share Posted May 31, 2020 do you mean single device pool as I only have 1 SSD? is it better to have 2 SSDs I do have the ca backup run each day... so do I just click the SCRUB button then I never touched it.. I honestly always figured it scrub the drive meaning erase it so I have never honestly touched it.. I know I have had issues before as you may seen my posts.. and its still running parity check so ill try it after... sooo unraid cant tell if the hotswap is the issue or if its a failure in the drive? also got new errors have no idea May 30 21:42:41 Tower nginx: 2020/05/30 21:42:41 [error] 17252#17252: *101393 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.47, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower", referrer: "http://tower/Settings/FixProblems" May 31 05:06:55 Tower nginx: 2020/05/31 05:06:55 [error] 17252#17252: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. May 31 05:06:55 Tower nginx: 2020/05/31 05:06:55 [error] 17252#17252: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. May 31 05:06:55 Tower nginx: 2020/05/31 05:06:55 [error] 17252#17252: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. Quote Link to comment
comet424 Posted June 1, 2020 Author Share Posted June 1, 2020 so I ran the scrub button on the cache drive no issues so then whats else is causing those errors. since scrub passed.. and the memtest86 passed when I did 2 passes UUID: 9d35d0ca-2ac6-4a96-9e3d-0b95e6170116 Scrub started: Sun May 31 20:47:04 2020 Status: finished Duration: 0:22:48 Total to scrub: 684.30GiB Rate: 512.23MiB/s Error summary: csum=2331 Corrected: 0 Uncorrectable: 0 Unverified: 0 Quote Link to comment
JorgeB Posted June 1, 2020 Share Posted June 1, 2020 8 hours ago, comet424 said: no issues 8 hours ago, comet424 said: Error summary: csum=2331 There are issues. Quote Link to comment
comet424 Posted June 1, 2020 Author Share Posted June 1, 2020 oh I was looking ed correct uncorrected unverified. it showed 0 csum means nothing to me.. if it had Said "There are 120 errors" then id have noticed... guess im used to windows and still semi new to unraid…. as before unraid a year and half ago I was 20 yrs since I used Linux redhat.. so I didn't know so what does the 2331 mean then? is that 2331 files is that just a error code what does it mean and where in the system logs do you fine these errors your mentioned Quote Link to comment
comet424 Posted June 1, 2020 Author Share Posted June 1, 2020 (edited) oh and I ran scrub then on my array drives figured cant hurt then... and I checked the syslog this is what it shows as my other drives I think are still scrubbing... and still don't know wha the past is a message from the past.. I need a message from the future lol... and are these errors showing why even though my Array drives are spun up I cant access some of my folders in windows.. the hour glass keeps spinning and takes a while to get in.. as they aren't spun down.. so like unraid is stalled like May 30 21:42:41 Tower nginx: 2020/05/30 21:42:41 [error] 17252#17252: *101393 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.47, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower", referrer: "http://tower/Settings/FixProblems" May 31 05:06:55 Tower nginx: 2020/05/31 05:06:55 [error] 17252#17252: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. May 31 05:06:55 Tower nginx: 2020/05/31 05:06:55 [error] 17252#17252: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. May 31 05:06:55 Tower nginx: 2020/05/31 05:06:55 [error] 17252#17252: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. May 31 14:36:01 Tower nginx: 2020/05/31 14:36:01 [error] 17252#17252: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. May 31 14:36:01 Tower nginx: 2020/05/31 14:36:01 [error] 17252#17252: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. May 31 14:36:01 Tower nginx: 2020/05/31 14:36:01 [error] 17252#17252: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. May 31 21:08:36 Tower kernel: BTRFS warning (device sde1): checksum error at logical 876900556800 on dev /dev/sde1, physical 874753073152, root 5, inode 3703059, offset 3952824320, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:08:36 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 May 31 21:08:51 Tower kernel: BTRFS warning (device sde1): checksum error at logical 884792160256 on dev /dev/sde1, physical 882644676608, root 5, inode 3703059, offset 3952857088, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:08:51 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 May 31 21:08:51 Tower kernel: BTRFS warning (device sde1): checksum error at logical 884792164352 on dev /dev/sde1, physical 882644680704, root 5, inode 3703059, offset 3952861184, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:08:51 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 May 31 21:09:02 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261186048 on dev /dev/sde1, physical 889113702400, root 5, inode 3703059, offset 3952914432, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:09:02 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 May 31 21:09:02 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261190144 on dev /dev/sde1, physical 889113706496, root 5, inode 3703059, offset 3952918528, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:09:02 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0 May 31 21:09:02 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261194240 on dev /dev/sde1, physical 889113710592, root 5, inode 3703059, offset 3952922624, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:09:02 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 6, gen 0 May 31 21:09:02 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261198336 on dev /dev/sde1, physical 889113714688, root 5, inode 3703059, offset 3952926720, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:09:02 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 May 31 21:09:02 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261202432 on dev /dev/sde1, physical 889113718784, root 5, inode 3703059, offset 3952930816, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:09:02 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 May 31 21:09:02 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261206528 on dev /dev/sde1, physical 889113722880, root 5, inode 3703059, offset 3952934912, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:09:02 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9, gen 0 May 31 21:09:02 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261210624 on dev /dev/sde1, physical 889113726976, root 5, inode 3703059, offset 3952939008, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:09:02 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 May 31 21:09:02 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261214720 on dev /dev/sde1, physical 889113731072, root 5, inode 3703059, offset 3952943104, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:09:02 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 11, gen 0 May 31 21:09:02 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261218816 on dev /dev/sde1, physical 889113735168, root 5, inode 3703059, offset 3952947200, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:09:02 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 12, gen 0 May 31 21:09:02 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261222912 on dev /dev/sde1, physical 889113739264, root 5, inode 3703059, offset 3952951296, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) May 31 21:09:02 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 13, gen 0 May 31 21:09:14 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1512, gen 0 May 31 21:09:14 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1513, gen 0 May 31 21:09:14 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1514, gen 0 May 31 21:09:14 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1515, gen 0 May 31 21:09:14 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1516, gen 0 May 31 21:09:14 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1517, gen 0 May 31 21:09:14 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1518, gen 0 May 31 21:09:14 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1519, gen 0 May 31 21:09:14 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1520, gen 0 May 31 21:09:14 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1521, gen 0 May 31 23:26:38 Tower kernel: BTRFS warning (device md3): checksum error at logical 385097449472 on dev /dev/md3, physical 385097449472, root 5, inode 57401, offset 138985472, length 4096, links 1 (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) May 31 23:26:38 Tower kernel: BTRFS warning (device md3): checksum error at logical 385097662464 on dev /dev/md3, physical 385097662464, root 5, inode 57401, offset 139198464, length 4096, links 1 (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) May 31 23:26:38 Tower kernel: BTRFS warning (device md3): checksum error at logical 385097531392 on dev /dev/md3, physical 385097531392, root 5, inode 57401, offset 139067392, length 4096, links 1 (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) May 31 23:26:38 Tower kernel: BTRFS error (device md3): bdev /dev/md3 errs: wr 0, rd 0, flush 0, corrupt 1033, gen 0 May 31 23:26:38 Tower kernel: BTRFS error (device md3): bdev /dev/md3 errs: wr 0, rd 0, flush 0, corrupt 1034, gen 0 May 31 23:26:38 Tower kernel: BTRFS error (device md3): bdev /dev/md3 errs: wr 0, rd 0, flush 0, corrupt 1035, gen 0 May 31 23:26:38 Tower kernel: BTRFS warning (device md3): checksum error at logical 385097924608 on dev /dev/md3, physical 385097924608, root 5, inode 57401, offset 139460608, length 4096, links 1 (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) May 31 23:26:38 Tower kernel: BTRFS warning (device md3): checksum error at logical 385097793536 on dev /dev/md3, physical 385097793536, root 5, inode 57401, offset 139329536, length 4096, links 1 (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) May 31 23:26:38 Tower kernel: BTRFS error (device md3): bdev /dev/md3 errs: wr 0, rd 0, flush 0, corrupt 1036, gen 0 May 31 23:26:38 Tower kernel: BTRFS error (device md3): bdev /dev/md3 errs: wr 0, rd 0, flush 0, corrupt 1037, gen 0 May 31 23:26:38 Tower kernel: BTRFS warning (device md3): checksum error at logical 385098055680 on dev /dev/md3, physical 385098055680, root 5, inode 57401, offset 139591680, length 4096, links 1 (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) May 31 23:26:38 Tower kernel: BTRFS error (device md3): bdev /dev/md3 errs: wr 0, rd 0, flush 0, corrupt 1038, gen 0 May 31 23:26:38 Tower kernel: BTRFS warning (device md3): checksum error at logical 385098317824 on dev /dev/md3, physical 385098317824, root 5, inode 57401, offset 139853824, length 4096, links 1 (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) May 31 23:26:38 Tower kernel: BTRFS warning (device md3): checksum error at logical 385098186752 on dev /dev/md3, physical 385098186752, root 5, inode 57401, offset 139722752, length 4096, links 1 (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) May 31 23:26:38 Tower kernel: BTRFS error (device md3): bdev /dev/md3 errs: wr 0, rd 0, flush 0, corrupt 1039, gen 0 May 31 23:26:38 Tower kernel: BTRFS error (device md3): bdev /dev/md3 errs: wr 0, rd 0, flush 0, corrupt 1040, gen 0 May 31 23:26:38 Tower kernel: BTRFS warning (device md3): checksum error at logical 385097453568 on dev /dev/md3, physical 385097453568, root 5, inode 57401, offset 138989568, length 4096, links 1 (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) May 31 23:26:38 Tower kernel: BTRFS error (device md3): bdev /dev/md3 errs: wr 0, rd 0, flush 0, corrupt 1041, gen 0 May 31 23:26:38 Tower kernel: BTRFS warning (device md3): checksum error at logical 385097535488 on dev /dev/md3, physical 385097535488, root 5, inode 57401, offset 139071488, length 4096, links 1 (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) May 31 23:26:38 Tower kernel: BTRFS error (device md3): bdev /dev/md3 errs: wr 0, rd 0, flush 0, corrupt 1042, gen 0 Edited June 1, 2020 by comet424 Quote Link to comment
JorgeB Posted June 1, 2020 Share Posted June 1, 2020 You also have corrupt data on the array, and that's not surprising since if data is getting corrupt on cache most likely it's getting corrupt on the array as well, you need to delete/restore those files, and find out what is causing the corruption, it's some hardware problem. Syslog after a scrub will show the corrupt files, e.g.: (path: Videos/TV Shows/Comedy/Cheers (1982)/Season 7/Cheers (1982) - S07E10 - Bar Wars II- The Woodman Strikes Back.avi) Quote Link to comment
comet424 Posted June 1, 2020 Author Share Posted June 1, 2020 is there a test to test if unraid is acting slow that its below the performance it should be at Quote Link to comment
comet424 Posted June 1, 2020 Author Share Posted June 1, 2020 (edited) ah ok... so orginally before I moved the SSD it was LSI Raid Card to my Array hds.. and Cache SSD was to the MotherBoard SATA but all are using Hot Swap internal moduals you cant buy anymore 😞 right now the Array HDS are still on the LSI card to the hot swaps and the SSD is a new cable directly from the SSD to the motherboard does it show the errors where they are on the SSD I didn't see it and ill redo my my video you pointed out and would the corrupted data be causing why I cant seem to get into my folders windows taking forever to try to get into the unraid shares and my motherboard can handle ECC ram should I have to get some of that or that wont help the issue I having Edited June 1, 2020 by comet424 Quote Link to comment
comet424 Posted June 1, 2020 Author Share Posted June 1, 2020 (edited) so I deleted the file off my array.. will that fix the error there? do I need to re run the scrub on that drive as I guess it was on my 2TB drive and my other drives are still scrubbing for another 4 hours it says Edited June 1, 2020 by comet424 Quote Link to comment
comet424 Posted June 1, 2020 Author Share Posted June 1, 2020 also copying the cache drive to the array in krusader... and then do I do scrub and repair errors on the ssd? Quote Link to comment
comet424 Posted June 1, 2020 Author Share Posted June 1, 2020 and do you know how to setup the notifications right I tried in past and gave up where it wsa to text or email you.. but email never worked.. as I wanted to be notified for serious errors like this then id know as I can get told cache drive broken or the hard drive array had corrupt data and is it good to scrub on a regular basis? Quote Link to comment
comet424 Posted June 2, 2020 Author Share Posted June 2, 2020 so I deleted the vm it gave issues for the SSD cache drive and then I ran the scrub repair but its not fixing.. and I haven't tested the array really I gonna scrub it before I goto bed but can you tell whats wrong? Jun 1 22:29:53 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 7006, gen 0 Jun 1 22:29:53 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 891261222912 on dev /dev/sde1 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8505, gen 0 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 897470119936 on dev /dev/sde1 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8506, gen 0 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 897472241664 on dev /dev/sde1 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8507, gen 0 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 897472266240 on dev /dev/sde1 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8508, gen 0 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 897470124032 on dev /dev/sde1 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8509, gen 0 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 897472245760 on dev /dev/sde1 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8510, gen 0 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 897472270336 on dev /dev/sde1 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8511, gen 0 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 897470128128 on dev /dev/sde1 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8512, gen 0 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 897472249856 on dev /dev/sde1 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8513, gen 0 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 897472274432 on dev /dev/sde1 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 8514, gen 0 Jun 1 22:30:04 Tower kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 897470132224 on dev /dev/sde1 tower-diagnostics-20200601-2256.zip Quote Link to comment
JorgeB Posted June 2, 2020 Share Posted June 2, 2020 3 hours ago, comet424 said: I ran the scrub repair but its not fixing On 5/31/2020 at 8:26 AM, johnnie.black said: Since it's a single device pool it can't fix data corruption Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.