Raid Jbod w/ busybox Help

[Tito]

On Sunday 22 March 2009 13:54:33 Mauro wrote:
>  Hi everybody
> 1st of all thanks for reading this, I'm unlucky owner of Lacie 2Big Network
> device ( as far as I know lacie violated usage terms of busybox, is that
> true ? ) and after the issue I had with the Seagate 7200.11 hard disk bug,
> taking it back to life with the rs232toTTL procedure spread over the
> internet, I began to have this issue.
> 
> The hard disk were part of a JBOD set ( 2 7200.11 1TB disks ) of this Lacie
> 2BIG Network device. Now the shares are not mounting, one of the disk is
> being seen as corrupt from the Lacie Device (hardware red led) and in
> Busybox log I see this error: "raid array is not clean -- starting
> background reconstruction"  I attach the whole log for any futher info.
> 
> Is there anything I can do for making the share available again instead of
> trying data recovery with 3rd party software ffrom a workstation ?
> 
> thanks
> bye
> 
> Mauro
> 

Hi,
are sure that it was a jbod disk set, because:

JBOD consists of an array of independent disks, it can be thought of as a distant relative of RAID.
Concatenation is sometimes used to turn several odd-sized drives into one larger useful drive, which
cannot be done with RAID 0. For example, JBOD (Just a Bunch Of Disks) could combine 3 GB, 15 GB,
5.5 GB, and 12 GB drives into a logical drive at 35.5 GB, which is often more useful than the individual
drives separately.

I don't think JBOD provides any data redundancy or ability to rebuild an array.
By looking at your log it seems to me that you are using RAID 1 at least on:

/dev/md0   
/dev/md1
/dev/md2
/dev/md3   setup as swap space :LACIE2BIG user.info kernel: Adding 128376k swap on /dev/md3.  Priority:-1 extents:1

grep raid  log.txt
Mar 20 13:37:59 LACIE2BIG user.info kernel: raid1: raid set md3 active with 1 out of 2 mirrors
Mar 20 13:39:55 LACIE2BIG user.info kernel: md: raid0 personality registered as nr 2
Mar 20 13:39:55 LACIE2BIG user.info kernel: md: raid1 personality registered as nr 3
Mar 20 13:39:55 LACIE2BIG user.err kernel: md: md0: raid array is not clean -- starting background reconstruction
Mar 20 13:39:55 LACIE2BIG user.info kernel: raid1: raid set md0 active with 1 out of 2 mirrors
Mar 20 13:39:55 LACIE2BIG user.err kernel: md: md1: raid array is not clean -- starting background reconstruction
Mar 20 13:39:55 LACIE2BIG user.info kernel: raid1: raid set md1 active with 1 out of 2 mirrors
Mar 20 13:39:55 LACIE2BIG user.info kernel: raid1: raid set md2 active with 1 out of 2 mirrors
Mar 20 13:39:55 LACIE2BIG user.info kernel: raid1: raid set md3 active with 1 out of 2 mirrors


Then there is  also:

Mar 20 13:39:56 LACIE2BIG local1.notice mountuserfs: Starting md4 (User)
Mar 20 13:40:00 LACIE2BIG local1.notice mountuserfs: Failure: Could not start md4
Mar 20 13:40:00 LACIE2BIG local1.notice mountuserfs: mounting /dev/md4 on /home failed

so, maybe this is the JBOD???

IMHO:
md0, md1, md2, md3 could be rebuild if you add a new disk, but it will take several hours to complete.

You can run in a shell: 

 while [ 1 == 1 ] ; do cat /proc/mdstat; sleep 1; done 

or 

watch -n .1 cat /proc/mdstat               

to check the rebuild process.

md4 if it is JBOD cannot be recovered.

You could post your /etc/fstab and the result of:

cat /proc/mdstat

to give us more details or better post on mailing list about linux raid as this is not a busybox problem.

Ciao,
Tito