2Big Network 2, Hard disk 2 failed

[Jocko]

Be careful, if I remember well with a factory reset you lose your data! :shocked

With a 2tb you must have a ms-dos table on your disks

As written previously, the first step is to get a telnet access.

So keep your both disks on their slot, and stop the nas.

- Start the fvdw-sl console and select as action "load a standalone kernel".
- select later the kernel "UIMAGE-3142-KIRKWOOD-158-standalone"
- a new nc windows should be opened with a wait message : "waiting for u-boot..."
- so start at this step the nas
- wait until a telnet window is loaded
- then you should be able to login (login: root; password: giveit2me)

- Next is to create the ms-dos table on disk2
so on the telnet window, do and post the output

Code: Select all

fdisk -l

[manelppa]

Dear Jocko,
I've tried your suggestions. For safety reason, I duplicated the Disk 1 using a Standalone duplicator. Guessing it only read the hard disk and copying to the Disk 2.
You requested to re-create the partition table. It's already done because of the duplication. (I checked with Linux and all partitions & RAID array are visible on Ubuntu "Disks" tool. Do you think I should delete all parition and restart from over with the disk2 ?
Anyway, I've installed on a PC the new Console version (6-17 5jun2017) and proceeded as described (use Stand Alone Kernel). The Console interrupts as well the NAS Boot. But during the Telnet connection, it fails.

The NAS is connected directly to Cisco switch with the PC. The PC IP Address is 192.168.1.251 (as suggested in your documentation). Although I think I did correctly, the Telnet console prompt : connexion to 192.168.1.252 time out. Even if I try manually, no connexion is possible to the NAS.
What I'm missing or mistaking ?
Thanks in advance for (still :-)) help...

[manelppa]

Addition information : on the LaCie 2Big 2 Manual, it's said : you can reset without DATA loss.

A new step, a new hope : I've succeeded to get telnet access. I changed the PC IP address to xxx.xxx.xxx.250 and I got the Login prompt window.
I typed the cmd "fdisk -l" and I got the results :
- sda & sdb a present

Code: Select all

Device boot       starts               end      id     system
- sda1 & sdb1           1              250      f    win85 Ext'd (LBA)
- sda2 & sdb2       251        243201    83   Linux
- sda5 & sdb5           1                32    83   Linux
- sda6 & sdb6         33                33    83   Linux
- sda7 & sdb7         34                34    83   Linux
- sda8 & sdb8         35              140    83   Linux
- sda9 & sdb9       141              249    83   Linux
- sda10 & sdb10   250              250    83   Linux


One additional information : when I connect the hard disk (1 or 2) onto the Ubuntu session, the Raid arrays are visible and degraded because of 1 disk missing) => does it helps to know this ?

from this point, I've no idea what to do with Telnet and how to go further.

Because it's late, wishing you a good rest

[Jocko]

Hi manelppa,

The NAS is connected directly to Cisco switch with the PC. The PC IP Address is 192.168.1.251 (as suggested in your documentation). Although I think I did correctly, the Telnet console prompt : connexion to 192.168.1.252 time out. Even if I try manually, no connexion is possible to the NAS.

You misunderstood our documentation, 192.168.1.251 is not the ip for the laptop but the ip used by the nas after uploading the standalone kernel.
In this configuration you had an IP conflict and then you could not login.

For safety reason, I duplicated the Disk 1 using a Standalone duplicator.

Why not and indeed create a new partition table is no longer useful (even if my way would be faster..)
By duplicating, the 2d disk contains now bad information for the raid, it is seen as the first component.

We got now examine all partition to see if there is no issue and please to do nothing else

- upload the binary mdadm

Code: Select all

tftp -l /sbin/mdadm -r mdadm -g pc-ip

change pc-ip by the current ip of your laptop
- set run permissions

Code: Select all

chmod a+x /sbin/mdadm

and post the output (please to use the BBcode 'code' for making it more readable')

Code: Select all

mdadm --examine /dev/sda[25789]
mdadm --examine /dev/sdb[25789]

Please to post

Code: Select all

ls -l /dev/md[0-9]

to check if we need to create them later for assembling

[manelppa]

Dear Jocko,
Those are very precise instruction. Thanks a lot. I care about any instruction...
May I add few question to avoid any mistake ?
When you request to upload the binary mdam files, where should I take them from ? where should I copy them ?
I found a file "glibc-and-tools-archive.zip" containing the mdam files in the tftp folder of the console folder. Do I need to unzip the file and to which area ?

Thanks

[Jocko]

Ok you use the last package and with it it is a bit different and more easy.

So no need to run

Code: Select all

tftp -l /sbin/mdadm -r mdadm -g pc-ip
chmod a+x /sbin/mdadm


But you need to run in the telnet client the command: fvdw-sl-programs
then a menu will appear and select "Upload and extract glibc mini and tools"

Which will install some additional commands (so mdadm)

[manelppa]

Ok, now I uderstand better; Sorry for my lack of knowledge on linux cmd and mdadm...

I will let you know later about the results before any other action (well noticed ;-))

Renaud F.

[manelppa]

Code: Select all

 Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x2[code][code][/code][/code]
     Array UUID : 314180ec:946b243e:712e8d71:6a260445
           Name : LaCie-2big-2:4
  Creation Time : Sat Feb 18 18:36:38 2017
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB)
     Array Size : 1951503768 (1861.10 GiB 1998.34 GB)
   Super Offset : 3903007792 sectors
Recovery Offset : 487876096 sectors
          State : clean
    Device UUID : 08a1e732:26e2d5a6:60a750ca:df424fe3

    Update Time : Sat Jun  3 17:38:07 2017
       Checksum : 983d4c76 - correct
         Events : 61892


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
/dev/sda5:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 047a508c:c926253b:6da39a5a:1697ed9a
  Creation Time : Thu Jan  1 00:00:22 1970
     Raid Level : raid1
  Used Dev Size : 256896 (250.92 MiB 263.06 MB)
     Array Size : 256896 (250.92 MiB 263.06 MB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 3

    Update Time : Sat Jun  3 18:06:49 2017
          State : active
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 543e3430 - correct
         Events : 101


      Number   Major   Minor   RaidDevice State
this     1       8       21        1      active sync   /dev/sdb5

   0     0       8        5        0      active sync   /dev/sda5
   1     1       8       21        1      active sync   /dev/sdb5
/dev/sda7:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 2d15cfdd:9bc252df:e368bf24:bd0fce41
  Creation Time : Fri Jan 27 19:42:16 2017
     Raid Level : raid1
  Used Dev Size : 6912 (6.75 MiB 7.08 MB)
     Array Size : 6912 (6.75 MiB 7.08 MB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 0

    Update Time : Thu Jun  8 16:50:56 2017
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : c4413e69 - correct
         Events : 85


      Number   Major   Minor   RaidDevice State
this     0       8        7        0      active sync   /dev/sda7

   0     0       8        7        0      active sync   /dev/sda7
   1     1       0        0        1      faulty removed
/dev/sda8:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 1c8ffb0e:2bb8a661:e368bf24:bd0fce41
  Creation Time : Fri Jan 27 19:45:42 2017
     Raid Level : raid1
  Used Dev Size : 850304 (830.51 MiB 870.71 MB)
     Array Size : 850304 (830.51 MiB 870.71 MB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 8

    Update Time : Sun Jun  4 22:42:59 2017
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 43b9a87b - correct
         Events : 23


      Number   Major   Minor   RaidDevice State
this     0       8        8        0      active sync   /dev/sda8

   0     0       8        8        0      active sync   /dev/sda8
   1     1       0        0        1      faulty removed
/dev/sda9:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 3037c944:64b27f33:e368bf24:bd0fce41
  Creation Time : Fri Jan 27 19:47:33 2017
     Raid Level : raid1
  Used Dev Size : 874432 (854.08 MiB 895.42 MB)
     Array Size : 874432 (854.08 MiB 895.42 MB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 9

    Update Time : Sun Jun  4 22:42:58 2017
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 905bae18 - correct
         Events : 9


      Number   Major   Minor   RaidDevice State
this     0       8        9        0      active sync   /dev/sda9

   0     0       8        9        0      active sync   /dev/sda9
   1     1       0        0        1      faulty removed
-----------------------------------------------------------
 mdadm --examine /dev/sdb[25789]
/dev/sdb2:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x2
     Array UUID : 314180ec:946b243e:712e8d71:6a260445
           Name : LaCie-2big-2:4
  Creation Time : Sat Feb 18 18:36:38 2017
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB)
     Array Size : 1951503768 (1861.10 GiB 1998.34 GB)
   Super Offset : 3903007792 sectors
Recovery Offset : 487876096 sectors
          State : clean
    Device UUID : 08a1e732:26e2d5a6:60a750ca:df424fe3

    Update Time : Sat Jun  3 17:38:07 2017
       Checksum : 983d4c76 - correct
         Events : 61892


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
/dev/sdb5:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 047a508c:c926253b:6da39a5a:1697ed9a
  Creation Time : Thu Jan  1 00:00:22 1970
     Raid Level : raid1
  Used Dev Size : 256896 (250.92 MiB 263.06 MB)
     Array Size : 256896 (250.92 MiB 263.06 MB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 3

    Update Time : Sat Jun  3 18:06:49 2017
          State : active
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 543e3430 - correct
         Events : 101


      Number   Major   Minor   RaidDevice State
this     1       8       21        1      active sync   /dev/sdb5

   0     0       8        5        0      active sync   /dev/sda5
   1     1       8       21        1      active sync   /dev/sdb5
/dev/sdb7:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 2d15cfdd:9bc252df:e368bf24:bd0fce41
  Creation Time : Fri Jan 27 19:42:16 2017
     Raid Level : raid1
  Used Dev Size : 6912 (6.75 MiB 7.08 MB)
     Array Size : 6912 (6.75 MiB 7.08 MB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 0

    Update Time : Mon Jun  5 17:00:49 2017
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : c43d4c3e - correct
         Events : 71


      Number   Major   Minor   RaidDevice State
this     0       8       23        0      active sync   /dev/sdb7

   0     0       8       23        0      active sync   /dev/sdb7
   1     1       0        0        1      faulty removed
/dev/sdb8:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 1c8ffb0e:2bb8a661:e368bf24:bd0fce41
  Creation Time : Fri Jan 27 19:45:42 2017
     Raid Level : raid1
  Used Dev Size : 850304 (830.51 MiB 870.71 MB)
     Array Size : 850304 (830.51 MiB 870.71 MB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 8

    Update Time : Sun Jun  4 22:42:59 2017
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 43b9a87b - correct
         Events : 23


      Number   Major   Minor   RaidDevice State
this     0       8        8        0      active sync   /dev/sda8

   0     0       8        8        0      active sync   /dev/sda8
   1     1       0        0        1      faulty removed
/dev/sdb9:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 3037c944:64b27f33:e368bf24:bd0fce41
  Creation Time : Fri Jan 27 19:47:33 2017
     Raid Level : raid1
  Used Dev Size : 874432 (854.08 MiB 895.42 MB)
     Array Size : 874432 (854.08 MiB 895.42 MB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 9

    Update Time : Sun Jun  4 22:42:58 2017
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 905bae18 - correct
         Events : 9


      Number   Major   Minor   RaidDevice State
this     0       8        9        0      active sync   /dev/sda9

   0     0       8        9        0      active sync   /dev/sda9
   1     1       0        0        1      faulty removed
--------------------------------------------
root@fvdw-sta-kirkwood:/ # ls -l /dev/md[0-9]
brw-r-----    1 root     root        9,   0 Mar  5 00:27 /dev/md0
brw-r-----    1 root     root        9,   1 Mar  5 00:27 /dev/md1
brw-r-----    1 root     root        9,   2 Mar  5 00:27 /dev/md2
brw-r-----    1 root     root        9,   3 Mar  5 00:27 /dev/md3
brw-r-----    1 root     root        9,   4 Mar  5 00:27 /dev/md4
brw-r-----    1 root     root        9,   5 Mar  5 00:27 /dev/md5
brw-r-----    1 root     root        9,   6 Mar  5 00:27 /dev/md6
brw-r-----    1 root     root        9,   7 Mar  5 00:27 /dev/md7
brw-r-----    1 root     root        9,   8 Mar  5 00:27 /dev/md8
brw-r-----    1 root     root        9,   9 Mar  5 00:27 /dev/md9

[Jocko]

Ok

all is not logical with your output :scratch

Can you confirm me the duplicate disk is the right disk when you see the back side (slots side)

for partition 8 and 9, it is ok
for example for sda8, you have

Code: Select all

      Number   Major   Minor   RaidDevice State
this     0       8        8        0      active sync   /dev/sda8

and for sdb8

Code: Select all

      Number   Major   Minor   RaidDevice State
this     0       8        8        0      active sync   /dev/sda8

it is logical if sdb is the duplicated disk(sdb8 contains in the superblock raid settings for sda8)

but then on 7, it is not logical:
for example for sda7, we have

Code: Select all

      Number   Major   Minor   RaidDevice State
this     1       8       7        0     active sync   /dev/sda7

and for /dev/sdb7

Code: Select all

      Number   Major   Minor   RaidDevice State
this     1       8       23        0      active sync   /dev/sdb7

so sda7 and sdb7 are both detected as the first component of the raid scratch

Otherwise some information are missing on sda2 and sdb2 (they are the data partitions)
So post again the output

Code: Select all

madm --examine /dev/sda2
madm --examine /dev/sdb2

---edit---
seem the raid on sda5 and sdb5 is rebuilt at each boot. That seems normal as it is the swap partition

[manelppa]

Dear Jocko,
Sorry for my output but I confirm the disk1 is at the LEFT position (by looking from the rear of the NAS). Maybe it'll be better to delete all partition of the duplicated disk (disk2)...
Here is the second post of the data :

Code: Select all

root@fvdw-sta-kirkwood:/ # mdadm --examine /dev/sda2
/dev/sda2:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x2
     Array UUID : 314180ec:946b243e:712e8d71:6a260445
           Name : LaCie-2big-2:4
  Creation Time : Sat Feb 18 18:36:38 2017
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB)
     Array Size : 1951503768 (1861.10 GiB 1998.34 GB)
   Super Offset : 3903007792 sectors
Recovery Offset : 487876096 sectors
          State : clean
    Device UUID : 08a1e732:26e2d5a6:60a750ca:df424fe3

    Update Time : Sat Jun  3 17:38:07 2017
       Checksum : 983d4c76 - correct
         Events : 61892


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--------------------------
root@fvdw-sta-kirkwood:/ # mdadm --examine /dev/sdb2
/dev/sdb2:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x2
     Array UUID : 314180ec:946b243e:712e8d71:6a260445
           Name : LaCie-2big-2:4
  Creation Time : Sat Feb 18 18:36:38 2017
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB)
     Array Size : 1951503768 (1861.10 GiB 1998.34 GB)
   Super Offset : 3903007792 sectors
Recovery Offset : 487876096 sectors
          State : clean
    Device UUID : 08a1e732:26e2d5a6:60a750ca:df424fe3

    Update Time : Sat Jun  3 17:38:07 2017
       Checksum : 983d4c76 - correct
         Events : 61892


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)