6 Replies Latest reply on Apr 10, 2012 3:36 AM by rpennol

    SS4000-E, rebuild and shared folder "not ready"

    rpennol

      Hi all,

      i've a trobule with a Lacie Ethernet Disk Raid (a Lacie branded Intel SS4000-E) with a RAID 5 w/o spare disk.

      The disk n. 2 failed and I was unable to continue to work with NAS (partition was mounted with NFS on a linux server).

      So I bought a new disk (the disk n. 2 ...) and i'm still rebuilding RAID.

       

      Schermata 04-2456024 alle 00.38.37.png

      In the 1st page i see:

       

      Schermata 04-2456024 alle 00.39.25.png

      Whill shared folder came ready when RAID finished rebuild ?

      Tnx in advance for help.

       

      BoB

        • 1. Re: SS4000-E, rebuild and shared folder "not ready"
          Dan_O

          On a RAID 5, the data should be available regardless of the status of the replacement drive.

           

          Does Lacie's version have any special restriction, that you know of?

          • 2. Re: SS4000-E, rebuild and shared folder "not ready"
            rpennol

            Hi Dan,

            raid5 was rebuilt. The strange is that NAS can't mount /public.

            I can access to NAS in ssh.

             

             

            # mdadm --detail --scan
            ARRAY /dev/md1 level=raid5 num-devices=4 UUID=07c2125e:d6e1b735:8c50bf4f:ef9fce2c
               devices=/dev/sda3,/dev/sdb3,/dev/sdc3,/dev/sdd3
            ARRAY /dev/md0 level=raid1 num-devices=4 UUID=4806857a:89707292:e7c4e35a:c47018fd
               devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1

             

             

            # mdadm --detail --scan /dev/md1

            /dev/md1:

                    Version : 00.90.01

              Creation Time : Thu May 15 13:51:30 2008

                 Raid Level : raid5

                 Array Size : 2196539520 (2094.78 GiB 2249.26 GB)

                Device Size : 732179840 (698.26 GiB 749.75 GB)

               Raid Devices : 4

              Total Devices : 4

            Preferred Minor : 1

                Persistence : Superblock is persistent

             

                Update Time : Sat Apr  7 07:40:51 2012

                      State : clean

            Active Devices : 4

            Working Devices : 4

            Failed Devices : 0

              Spare Devices : 0

             

                     Layout : left-symmetric

                 Chunk Size : 64K

             

                       UUID : 07c2125e:d6e1b735:8c50bf4f:ef9fce2c

                     Events : 0.104795538

             

                Number   Major   Minor   RaidDevice State

                   0       8        3        0      active sync   /dev/sda3

                   1       8       19        1      active sync   /dev/sdb3

                   2       8       35        2      active sync   /dev/sdc3

                   3       8       51        3      active sync   /dev/sdd3

             

             

             

             

            # dmesg

            ...

             

            md: md1 stopped.

            md: bind<sdb3>

            md: bind<sdc3>

            md: bind<sdd3>

            md: bind<sda3>

            raid5: device sda3 operational as raid disk 0

            raid5: device sdd3 operational as raid disk 3

            raid5: device sdc3 operational as raid disk 2

            raid5: device sdb3 operational as raid disk 1

            raid5: allocated 4201kB for md1

            raid5: raid level 5 set md1 active with 4 out of 4 devices, algorithm 2

            RAID5 conf printout:

            --- rd:4 wd:4 fd:0

            disk 0, o:1, dev:sda3

            disk 1, o:1, dev:sdb3

            disk 2, o:1, dev:sdc3

            disk 3, o:1, dev:sdd3

            ...
            The RAID5 exists and is allocated as MD1
            # fdisk -l /dev/md1
            You must set cylinders.
            You can do this from the extra functions menu.
            Disk /dev/md1: 2 heads, 4 sectors, 0 cylinders
            Units = cylinders of 8 * 512 bytes
                Device Boot    Start       End    Blocks   Id  System
            /dev/md1p1             1      2009      8032   77  Unknown
            Partition 1 has different physical/logical endings:
                 phys=(0, 254, 63) logical=(2008, 0, 1)
            Partition 1 does not end on cylinder boundary:
                 phys=(0, 254, 63) should be (0, 1, 4)
            /dev/md1p2          2009 536870910 2147475607+  88  Unknown
            Partition 2 has different physical/logical beginnings (non-Linux?):
                 phys=(1, 0, 1) logical=(2008, 0, 2)
            Partition 2 has different physical/logical endings:
                 phys=(1023, 254, 63) logical=(536870909, 1, 4)
            Partition 2 does not end on cylinder boundary:
                 phys=(1023, 254, 63) should be (1023, 1, 4)
            But i can't mount
            # mount -t xfs /dev/md1 /nas/NASDisk-00003/public/
            mount: Mounting /dev/md1 on /nas/NASDisk-00003/public failed: Invalid argument
            Any ideas ???
            • 3. Re: SS4000-E, rebuild and shared folder "not ready"
              john_s@intel

              Does /nas/NASDisk-00003/public/ exist?

               

              John

              • 4. Re: SS4000-E, rebuild and shared folder "not ready"
                rpennol

                No, i have hand made make with mkdir.

                The strange is:

                 

                 

                XFS mounting filesystem vbdi2
                Ending clean XFS mount for filesystem: vbdi2
                XFS mounting filesystem vbdi3
                XFS: Log inconsistent (didn't find previous header)
                XFS: failed to find log head
                XFS: log mount/recovery failed: error 5
                XFS: log mount failed
                XFS mounting filesystem vbdi2
                Ending clean XFS mount for filesystem: vbdi2
                XFS mounting filesystem vbdi3
                XFS: Log inconsistent (didn't find previous header)
                XFS: failed to find log head
                XFS: log mount/recovery failed: error 5
                XFS: log mount failed
                XFS mounting filesystem vbdi3
                XFS: Log inconsistent (didn't find previous header)
                XFS: failed to find log head
                XFS: log mount/recovery failed: error 5
                XFS: log mount failed

                 

                 

                Then /dev/md1 (vbdi2) has xfs filesystem troubles ...

                • 5. Re: SS4000-E, rebuild and shared folder "not ready"
                  edwardzh

                  Try this one:

                   

                  mount -t xfs /dev/vbdi3 /nas/NASDisk-00003

                   

                  If it's not working you may try to run xfs_check on /dev/vbdi3.

                  • 6. Re: SS4000-E, rebuild and shared folder "not ready"
                    rpennol

                    I love u man ! You saved me !!!!!!!

                     

                    I tried:

                     

                    # xfs_repair /dev/vbdi3

                     

                    and reboot.

                     

                    SS4000-E mounted regulary and all data was there