Hi,

I am currently running version 4.7

15 Drives + Parity

 

The issue I currently have is I was replacing a smaller drive 'Disk1' 1TB with with a new 2TB drive and when I checked on it appears that another drive 'Disk5' became 'DISK_DSBL'

It appears that the new drive didn't completely rebuild as it only has a few files on it.

 

I have the original Drive1 untouched from the server.

 

I believe I need to place the original drive back in the array and get the server to see Disk5 again and do a initial config to rebuild parity but I would like to make sure that is the proper process before attempting anything.

 

Thanks

Grant

 

 

 

 

syslog-2012-12-09.zip

Looks like Disk5 is on the way out.

 

So just trying to find out how to keep as much data as it failed during the rebuild I believe.

 

I ran the commands as recommended by Joe L, on another post with DISK_DSBL

 

smartctl -a /dev/sdX - included

hdparm -I /dev/sdX - included

 

can you get it to show you the partitioning using fdisk?

fdisk -l dev/sdX - (nothing returned)

 

can you read it using "dd"

dd if=dev/sdX count=1 | od -c - (nothing returned)

 

smartctl_disk_5.txt

hdparm_disk_5.txt

Send an email to Lime-tech and reference this thread.

The big question here is if you made a copy of your /boot/config folder prior to the disk replacement. If you did, you can restore it and start the old configuration of the array right now, with the old "Disk1"on it's place, and replace the "Disk5" with the new "Disk1", and let it rebuild. If not, there's still a way of erase and restore the array super block, but wait until Joe L. or other senior member come here and explain it.

 

Unfortunately I didn't make a copy of the /boot/config folder before disk replacement.

 

Sent email to '[email protected]' is that the best address?

Sent email to '[email protected]' is that the best address?

yes.