Hi All,

 

I noticed one of my drives(ST2000DL001) had a red ball so i though i would try to rebuild it by taking array off-line and then rebuild it. Problem is when the drive was not installed i noticed the drive size had changed from 2TB to 3TB

 

 

When i then tried to bring the drive back online so i could rebuild it, i noticed a message "Stopped. Replacement disk is too small." and another message in the Array status "The replacement disk must be as big or bigger than the original"

 

I can access the drive from windows and also when i did bring the array online without this drive(DISK1 ) i can still access the movies on this drive from my media player.

 

Please any idea what is going on and how can i resolve this issue?

 

 

Hardware:

mobo: Asus Motherboard - M5A78L-M LX V2  http://uk.asus.com/Motherboards/AMD_AM3Plus/M5A78LM_LX_V2/#specifications

processor: AMD Sempron 145 OEM Processor

Drives: WD 3TB 3.5" SATA-III 6GB/s Caviar Green Hard Drive - 5400rpm 64MB Cache WD30EZRX  (PARITY)

        : Seagate 2TB ST2000DL001 (DISK 1) - This is the red ball drive, all other drives are all green

RAM: 1 x Patriot Signature 4GB DDR3 Memory http://www.play.com/PC/PCs/4-/23584140/Patriot-Signature-4GB-Sodimm-DDR3-1333-Memory/Product.html?_%24ja=tsid:11518|cat:23584140|prd:23584140

 

Running version: 5.0-beta14

syslog.txt

That sounds like a nasty bug in unRAID.

 

I know of no way to set the size expected.  Contact Lime-tech for resolution (unless you happen to have another 3TB drive to use as the replacement instead of the existing drive)

That sounds like a nasty bug in unRAID.

 

I know of no way to set the size expected.  Contact Lime-tech for resolution (unless you happen to have another 3TB drive to use as the replacement instead of the existing drive)

 

Thanks Joe.

Coincidentally i am meant to pick up a 3tb sata drive later this afternoon, so hopefully that should resolve the issue. My only worry is can this same issue occur with a 3TB i.e drive size change from 3TB to 4TB

 

 

I suspect that the problem has occurred because you only have the one data drive and it has then taken the size of the parity drive as the size to reconstruct.  If that is the case, it will not keep on demanding an ever-increasing data drive capacity.

I suspect that the problem has occurred because you only have the one data drive and it has then taken the size of the parity drive as the size to reconstruct.  If that is the case, it will not keep on demanding an ever-increasing data drive capacity.

I think you are right, but it is a serious bug, and not one easily detected in lime-tech's testing a new release.

 

Please report it as a bug in a PM/email to lime-technology.    Who knows, it might be resolved in the current "rc" release, but since I've see no other mention of it, odds are you are the first to discover it.  (even though you are several releases behind)

 

Joe L.

Thanks. I will report the bug via email

This same thing happened to me on one of the RC candidates (can't remember which one) about a month ago, where one of my drives was red-balled (due to a cabling issue), so I restarted the array with the drive missing, then re-added the same drive to the system. 

 

UnRaid then told me that it was too small. 

 

The way I got around it was to add the drive to another slot, and then copy all the info from disk x (and have UnRaid simulate the drive through the other drives and parity)  to the new drive (after pre-cleared again)

 

This bug has nothing to do with only having the one data drive and a parity, as I was running 16 drives at the time.

This same thing happened to me on one of the RC candidates (can't remember which one) about a month ago, where one of my drives was red-balled (due to a cabling issue), so I restarted the array with the drive missing, then re-added the same drive to the system. 

 

UnRaid then told me that it was too small. 

 

The way I got around it was to add the drive to another slot, and then copy all the info from disk x (and have UnRaid simulate the drive through the other drives and parity)  to the new drive (after pre-cleared again)

 

This bug has nothing to do with only having the one data drive and a parity, as I was running 16 drives at the time.

Again, please send an email/PM to Tom at limetech.  point him to this thread.

This same thing happened to me on one of the RC candidates (can't remember which one) about a month ago, where one of my drives was red-balled (due to a cabling issue), so I restarted the array with the drive missing, then re-added the same drive to the system. 

 

UnRaid then told me that it was too small. 

 

The way I got around it was to add the drive to another slot, and then copy all the info from disk x (and have UnRaid simulate the drive through the other drives and parity)  to the new drive (after pre-cleared again)

 

This bug has nothing to do with only having the one data drive and a parity, as I was running 16 drives at the time.

 

Looks like it is the same issue..I am currently running 8 drives including the parity drive

Just got back online..will be sending an email to Tom shortly