Hello all,

 

I purchased a server from Lime Technology and all has been well for over 4 years.  Space was getting tight so I decided to upgrade to allow the jump to 3TB drives.  I upgraded the following:

- did a preclear on a new WD Green 3 TB drive, no errors all looked good

- stopped the array and shut down the server

- replaced the old parity drive with the new 3TB drive

- started up the server and then assigned the new drive to the party

- clicked yes to bring array back online and do a parity sync.

- after 24 hours I got a blue ball and message that the disk was disabled and not valid?

 

repeated the sync same issue

 

I have a 2nd 3tb drive that I have installed on the server but not done a pre-clear yet, tried to set it as parity and bring back online and sync, but server would not start.

 

I am hoping that I am just missing something simple, appreciate some guidance and help.

 

I just shut down and then brought back up and am trying a sync against original 3TB drive for 3rd time hoping that the reboot helped in some way.

 

Running: Unraid Pro 5.0-beta8d

Log attached

 

 

 

Many thanks in advance,

 

Unraid_Log_-_Parity_Sync_Issue.txt

I would upgrade to the newest "rc6-test2" beta and then attempt your replacement of the parity disk.

Apparently, your kernel-driver/disk/disk-controller combination is attempting to go past the end of the disk.

ul 30 17:51:30 Tower kernel: attempt to access beyond end of device

Jul 30 17:51:30 Tower kernel: sdi1: rw=1, want=4294967296, limit=4294967295

Jul 30 17:51:30 Tower kernel: md: disk0 write error

Jul 30 17:51:30 Tower kernel: handle_stripe write error: 4294967288/0, count: 1

Jul 30 17:51:30 Tower kernel: attempt to access beyond end of device

Jul 30 17:51:30 Tower kernel: sdi1: rw=1, want=4294967304, limit=4294967295

Jul 30 17:51:30 Tower kernel: md: md_do_sync: got signal, exit...

Jul 30 17:51:30 Tower kernel: md: disk0 write error

Jul 30 17:51:30 Tower kernel: handle_stripe write error: 4294967296/0, count: 1