How to stop autosync on boot to run fsck

[captainhaddock]

I had a SATA reset on my duo (v1) and it eventually locked up so I had to pull the power lead to force a shutdown / kill

On reboot it now automatically goes into an xraid re-sync but also warns me I need to do a fsck / volume scan, it has locked up twice now before the resync has completed and I had to pull the power again each time.

I assume if I pull one disk this will stop the re-sync and once I have done the fsck I can reinsert the disk and have it sync.

How do I determine which is the primary disk being used as the source of the sync, obviously if I pull an out of date disk I will lose data etc

Is this a good method or have you any other recommendations to ensure integrity?

Looking at the SMART stats, for Disk 1 I see -
Reallocated Sector Count 4
Current Pending Sector 4
Offline Uncorrectable 3
Lp stat events 1598

Disk 2 is zero for these

Thanks in advance.

[captainhaddock]

Am I right in guessing from the log entries detailed below that disk 0 (the left hand disk) is the source of the resync and also the one with the problems?


Jul 1 00:54:13 amber kernel: Drive at position 0 found status 51, need retry.
Jul 1 01:04:18 amber kernel: :2req = 0 00000000,00000000,00000000,00000000 0
Jul 1 01:11:15 amber kernel: SYNC command time out.
Jul 1 01:11:15 amber kernel: start_position=1, XRAID_MAX_CHN=5,source_image=1,ready=1
Jul 1 01:11:15 amber kernel: ==== SATA init channel 0
Jul 1 01:11:15 amber kernel: After INIT SATA channel 0, retry=130, sata=113, status=50
Jul 1 01:11:15 amber kernel: ==== SATA init channel 1
Jul 1 01:11:15 amber kernel: After INIT SATA channel 1, retry=398, sata=113, status=50
Jul 1 01:12:55 amber kernel: :Drive at position 0 found status 51, need retry.
Jul 1 01:12:55 amber kernel: Drive at position 0 found status 51, need retry.
Jul 1 01:25:22 amber kernel: :2req = 0 00000000,00000000,00000000,00000000 0
Jul 1 01:29:57 amber kernel: SYNC command time out.
Jul 1 01:29:57 amber kernel: start_position=1, XRAID_MAX_CHN=5,source_image=1,ready=1
Jul 1 01:29:57 amber kernel: ==== SATA init channel 0
Jul 1 01:29:57 amber kernel: After INIT SATA channel 0, retry=131, sata=113, status=50
Jul 1 01:29:57 amber kernel: ==== SATA init channel 1
Jul 1 01:29:57 amber kernel: After INIT SATA channel 1, retry=0, sata=113, status=50
Jul 1 01:30:00 amber kernel: Drive at position 0 found status 51, need retry.
Jul 1 01:30:00 amber kernel: Drive at position 0 found status 51, need retry.
Jul 1 01:30:27 amber kernel: 2req = 0 00000000,00000000,00000000,00000000 0
Jul 1 01:47:01 amber kernel: 0000000 0
Jul 1 01:47:01 amber kernel: 2req = 0 00000000,00000000,00000000,00000000 0
Jul 1 01:47:22 amber last message repeated 2615 times
Jul 1 01:47:22 amber kernel: SYNC command time out.
Jul 1 01:47:22 amber kernel: start_position=1, XRAID_MAX_CHN=5,source_image=1,ready=1
Jul 1 01:47:22 amber kernel: ==== SATA init channel 0
Jul 1 01:47:22 amber kernel: After INIT SATA channel 0, retry=130, sata=113, status=50
Jul 1 01:47:22 amber kernel: ==== SATA init channel 1
Jul 1 01:47:22 amber kernel: After INIT SATA channel 1, retry=0, sata=113, status=50
Jul 1 03:41:00 amber kernel: :::::::::::::::::::::::::::::::::::::::Drive at position 0 found status 51, need retry.
Jul 1 03:41:00 amber kernel: Drive at position 0 found status 51, need retry.
Jul 1 03:47:32 amber kernel: :2req = 0 00000000,00000000,00000000,00000000 0
Jul 1 03:53:05 amber kernel: 2req = 0 00000000,00000000,00000000,00000000 0
Jul 1 03:58:01 amber kernel: SYNC command time out.
Jul 1 03:58:01 amber kernel: start_position=1, XRAID_MAX_CHN=5,source_image=1,ready=1
Jul 1 03:58:01 amber kernel: ==== SATA init channel 0
Jul 1 03:58:01 amber kernel: After INIT SATA channel 0, retry=133, sata=113, status=50
Jul 1 03:58:01 amber kernel: ==== SATA init channel 1
Jul 1 03:58:01 amber kernel: After INIT SATA channel 1, retry=0, sata=113, status=50
Jul 1 04:00:11 amber ntpdate[9955]: step time server 209.249.181.23 offset -0.637306 sec
Jul 1 04:48:34 amber kernel: :::::::::::::::::Sync:1, source_image=1/1, between 4096032 to 3907008718,all_tgt=3
Jul 1 06:25:27 amber syslogd 1.4.1#10: restart.
Jul 1 06:25:31 amber ntpdate[12623]: step time server 209.249.181.23 offset 0.084689 sec
Jul 1 06:47:02 amber kernel: ::::::::::::::::::::::::::::::::::::::::::X_RAID_DUMP
Jul 1 06:47:02 amber kernel:
Jul 1 06:47:02 amber kernel: VERSION/ID : SB=(V:0.1.0) ID=<3f374895.00000000.00000000.00000000> CT:4e2a78bd
Jul 1 06:47:02 amber kernel: RAID_INFO : DISKS(TOTAL:2 RAID:2 PARITY:1 ONL:2 WRK:2 FAILED:0 SPARE:0 BASE:0)
Jul 1 06:47:02 amber kernel: SZ:3907008688 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:3907008686
Jul 1 06:47:02 amber kernel: LOGICAL_DRIVE : 0: B:0000000032 E:0004096000 R:1 O:1 I:1:000000000 DM:3
Jul 1 06:47:02 amber kernel: LOGICAL_DRIVE : 1: B:0004096032 E:3902912686 R:1 O:1 I:1:000000000 DM:3
Jul 1 06:47:02 amber kernel: PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:3907008688,ST: B:online>
Jul 1 06:47:02 amber kernel: PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:3907008688,ST:P :online>
Jul 1 06:47:02 amber kernel: CURRENT_DRIVE : DISK<N:0/1,XXX(22,0),ID:0,PT:1,SZ:3907008688,ST: B:online>
Jul 1 06:47:02 amber kernel:
Jul 1 06:47:02 amber kernel: VERSION/ID : SB=(V:0.1.0) ID=<3f374895.00000000.00000000.00000000> CT:4e2a78bd
Jul 1 06:47:02 amber kernel: RAID_INFO : DISKS(TOTAL:2 RAID:2 PARITY:1 ONL:2 WRK:2 FAILED:0 SPARE:0 BASE:0)
Jul 1 06:47:02 amber kernel: SZ:3907008688 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:3907008686
Jul 1 06:47:02 amber kernel: LOGICAL_DRIVE : 0: B:0000000032 E:0004096000 R:1 O:1 I:1:000000000 DM:3
Jul 1 06:47:02 amber kernel: LOGICAL_DRIVE : 1: B:0004096032 E:3902912686 R:1 O:1 I:1:000000000 DM:3
Jul 1 06:47:02 amber kernel: PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:3907008688,ST: B:online>
Jul 1 06:47:02 amber kernel: PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:3907008688,ST:P :online>
Jul 1 06:47:02 amber kernel: CURRENT_DRIVE : DISK<N:1/2,XXX(33,0),ID:1,PT:1,SZ:3907008688,ST:P :online>
Jul 1 06:47:02 amber kernel:
Jul 1 06:47:02 amber kernel: VERSION/ID : SB=(V:0.1.0) ID=<3f374895.00000000.00000000.00000000> CT:4e2a78bd
Jul 1 06:47:02 amber kernel: RAID_INFO : DISKS(TOTAL:2 RAID:2 PARITY:1 ONL:2 WRK:2 FAILED:0 SPARE:0 BASE:0)
Jul 1 06:47:02 amber kernel: SZ:3907008688 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:3907008686
Jul 1 06:47:02 amber kernel: LOGICAL_DRIVE : 0: B:0000000032 E:0004096000 R:1 O:1 I:1:000000000 DM:3
Jul 1 06:47:02 amber kernel: LOGICAL_DRIVE : 1: B:0004096032 E:3902912686 R:1 O:1 I:1:000000000 DM:3
Jul 1 06:47:02 amber kernel: PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:3907008688,ST: B:online>
Jul 1 06:47:02 amber kernel: PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:3907008688,ST:P :online>
Jul 1 06:47:02 amber kernel: CURRENT_DRIVE : DISK<N:0/1,XXX(22,0),ID:0,PT:1,SZ:3907008688,ST: B:online>
Jul 1 06:47:02 amber kernel:
Jul 1 06:47:02 amber kernel: RUN_PARAMETERS: raid_running=1,last_word=ok,interface_start_at=1,fake=0
Jul 1 06:47:02 amber kernel: RAID_REBUILD : sync=1,logical=1,parity=1,sectors/TOTAL=957558816/3907008717
Jul 1 06:47:02 amber kernel: : source=1, total_drives=1, auto_sync=1
Jul 1 06:47:02 amber kernel: RAID_P_CHECK : chck=0,logical/total=0/2,raid_level=0
Jul 1 06:47:02 amber kernel: : err/sectors/TOTAL=0/0/0,report_err=1
Jul 1 06:47:02 amber kernel: : initialized=0x3,initialize_error=0x0,initializing=0x0
Jul 1 06:47:02 amber kernel: : where=0,total=0
Jul 1 06:47:02 amber kernel: SIZE_INFOR : sb_size=9440,sections_size=32/256,disk_t_size=128
Jul 1 06:47:02 amber kernel: : sb=f8148294,disks=512/1536,luns=2048/3168,thisdisk=5216/128,diskid=5344/4096
Jul 1 06:47:02 amber kernel: DJO_RECORD : dj_raid=NO_RAID,chns=0,source=0,disks=0 parity=0,chn_image=3,
Jul 1 06:47:02 amber kernel: : sectors=3675392/0x381500,need_IO=0
Jul 1 06:47:02 amber kernel: IO__RECORD : 0=1422118,1=528,2=0,3=0, busy=0/0/1/0/0,t_d=3


Any suggestions as to the best way to proceed most gratefully received.

TIA.

[de_niro]

"Current Pending Sector 4" means there are 4 bad sectors on the HDD,so do not try anything on this disk and you must to replace it to another good disk.

[StephenB]

de niro wrote:
"Current Pending Sector 4" means there are 4 bad sectors on the HDD,so do not try anything on this disk and you must to replace it to another good disk.

If the bad sector is found on a read request, you get "current pending sector", it becomes a reallocated sector when you write to it.

Although any increase in current pending counts or reallocated counts is concerning, immediate replacement of a disk with 4 of each is an aggressive replacement strategy. The more serious issue is the lockups. Likely this is also disk 1 (counting them as 1 and 2), though it would be good to check it.

So I would remove disk 1 and test it offline with vendor tools.

If the disk is under warranty, you can exchange it with the manufacturer with a refurbished unit (if advanced replacement is an option, it is usually good to take it). Another option is to buy a replacement disk, and use the RMA replacement as a spare.

[captainhaddock]

Many Thanks guys, spent the weekend trying to ensure the rsync completed successfully to top up my backups before pulling disk 1, 3rd attempt at the sync succeeded after 17 hours.

Will now run the WD diags.

Appreciate the advice.