Had one parity and one data drive. Shutdown server, install a 3rd drive, startup server, wen to main page, stopped array, assigned drive from drop down list, tried to start array and every time i press the start button it shows the status as being stopped. Removed old partition from drive as it used to be in my v4 unraid server but same results. Am I missing a step? Is there a more advanced clear that needs to be performed?

 

Thanks.

 

JR

attach a syslog.  (one that includes the time period where you pressed the start button)

Zip the syslog before attaching it if too large to attach otherwise. (the compress really well)

 

Also, what happens when you type:

sgdisk

 

Joe L.

root@Tower2:~# sgdisk /dev/sdf

 

***************************************************************

Found invalid GPT and valid MBR; converting MBR to GPT format.

***************************************************************

 

 

Warning! Secondary partition table overlaps the last partition by

33 blocks!

You will need to delete this partition or resize it in another utility.

 

 

 

Apr 28 12:54:51 Tower2 emhttp: shcmd (5611): rmmod md-mod |$stuff$ logger (Other emhttp)

Apr 28 12:54:51 Tower2 kernel: md: unRAID driver removed (System)

Apr 28 12:54:51 Tower2 emhttp: shcmd (5612): modprobe md-mod super=/boot/config/super.dat slots=3 |$stuff$ logger (unRAID engine)

Apr 28 12:54:51 Tower2 emhttp: shcmd (5613): udevadm settle (Other emhttp)

Apr 28 12:54:51 Tower2 kernel: md: unRAID driver 2.1.6 installed (System)

Apr 28 12:54:51 Tower2 emhttp: Device inventory: (Drive related)

Apr 28 12:54:51 Tower2 emhttp: ST2000DM001-9YN164_W240YJLJ (sdb) 1953514584 (Drive related)

Apr 28 12:54:51 Tower2 emhttp: WDC_WD1600JD-75HBB0_WD-WMAL91065310 (sdc) 156250000 (Drive related)

Apr 28 12:54:51 Tower2 emhttp: ST2000DM001-9YN164_W240Y7WT (sde) 1953514584 (Drive related)

Apr 28 12:54:51 Tower2 emhttp: ST1000DL002-9TT153_W1V0H2B4 (sdf) 976762584 (Drive related)

Apr 28 12:54:51 Tower2 emhttp: shcmd (5614): /usr/local/sbin/emhttp_event driver_loaded (System)

Apr 28 12:54:51 Tower2 kernel: mdcmd (1): import 0 8,16 1953514552 ST2000DM001-9YN164_W240YJLJ (unRAID engine)

Apr 28 12:54:51 Tower2 kernel: md: import disk0: [8,16] (sdb) ST2000DM001-9YN164_W240YJLJ size: 1953514552 (Drive related)

Apr 28 12:54:51 Tower2 kernel: mdcmd (2): import 1 8,64 1953514552 ST2000DM001-9YN164_W240Y7WT (unRAID engine)

Apr 28 12:54:51 Tower2 kernel: md: import disk1: [8,64] (sde) ST2000DM001-9YN164_W240Y7WT size: 1953514552 (Drive related)

Apr 28 12:54:51 Tower2 kernel: mdcmd (3): import 2 8,80 976762552 ST1000DL002-9TT153_W1V0H2B4 (unRAID engine)

Apr 28 12:54:51 Tower2 kernel: md: import disk2: [8,80] (sdf) ST1000DL002-9TT153_W1V0H2B4 size: 976762552 (Drive related)

Apr 28 12:54:51 Tower2 kernel: md: disk2 new disk (unRAID engine)

Apr 28 12:54:51 Tower2 emhttp_event: driver_loaded (System)

See here: http://lime-technology.com/forum/index.php?topic=9880.0

There have been several instances of folks having this problem.  It seems to be a bug in the current release of v5.

 

If you run Joe L's excellent Pre-Clear script on the drive, it can then be added to your array with no problem.

 

Here are a couple of threads outlining the same problem:

 

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

 

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

... here's a link to Joe L's thread detailing how to use Pre-Clear:

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

 

Preclear worked like a charm. Thanks for the info! I did do a search on the forums before I posted but couldn't seem to locate any info about this issue.

 

JR

You're welcome.

 

It's not supposed to require the use of Pre-Clear ... but clearly it does now.  Not sure how long it's been an issue -- most folks already use Pre-Clear, so until a few folks started having problems adding new drives it wasn't apparent there was an issue.

 

Hopefully Tom will have this resolved fairly soon 

 

[Although frankly, Pre-Clear is a better way to add a drive anyway.]

This issue is caused by an add-on. Contact the add-on developer for a fix.

This issue is caused by an add-on. Contact the add-on developer for a fix.

 

Do you know which add-on causes this?  I sent Tom a note a few days ago noting that there are SEVERAL folks posting recently with the same issue -- some of which indicate they're running a "plain" install with no add-ons except UnMenu (which is a VERY safe add-on).  If you know a specific add-on that's causing this, you should let him know and post a note in the thread for that specific add-on warning folks of the drive-clearing issue it creates.    I suspect many would never encounter it -- since most of us use Pre-Clear;  but it should nevertheless be noted.

 

Apparently some folks have resolved this issue by removing Simple Features.

 

Just curious if that's the cause of this issue.    Were you using Simple Features?