WD MyBook II questions

[gaf-mNDKBlG2WHs at public.gmane.org (Jerry Feldman)]

AFAIK both drives are good. They both mount properly as a RAID1 array on
Linux. I think I may have done something to the box although I don't
know what. The MyBook II is very simple to remove the drives. The bottom
line is that I just shipped it back to WD on RMA (in a Mini-Moos box :-).=


One question on the mdadm command. Once mdadm discovers the drives, how
important is it to do a STOP before removing the drives (eg)
mount /dev/mdnnn /foo
umount /foo
mdadm -S

When I get the system back next week, I want to be overly cautious.
Maybe I should have listened to Bogstad :-)

On 07/19/2009 08:17 AM, Jerry Feldman wrote:
> Yesterday, I set up the MybookII first my setting up users via the web
> interace,. I then popped the drives out, used 'mdadm --detail --scan
> --verbose' to detect the drives, and mounted the root partition (eg.
> md124). All well and good. I edited /etc/shadow to remove the root
> password, and /etc/inetd.conf to enable telnetd. I then unmonted the
> drives and placed them into the MyBookII. One mistake I made was to
> place the drives in the opposite order (A was in B's slot and B was in
> A's slot. After discovering my error I replaced them in the correct
> order, but the MyBookII failed to boot. I then removed the drives and
> checked them into my system (I love hot swap). I then mounted partition=

> 1 (as /dev/md124). All I did here was to check to see if the file syste=
m
> looked ok, and checked if rsync was available. Still no boot. So this
> morning I inserted the drives, but I get nothing from mdadm:
> Fdisk shows:
> Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes
> 255 heads, 63 sectors/track, 243201 cylinders
> Units =3D cylinders of 16065 * 512 =3D 8225280 bytes
> Disk identifier: 0x0001cf00
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdc1               5         248     1959930   fd  Linux raid
> autodetect
> /dev/sdc2             249         280      257040   fd  Linux raid
> autodetect
> /dev/sdc3             281         403      987997+  fd  Linux raid
> autodetect
> /dev/sdc4             404      243201  1950274935   fd  Linux raid
> autodetect
>
> Disk /dev/sdd: 2000.3 GB, 2000398934016 bytes
> 255 heads, 63 sectors/track, 243201 cylinders
> Units =3D cylinders of 16065 * 512 =3D 8225280 bytes
> Disk identifier: 0x0001cf00
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdd1               5         248     1959930   fd  Linux raid
> autodetect
> /dev/sdd2             249         280      257040   fd  Linux raid
> autodetect
> /dev/sdd3             281         403      987997+  fd  Linux raid
> autodetect
> /dev/sdd4             404      243201  1950274935   fd  Linux raid
> autodetect
>
> Before I did the scan, initially I used the -I flag. I can mount them
>
> This is what mdadm showed yesterday
> ARRAY /dev/md127 level=3Draid1 num-devices=3D2 metadata=3D0.90
> UUID=3D658b57d1:ca46008b:6a31894b:e0f4ea00
>    devices=3D/dev/sdd4,/dev/sdc4
> ARRAY /dev/md126 level=3Draid1 num-devices=3D2 metadata=3D0.90
> UUID=3D3371a2e6:55acae9c:07bafcb4:92b1dd2d
>    devices=3D/dev/sdd3,/dev/sdc3
> ARRAY /dev/md125 level=3Draid1 num-devices=3D2 metadata=3D0.90
> UUID=3Ddb6ffcaf:ca15217e:65d656a0:5605a909
>    devices=3D/dev/sdd2,/dev/sdc2
> ARRAY /dev/md124 level=3Draid1 num-devices=3D2 metadata=3D0.90
> UUID=3D4f3ee775:cd53ba76:3577bcbb:e2ebc6cc
>    devices=3D/dev/sdd1,/dev/sdc1
>
> Any ideas on how to fix this, first , what flags on mdadm can I use
> without screwing things up, and secondly allowing the MybookII to boot.=

>
>  =20


--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846