Stuck trying upgrading Parity drive from 2tb to 4tb on 5.0.5

Sean_W_Smith · May 5, 2014

Hi All,

Currently on 5.0.5 on a 20 bay Norco with 4 sata's on the mobo and 1 SAS-MV8 8 port card and the SAS2-MV8 8 port card.

Both expansion cards seem to work well and the parity drive is currently on the mobo.

I can't figure out for the life of me how to upgrade my parity disk.

If I stop the array and pick the new disk it says its the wrong disk and wont start the array.

If I remove the parity drive complete and then reboot the array unprotected (which starts fine) and then shut the array down and select the 4TB as the new parity drive and then start the array the array fails to start. There is no error on the screen on anything obvious in the syslog.

I've read this thread here but its not working for me.

http://lime-technology.com/forum/index.php?topic=2280.0

Any ideas on how to debug this or what I might be doing wrong?

Thanks,

Sean

Sean_W_Smith · May 5, 2014

Here's a pastebin of the syslog of me trying to change the parity to the new disk.

http://pastebin.com/iQy3xsWn

Sean

Sean_W_Smith · May 5, 2014

Here's a snippet from the log if I disable the old parity disk and leave the array completely unprotected and then

try and add back the 4tb drive as a new drive....

May 5 16:44:56 LeRoi emhttp: Spinning up all drives...

May 5 16:44:56 LeRoi emhttp: shcmd (1355): /usr/sbin/hdparm -S0 /dev/sdo &> /dev/null

May 5 16:44:56 LeRoi kernel: mdcmd (41): spinup 0

May 5 16:44:56 LeRoi kernel: mdcmd (42): spinup 1

May 5 16:44:56 LeRoi kernel: mdcmd (43): spinup 2

May 5 16:44:56 LeRoi kernel: mdcmd (44): spinup 3

May 5 16:44:56 LeRoi kernel: mdcmd (45): spinup 4

May 5 16:44:56 LeRoi kernel: mdcmd (46): spinup 5

May 5 16:44:56 LeRoi kernel: mdcmd (47): spinup 6

May 5 16:44:56 LeRoi kernel: mdcmd (48): spinup 7

May 5 16:44:56 LeRoi kernel: mdcmd (49): spinup 8

May 5 16:44:56 LeRoi kernel: mdcmd (50): spinup 9

May 5 16:44:56 LeRoi kernel: mdcmd (51): spinup 10

May 5 16:44:56 LeRoi kernel: mdcmd (52): spinup 11

May 5 16:44:56 LeRoi kernel: mdcmd (53): spinup 12

May 5 16:44:56 LeRoi emhttp: writing GPT on disk (sdi), with partition 1 offset 64, erased: 0

May 5 16:44:56 LeRoi emhttp: shcmd (1356): sgdisk -Z /dev/sdi &> /dev/null

May 5 16:44:56 LeRoi emhttp: _shcmd: shcmd (1356): exit status: 1

May 5 16:44:56 LeRoi emhttp: shcmd (1357): sgdisk -o -a 64 -n 1:64:0 /dev/sdi |& logger

May 5 16:44:56 LeRoi logger: sgdisk: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by sgdisk)

May 5 16:44:56 LeRoi emhttp: shcmd (1358): udevadm settle

May 5 16:44:56 LeRoi emhttp: Start array...

May 5 16:44:56 LeRoi emhttp: mdcmd: write: No such device or address

May 5 16:44:56 LeRoi kernel: mdcmd (54): start RECON_DISK

May 5 16:44:56 LeRoi kernel: md: do_run: lock_rdev error: -6

May 5 16:44:56 LeRoi emhttp: shcmd (1359): rmmod md-mod |& logger

May 5 16:44:56 LeRoi emhttp: shcmd (1360): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger

May 5 16:44:56 LeRoi kernel: md: unRAID driver removed

Any ideas?

This works fine with 2TB drive.....

dgaschk · May 6, 2014

Run check disk on the flash in a Mac or PC.

Sean_W_Smith · May 6, 2014

OK trying now.....

Sean

Sean_W_Smith · May 6, 2014

OK that worked....

when I installed the stick the PC asked me to run chkdsk. never seen it do that before.

no the array starts and tries to rebuild parity but I am getting massive write errors trying to write to the drive....

syslog here...

http://pastebin.com/zDPZDibR

Sean_W_Smith · May 6, 2014

could attaching the 4TB drive to a PC and formatting it cause problems...... I did that previously to test the drive....

I wanted to try pre-clearing the disk so I started that....

Is this warning something I should be concerned about?

################################################################## 1.15
Device Model:     HGST HMS5C4040BLE640
Serial Number:    PL2331LAGJGVSJ
LU WWN Device Id: 5 000cca 22ec77dbb
Firmware Version: MPAOA5D0
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
WARNING: GPT (GUID Partition Table) detected on '/dev/sdn'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdn: 4000.8 GB, 4000787030016 bytes
256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdn1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.
########################################################################
invoked as  ./preclear_disk.sh /dev/sdn
########################################################################
(MBR 4k-aligned set. Partition will start on sector 64 for disks <= 2.2TB and sector 1 for disks > 2.2TB)
Are you absolutely sure you want to clear this drive?
(Answer Yes to continue. Capital 'Y', lower case 'es'): Yes
================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdn
=               cycle 1 of 1, partition start on sector 1
= Disk Pre-Read in progress: 0% complete
= ( 0  bytes of  4,000,787,030,016  read )
=

Sean_W_Smith · May 6, 2014

I see this at the bottom of my syslog....

May 6 11:34:00 LeRoi cache_dirs: cache_dirs process ID 9090 started, To terminate it, type: cache_dirs -q

May 6 11:38:53 LeRoi kernel: GPT:Primary header thinks Alt. header is not at the end of the disk.

May 6 11:38:53 LeRoi kernel: GPT:3519069871 != 7814037167

May 6 11:38:53 LeRoi kernel: GPT:Alternate GPT header not at the end of the disk.

May 6 11:38:53 LeRoi kernel: GPT:3519069871 != 7814037167

May 6 11:38:53 LeRoi kernel: GPT: Use GNU Parted to correct GPT errors.

May 6 11:38:53 LeRoi kernel: sdn: sdn1

dgaschk · May 6, 2014

This looks like the issue:

May  6 10:52:15 LeRoi emhttp: writing GPT on disk (sdo), with partition 1 offset 64, erased: 0 (Drive related)
May  6 10:52:15 LeRoi emhttp: shcmd (668): sgdisk -Z /dev/sdo $stuff$> /dev/null (Drive related)
May  6 10:52:15 LeRoi emhttp: _shcmd: shcmd (668): exit status: 1 (Other emhttp)
May  6 10:52:15 LeRoi emhttp: shcmd (669): sgdisk -o -a 64 -n 1:64:0 /dev/sdo |$stuff$ logger (Drive related)
May  6 10:52:15 LeRoi logger: sgdisk: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by sgdisk) (System)

It is usually cause by an incompatible add-on. Start up in SAFE-MODE.

Sean_W_Smith · May 6, 2014

Thanks I will try that once the preclear finishes.....

It still seems from me that when I plugged into windows via USB 2.0 and it thought it was a 2TB disk. maybe unraid is confused by the BS the USB 2.0 host under windows wrote to the disk. hopefully the preclear will fix this or your suggestion.

Sean

Sean_W_Smith · May 9, 2014

OK gonna try safe mode but I don't think that will solve it.

what happend was the parity sync failed at the very very end after 1+ days of syncing. pre_clear worked though......

I still think something thinks the disc is the wrong size...

here's what's in the syslog....