Raid Jbod w/ busybox Help

[Mauro]

Hi,
this device 2BIG NETWORK has high potential but due to lack of Lacie support
and heavy tech user large adoption SSH is still an incognite (need trying
device hacking as with edmini) however coming to us:

I found this article
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/108971 in which refers
to alowing coming up of JBOD raid in "degraded mode" using this code
http://launchpadlibrarian.net/9478401/failed-raid.patch

do you think it's still excutable from bbox ?

thanks
bye

Mauro



On Mon, Mar 23, 2009 at 8:35 AM, Tito <farmatito at tiscali.it> wrote:

> On Monday 23 March 2009 08:21:23 Mauro wrote:
> > Hi,
> > thanks for your answer. Now I can't provide details about the partition
> > because I'm not at home, however as far as I remember the 2 disks have 7
> > partitions each one, one of those is 950+ gigabytes and is the one
> probably
> > mounted as jbod. As you noticed probably all the others partitions are
> used
> > for system purposes and are in raid1. However on the device basicly there
> is
> > this selector which allow you to choose between concatenation or raid1
> and
> > now is set on concatenation(so I think it is jbod. A Diskinternals
> Windows
> > software for Ext2 RAID recovery sees it as JBOD as well.).
> >
> > I read on some forum that with the warning "raid array is not clean --
> > starting background reconstruction" and a jbod array it is possible to
> > ignore this warning allowing mounting, I can't find the discussion where
> > this was explained, gonna post it later... just in case
> >
> > however I'm still missing the way how I can remotey telnet (ssh ? how ?)
> the
> > device to give those commands. Could you please explain it too me ?
> >
> > bye
> > Mauro
> >
>
> Hi,
> the Lacie Ethernet Raid for example supports SSH, but it must be
> enabled by the user through a page dedicated to debug purposes
> in the web interface. Google for it. If you can enable it
> you can use some program like putty (win or linux version)
> to ssh into the box and carry out more investigation.
> One more option could be to check for some serial port
> in the device, but this is more complicated as you need
> to open the box and do some soldering etc.
>
> Ciao,
> Tito
>
> >
> >
> >
> > On Sun, Mar 22, 2009 at 10:00 PM, Tito <farmatito at tiscali.it> wrote:
> >
> > >  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
> > >
> > >
> > >
> > >
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20090323/24979337/attachment.htm>