Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Keep getting 1 parity sync error, same sector?

kin0kin
in unRAID Server 4.5 [No new topics]

Featured Replies

Oct 9 00:14:11 Tower ntpd[1416]: ntpd [email protected] Wed Jan 14 23:46:25 UTC 2009 (1)
Oct 9 00:14:11 Tower ifplugd(eth0)[1376]: client: Starting NTP daemon: /usr/sbin/ntpd -g
Oct 9 00:14:11 Tower ntpd[1417]: precision = 2.000 usec
Oct 9 00:14:11 Tower ntpd[1417]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 9 00:14:11 Tower ntpd[1417]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Oct 9 00:14:11 Tower ntpd[1417]: Listening on interface #1 lo, 127.0.0.1#123 Enabled
Oct 9 00:14:11 Tower ntpd[1417]: Listening on interface #2 eth0, 192.168.1.102#123 Enabled
Oct 9 00:14:11 Tower ntpd[1417]: kernel time sync status 0040
Oct 9 00:14:11 Tower ntpd[1417]: frequency initialized -32.968 PPM from /etc/ntp/drift
Oct 9 00:14:11 Tower ifplugd(eth0)[1376]: Program executed successfully.
Oct 9 00:14:11 Tower rpc.statd[1431]: Version 1.1.4 Starting
Oct 9 00:14:11 Tower emhttp: unRAID System Management Utility version 4.5.6
Oct 9 00:14:11 Tower emhttp: Copyright (C) 2005-2010, Lime Technology, LLC
Oct 9 00:14:11 Tower emhttp: Pro key detected, GUID: 0930-6545-0000-5B831600014F
Oct 9 00:14:11 Tower emhttp: shcmd (1): udevadm settle
Oct 9 00:14:11 Tower emhttp: Device inventory:
Oct 9 00:14:11 Tower emhttp: pci-0000:00:0e.0-scsi-0:0:0:0 host1 (sda) WDC_WD6400AAKS-75A7B0_WD-WCASY1489916
Oct 9 00:14:11 Tower emhttp: pci-0000:00:0e.0-scsi-1:0:0:0 host2 (sdb) WDC_WD6400AAKS-75A7B0_WD-WCASY1185307
Oct 9 00:14:11 Tower emhttp: pci-0000:00:0f.0-scsi-0:0:0:0 host3 (sdc) WDC_WD20EADS-00R6B0_WD-WCAVY4778249
Oct 9 00:14:11 Tower emhttp: pci-0000:00:0f.0-scsi-1:0:0:0 host4 (sdd) WDC_WD10EAVS-00D7B1_WD-WCAU49248571
Oct 9 00:14:11 Tower emhttp: pci-0000:04:08.0-scsi-3:0:0:0 host8 (sde) WDC_WD3200BEVT-60A23T0_WD-WX21A2043710
Oct 9 00:14:11 Tower emhttp: pci-0000:04:09.0-scsi-0:0:0:0 host13 (sdg) WDC_WD10EAVS-14D7B1_WD-WCAU49737055
Oct 9 00:14:11 Tower emhttp: pci-0000:04:09.0-scsi-1:0:0:0 host14 (sdh) WDC_WD10EALS-00Z8A0_WD-WCATR0532565
Oct 9 00:14:11 Tower emhttp: shcmd (2): modprobe -rw md-mod 2>&1 | logger
Oct 9 00:14:11 Tower emhttp: shcmd (3): modprobe md-mod super=/boot/config/super.dat slots=8,32,8,48,8,0,8,16,8,96,8,112,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger
Oct 9 00:14:11 Tower kernel: xor: automatically using best checksumming function: pIII_sse
Oct 9 00:14:11 Tower kernel: pIII_sse : 6164.800 MB/sec
Oct 9 00:14:11 Tower kernel: xor: using function: pIII_sse (6164.800 MB/sec)
Oct 9 00:14:11 Tower emhttp: Spinning up all drives...
Oct 9 00:14:11 Tower kernel: md: unRAID driver 0.95.4 installed
Oct 9 00:14:11 Tower kernel: md: import disk0: [8,32] (sdc) WDC WD20EADS-00R WD-WCAVY4778249 offset: 63 size: 1953514552
Oct 9 00:14:11 Tower kernel: md: import disk1: [8,48] (sdd) WDC WD10EAVS-00D WD-WCAU49248571 offset: 63 size: 976762552
Oct 9 00:14:11 Tower kernel: md: import disk2: [8,0] (sda) WDC WD6400AAKS-7 WD-WCASY1489916 offset: 63 size: 625131832
Oct 9 00:14:11 Tower kernel: md: import disk3: [8,16] (sdb) WDC WD6400AAKS-7 WD-WCASY1185307 offset: 63 size: 625131832
Oct 9 00:14:11 Tower kernel: md: import disk4: [8,96] (sdg) WDC WD10EAVS-14D WD-WCAU49737055 offset: 63 size: 976762552
Oct 9 00:14:11 Tower kernel: md: import disk5: [8,112] (sdh) WDC WD10EALS-00Z WD-WCATR0532565 offset: 63 size: 976762552
Oct 9 00:14:11 Tower kernel: mdcmd (2): set md_num_stripes 1280
Oct 9 00:14:11 Tower kernel: mdcmd (3): set md_write_limit 768
Oct 9 00:14:11 Tower kernel: mdcmd (4): set md_sync_window 288
Oct 9 00:14:11 Tower kernel: mdcmd (5): set spinup_group 0 0
Oct 9 00:14:11 Tower kernel: mdcmd (6): set spinup_group 1 0
Oct 9 00:14:11 Tower kernel: mdcmd (7): set spinup_group 2 0
Oct 9 00:14:11 Tower kernel: mdcmd (: set spinup_group 3 0
Oct 9 00:14:11 Tower kernel: mdcmd (9): set spinup_group 4 0
Oct 9 00:14:11 Tower kernel: mdcmd (10): set spinup_group 5 0
Oct 9 00:14:11 Tower kernel: mdcmd (11): spinup 0
Oct 9 00:14:11 Tower kernel: mdcmd (12): spinup 1
Oct 9 00:14:11 Tower kernel: mdcmd (13): spinup 2
Oct 9 00:14:11 Tower kernel: mdcmd (14): spinup 3
Oct 9 00:14:11 Tower kernel: mdcmd (15): spinup 4
Oct 9 00:14:11 Tower emhttp: shcmd (4): /usr/sbin/hdparm -S0 /dev/sde >/dev/null
Oct 9 00:14:11 Tower kernel: mdcmd (16): spinup 5
Oct 9 00:14:12 Tower emhttp: shcmd (5): /usr/local/sbin/set_ncq sdc 1 >/dev/null
Oct 9 00:14:12 Tower emhttp: shcmd (6): /usr/local/sbin/set_ncq sdd 1 >/dev/null
Oct 9 00:14:12 Tower emhttp: shcmd (7): /usr/local/sbin/set_ncq sda 1 >/dev/null
Oct 9 00:14:12 Tower emhttp: shcmd (: /usr/local/sbin/set_ncq sdb 1 >/dev/null
Oct 9 00:14:12 Tower emhttp: shcmd (9): /usr/local/sbin/set_ncq sdg 1 >/dev/null
Oct 9 00:14:12 Tower emhttp: shcmd (10): /usr/local/sbin/set_ncq sdh 1 >/dev/null
Oct 9 00:14:12 Tower emhttp: shcmd (11): /usr/local/sbin/set_ncq sde 1 >/dev/null
Oct 9 00:14:12 Tower kernel: mdcmd (18): start STOPPED
Oct 9 00:14:12 Tower kernel: unraid: allocating 33720K for 1280 stripes (6 disks)
Oct 9 00:14:12 Tower kernel: md1: running, size: 976762552 blocks
Oct 9 00:14:12 Tower kernel: md2: running, size: 625131832 blocks
Oct 9 00:14:12 Tower kernel: md3: running, size: 625131832 blocks
Oct 9 00:14:12 Tower kernel: md4: running, size: 976762552 blocks
Oct 9 00:14:12 Tower kernel: md5: running, size: 976762552 blocks
Oct 9 00:14:12 Tower emhttp: shcmd (12): udevadm settle
Oct 9 00:14:12 Tower emhttp: shcmd (13): mkdir /mnt/disk3
Oct 9 00:14:12 Tower emhttp: shcmd (13): mkdir /mnt/disk4
Oct 9 00:14:12 Tower emhttp: shcmd (13): mkdir /mnt/disk5
Oct 9 00:14:12 Tower emhttp: shcmd (13): mkdir /mnt/cache
Oct 9 00:14:12 Tower emhttp: shcmd (13): mkdir /mnt/disk2
Oct 9 00:14:12 Tower emhttp: shcmd (13): mkdir /mnt/disk1
Oct 9 00:14:12 Tower emhttp: shcmd (14): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 | logger
Oct 9 00:14:12 Tower emhttp: shcmd (15): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 2>&1 | logger
Oct 9 00:14:12 Tower kernel: mdcmd (20): check 
Oct 9 00:14:12 Tower kernel: md: recovery thread woken up ...
Oct 9 00:14:12 Tower emhttp: shcmd (16): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/sde1 /mnt/cache 2>&1 | logger
Oct 9 00:14:12 Tower emhttp: shcmd (17): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 | logger
Oct 9 00:14:12 Tower emhttp: shcmd (18): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger
Oct 9 00:14:12 Tower emhttp: shcmd (19): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md4 /mnt/disk4 2>&1 | logger
Oct 9 00:14:12 Tower kernel: md: recovery thread has nothing to resync
Oct 9 00:14:12 Tower kernel: REISERFS (device sde1): found reiserfs format "3.6" with standard journal
Oct 9 00:14:12 Tower kernel: REISERFS (device sde1): using ordered data mode
Oct 9 00:14:12 Tower kernel: REISERFS (device sde1): journal params: device sde1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Oct 9 00:14:12 Tower kernel: REISERFS (device sde1): checking transaction log (sde1)
Oct 9 00:14:12 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal
Oct 9 00:14:12 Tower kernel: REISERFS (device md5): using ordered data mode
Oct 9 00:14:12 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Oct 9 00:14:12 Tower kernel: REISERFS (device md5): checking transaction log (md5)
Oct 9 00:14:12 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal
Oct 9 00:14:12 Tower kernel: REISERFS (device md3): using ordered data mode
Oct 9 00:14:12 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal
Oct 9 00:14:12 Tower kernel: REISERFS (device md2): using ordered data mode
Oct 9 00:14:12 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal
Oct 9 00:14:12 Tower kernel: REISERFS (device md1): using ordered data mode
Oct 9 00:14:12 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal
Oct 9 00:14:12 Tower kernel: REISERFS (device md4): using ordered data mode
Oct 9 00:14:12 Tower kernel: REISERFS (device sde1): Using r5 hash to sort names
Oct 9 00:14:12 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Oct 9 00:14:12 Tower kernel: REISERFS (device md3): checking transaction log (md3)
Oct 9 00:14:12 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Oct 9 00:14:12 Tower kernel: REISERFS (device md2): checking transaction log (md2)
Oct 9 00:14:12 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Oct 9 00:14:12 Tower kernel: REISERFS (device md1): checking transaction log (md1)
Oct 9 00:14:12 Tower kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Oct 9 00:14:12 Tower kernel: REISERFS (device md4): checking transaction log (md4)
Oct 9 00:14:12 Tower kernel: REISERFS (device md5): Using r5 hash to sort names
Oct 9 00:14:12 Tower kernel: REISERFS (device md2): Using r5 hash to sort names
Oct 9 00:14:12 Tower kernel: REISERFS (device md3): Using r5 hash to sort names
Oct 9 00:14:12 Tower kernel: REISERFS (device md1): Using r5 hash to sort names
Oct 9 00:14:12 Tower kernel: REISERFS (device md4): Using r5 hash to sort names
Oct 9 00:14:13 Tower emhttp: shcmd (25): rm /etc/samba/smb-shares.conf >/dev/null 2>&1
Oct 9 00:14:13 Tower emhttp: _shcmd: shcmd (25): exit status: 1
Oct 9 00:14:13 Tower emhttp: shcmd (26): cp /etc/exports- /etc/exports
Oct 9 00:14:13 Tower emhttp: shcmd (27): mkdir /mnt/user
Oct 9 00:14:13 Tower emhttp: shcmd (28): /usr/local/sbin/shfs /mnt/user -cache 1 -floor 2000000 -o noatime,big_writes,allow_other,default_permissions
Oct 9 00:14:13 Tower emhttp: shcmd (29): mkdir /mnt/user0
Oct 9 00:14:13 Tower emhttp: shcmd (30): /usr/local/sbin/shfs /mnt/user0 -cache 0 -o noatime,big_writes,allow_other,default_permissions
Oct 9 00:14:13 Tower emhttp: shcmd (31): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root
Oct 9 00:14:13 Tower emhttp: shcmd (32): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root
Oct 9 00:14:13 Tower emhttp: shcmd (33): echo '45 2 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root
Oct 9 00:14:13 Tower emhttp: shcmd (34): crontab /var/spool/cron/crontabs/root
Oct 9 00:14:14 Tower emhttp: shcmd (35): killall -HUP smbd
Oct 9 00:14:14 Tower emhttp: shcmd (36): /etc/rc.d/rc.nfsd restart | logger
Oct 9 00:14:20 Tower ntpd[1417]: synchronized to 209.167.68.100, stratum 2
Oct 9 00:14:21 Tower kernel: mdcmd (23): clear 
Oct 9 00:14:21 Tower unmenu-status: Starting unmenu web-server
Oct 9 00:14:29 Tower kernel: mdcmd (26): check CORRECT
Oct 9 00:14:29 Tower kernel: md: recovery thread woken up ...
Oct 9 00:14:29 Tower kernel: md: recovery thread checking parity...
Oct 9 00:14:29 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks.
Oct 9 00:14:32 Tower apcupsd[1849]: apcupsd FATAL ERROR in linux-usb.c at line 609 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see . 
Oct 9 00:14:32 Tower apcupsd[1849]: apcupsd error shutdown completed
Oct 9 00:14:37 Tower kernel: mdcmd (29): nocheck 
Oct 9 00:14:37 Tower kernel: md: md_do_sync: got signal, exit...
Oct 9 00:14:37 Tower kernel: md: recovery thread sync completion status: -4
Oct 9 00:17:24 Tower kernel: mdcmd (56): check 
Oct 9 00:17:24 Tower kernel: md: recovery thread woken up ...
Oct 9 00:17:24 Tower kernel: md: recovery thread checking parity...
Oct 9 00:17:24 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks.
[color=red]Oct 9 01:09:47 Tower kernel: md: parity incorrect: 380084480[/color]
Oct 9 01:19:57 Tower kernel: mdcmd (503): nocheck 
Oct 9 01:19:57 Tower kernel: md: md_do_sync: got signal, exit...
Oct 9 01:19:57 Tower kernel: md: recovery thread sync completion status: -4
Oct 9 01:20:02 Tower kernel: mdcmd (506): check CORRECT
Oct 9 01:20:02 Tower kernel: md: recovery thread woken up ...
Oct 9 01:20:02 Tower kernel: md: recovery thread checking parity...
Oct 9 01:20:02 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks.
[color=red][font=Verdana]Oct 9 02:12:00 Tower kernel: md: parity incorrect: 380084480[/font][/color]

 

What seems to be the problem?

  • Author

One other weird issue. I've included disk 5 for games. Split level 1. There are over 300gb spaces available, but when mover tries to move stuff over, it says not enough space?

Oct 9 02:45:01 Tower logger: mover started
Oct 9 02:45:04 Tower logger: ./games/Nintendo DSI/Metroid - Prime Hunters.nds
Oct 9 02:45:04 Tower shfs0: shfs_mkdir: assign_disk: games/Nintendo DSI (28) No space left on device
Oct 9 02:45:04 Tower logger: cd+++++++++ games/Nintendo DSI/
Oct 9 02:45:04 Tower logger: rsync: recv_generator: mkdir "/mnt/user0/games/Nintendo DSI" failed: No space left on device (28)
Oct 9 02:45:04 Tower logger: *** Skipping any contents from this failed directory ***
Oct 9 02:45:04 Tower logger: rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2]
Oct 9 02:45:04 Tower logger: ./games/Nintendo DSI/Final Fantasy IV.nds
Oct 9 02:45:04 Tower shfs0: shfs_mkdir: assign_disk: games/Nintendo DSI (28) No space left on device
Oct 9 02:45:04 Tower logger: cd+++++++++ games/Nintendo DSI/
Oct 9 02:45:04 Tower logger: rsync: recv_generator: mkdir "/mnt/user0/games/Nintendo DSI" failed: No space left on device (28)
Oct 9 02:45:04 Tower logger: *** Skipping any contents from this failed directory ***
Oct 9 02:45:04 Tower logger: rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2]
Oct 9 02:45:04 Tower logger: ./games/Nintendo DSI/Final Fantasy XII Revenant Wings.nds
Oct 9 02:45:04 Tower shfs0: shfs_mkdir: assign_disk: games/Nintendo DSI (28) No space left on device
Oct 9 02:45:04 Tower logger: cd+++++++++ games/Nintendo DSI/
Oct 9 02:45:04 Tower logger: rsync: recv_generator: mkdir "/mnt/user0/games/Nintendo DSI" failed: No space left on device (28)
Oct 9 02:45:04 Tower logger: *** Skipping any contents from this failed directory ***
Oct 9 02:45:04 Tower logger: rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2]
Oct 9 02:45:04 Tower logger: ./games/Nintendo DSI/Zoo Tycoon 2.nds
Oct 9 02:45:04 Tower shfs0: shfs_mkdir: assign_disk: games/Nintendo DSI (28) No space left on device
Oct 9 02:45:04 Tower logger: cd+++++++++ games/Nintendo DSI/
Oct 9 02:45:04 Tower logger: rsync: recv_generator: mkdir "/mnt/user0/games/Nintendo DSI" failed: No space left on device (28)
Oct 9 02:45:04 Tower logger: *** Skipping any contents from this failed directory ***
Oct 9 02:45:04 Tower logger: rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2]
Oct 9 02:45:04 Tower logger: ./games/Nintendo DSI/Tetris DS.nds
Oct 9 02:45:04 Tower shfs0: shfs_mkdir: assign_disk: games/Nintendo DSI (28) No space left on device
Oct 9 02:45:04 Tower logger: cd+++++++++ games/Nintendo DSI/
Oct 9 02:45:04 Tower logger: rsync: recv_generator: mkdir "/mnt/user0/games/Nintendo DSI" failed: No space left on device (28)
Oct 9 02:45:04 Tower logger: *** Skipping any contents from this failed directory ***
Oct 9 02:45:04 Tower logger: rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2]
Oct 9 02:45:04 Tower logger: ./games/Nintendo DSI/Rhythm Paradise.nds
Oct 9 02:45:04 Tower shfs0: shfs_mkdir: assign_disk: games/Nintendo DSI (28) No space left on device
Oct 9 02:45:04 Tower logger: cd+++++++++ games/Nintendo DSI/
Oct 9 02:45:04 Tower logger: rsync: recv_generator: mkdir "/mnt/user0/games/Nintendo DSI" failed: No space left on device (28)

 

Oct 9 00:14:21 Tower kernel: mdcmd (23): clear 
Oct 9 00:14:21 Tower unmenu-status: Starting unmenu web-server
Oct 9 00:14:29 Tower kernel: mdcmd (26): check CORRECT
Oct 9 00:14:29 Tower kernel: md: recovery thread woken up ...
Oct 9 00:14:29 Tower kernel: md: recovery thread checking parity...
Oct 9 00:14:29 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks.
Oct 9 00:14:32 Tower apcupsd[1849]: apcupsd FATAL ERROR in linux-usb.c at line 609 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see . 
Oct 9 00:14:32 Tower apcupsd[1849]: apcupsd error shutdown completed
Oct 9 00:14:37 Tower kernel: mdcmd (29): nocheck 
Oct 9 00:14:37 Tower kernel: md: md_do_sync: got signal, exit...
Oct 9 00:14:37 Tower kernel: md: recovery thread sync completion status: -4
Oct 9 00:17:24 Tower kernel: mdcmd (56): check 
Oct 9 00:17:24 Tower kernel: md: recovery thread woken up ...
Oct 9 00:17:24 Tower kernel: md: recovery thread checking parity...
Oct 9 00:17:24 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks.
[color=red]Oct 9 01:09:47 Tower kernel: md: parity incorrect: 380084480[/color]
Oct 9 01:19:57 Tower kernel: mdcmd (503): nocheck 
Oct 9 01:19:57 Tower kernel: md: md_do_sync: got signal, exit...
Oct 9 01:19:57 Tower kernel: md: recovery thread sync completion status: -4
Oct 9 01:20:02 Tower kernel: mdcmd (506): check CORRECT
Oct 9 01:20:02 Tower kernel: md: recovery thread woken up ...
Oct 9 01:20:02 Tower kernel: md: recovery thread checking parity...
Oct 9 01:20:02 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks.
[color=red][font=Verdana]Oct 9 02:12:00 Tower kernel: md: parity incorrect: 380084480[/font][/color]

 

What seems to be the problem?

 

I have seen something similar, I'm guessing that the first time this error was hit:

 

Oct 9 01:09:47 Tower kernel: md: parity incorrect: 380084480

 

the parity got incorrectly computed and then the second time this error was reported:

 

Oct 9 02:12:00 Tower kernel: md: parity incorrect: 380084480

 

the parity got recomputed correctly.

 

Of course the sequence might be backwards if the original parity was incorrect.  Since you are running the "unmenu" web server you could use its option to "verify but do not correct" parity.  If you do this then you may see an error reported on one run and then no errors reported on the next run.

 

I have been finding that there is a zone, roughly in the middle of my array's block count, where I might get one or two such errors on maybe on one parity check in three.  I'll run the "nocorrect" verify pass and an error will show up, then I'll run a couple more verifies without seeing another error.  Sometimes there will be a "multi zone error" reported by one of the drives in the SMART report when this happens. I've replaced all the SATA cables, and just replaced the SATA controller cards too.  I suspect it might be heat related as the issue seemed more frequent in the summer.

 

Regards,

 

Stephen

 

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.