[SOLVE] How add a second disk for RAID feature. (2BIG2)

[maxdo]

Hello,
i've install with success your firmware fvdw-sl.
So, i've a 2BIG Network 2, and i want to install the second disk and put it in RAID 1.

following your document "Add additional disks instruction 5big2 2big2 nwsp2max 2big1 5big1-04oct15" i can read that, after install the firmware and access to the web interface, i need to power off the device, insert the second disk, restart the device, and then access via §SSH for the different command to run.....

But here i have a problem. in fact after inserting an empty disk in slot 2 (without any partition on it) and restart the NAS, seems how the OS in the HD 1 going in "TILT-2. the NAS, where first run and answer via web interface, it is hidden from the network, and it doesn't present him in any mode.
only shut down the NAS, remove the disk on the slot 2, and restart, anything came back to run regularly.
WHY?

:please can you give me a hand to see where is the problem?
many thanks

[Jocko]

Hi maxdo

following your document "Add additional disks instruction 5big2 2big2 nwsp2max 2big1 5big1-04oct15" i can read that,

This is an outdated howto. Now you can format the disk directly from the web-interface.

But here i have a problem. in fact after inserting an empty disk in slot 2 (without any partition on it) and restart the NAS, seems how the OS in the HD 1 going in "TILT-2. the NAS, where first run and answer via web interface, it is hidden from the network, and it doesn't present him in any mode.
only shut down the NAS, remove the disk on the slot 2, and restart, anything came back to run regularly.

Are you sure your disk is really empty ?

---edit---
In what slot you have the formatted disk by using fvdw-sl console?
it must be in the left slot when you see the back side

[Jocko]

I just checked if init disk menu handles an hot plug and then you can do :
- start the nas with only one disk (this one initialized with fvdw-sl console)
- plug the unformatted disk in 2d slot (so the right slot when you see the back side)
- go to the fiirmware interface and load the disk setup menu
- click on the button 'initialize disks'
- you should see your 2d disk on the table 'other disks'
- select it
- and do a submit

[maxdo]

Hello Jocko,
i have run the your procedure, for put on line the second disk.
after submit i have back the following screen (see attachment.
it is one houre that wait after that messagge but it is not change anything other that.
What can i do?
thanks

[maxdo]

Hello, update.
after to long time, i prefer shutdown thenas, removeteh second disk and restart.
but now when i enter in web configuration i'm in the nas server setup mode, withou the possibility to exit from that state.
the only way that i have, it is the running setup task.... but i press, after isnert the second disk, i have again the last screenshot hat i had send you, a nothing else for long time.
i can enter in sSH. there is a way for remove that stat from Console SSH?
thx

[Jocko]

:scratch

the only way that i have, it is the running setup task.... but i press, after isnert the second disk, i have again the last screenshot hat i had send you, a nothing else for long time.
i can enter in sSH. there is a way for remove that sta

It is the expected behaviour !
On this setup mode, we wants to a setup task ends even if there is a power outage. So the script restart at the step where it stopped!
You have detail in the help page :

Setup mode : is a special mode allowing to run some setup tasks like reset a disk or manage a raid (build, destroy,...)

This menu allows you to monitor the setup task and you can :

- Start the setup task by clicking on the related button. The firmware enables it only when it ended to activate the setup mode (stop any server except the web server and the SSH server; unmount all data partitions; disassemble the raids device)

- See the setup task progress

- Restart the setup task if previously it aborts with a critical errors. The firmware will try to restart it at the error step

- Restart the NAS to restore the regular mode by clicking on the button "Restart the NAS". This button is available only after running the setup task

Note: If a setup task is running, the script will restart at the current step on a power failure when you try to start again the setup task.

So to abort the setup mode, you just need to click on the button "Restart the NAS"

But please to keep this "setup mode" with the 2d disk, I think there is an issue with your disk. :whistle

So on the ssh window, do

Code: Select all

cat /proc/partitions
fdisk -l /dev/sdb
gdisk -l /dev/sdb

and post their output

[maxdo]

Hello Jocko
i'm sorry but i can't press the button "Restart the NAS" because it is in gray and it is not available. i suppose because teh Cron Task it never ends.
i'm try to reset the NAS with or without second disk in it, but doesn't fix the issue.
Below you can find my output command that you had ask me to do:

cat /proc/partitions

Code: Select all

login as: root
root@192.168.4.252's password:
root@fvdwsl-base:/ # cat /proc/partitions
major minor  #blocks  name

   1        0       4096 ram0
   1        1       4096 ram1
   1        2       4096 ram2
   1        3       4096 ram3
   1        4       4096 ram4
   1        5       4096 ram5
   1        6       4096 ram6
   1        7       4096 ram7
   1        8       4096 ram8
   1        9       4096 ram9
   1       10       4096 ram10
   1       11       4096 ram11
   1       12       4096 ram12
   1       13       4096 ram13
   1       14       4096 ram14
   1       15       4096 ram15
  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0  976762584 sdb
   8        1     514080 sdb1
   8        2     514080 sdb2
   8        3     514080 sdb3
   8        4          1 sdb4
   8        5     835380 sdb5
   8        6      64260 sdb6
   8        7     514080 sdb7
   8        8  973474740 sdb8
   8       16  976762584 sda

fdisk -l /dev/sdb

Code: Select all

root@fvdwsl-base:/ # fdisk -l /dev/sdb

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               9          72      514080  83 Linux
/dev/sdb2              73         136      514080  83 Linux
/dev/sdb3             137         200      514080  82 Linux swap
/dev/sdb4             201      121600   975145500   5 Extended
/dev/sdb5             209         312      835380  83 Linux
/dev/sdb6             321         328       64260  83 Linux
/dev/sdb7             337         400      514080  83 Linux
/dev/sdb8             409      121600   973474740  83 Linux

gdisk -l /dev/sdb

Code: Select all

root@fvdwsl-base:/ # gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************

Disk /dev/sdb: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 3677C8EA-0C5F-4DB5-86D8-68BE79A79DFC
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 663701 sectors (324.1 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1          128520         1156679   502.0 MiB   8300  Linux filesystem
   2         1156680         2184839   502.0 MiB   8300  Linux filesystem
   3         2184840         3212999   502.0 MiB   8200  Linux swap
   5         3341520         5012279   815.8 MiB   8300  Linux filesystem
   6         5140800         5269319   62.8 MiB    8300  Linux filesystem
   7         5397840         6425999   502.0 MiB   8300  Linux filesystem
   8         6554520      1953503999   928.4 GiB   8300  Linux filesystem
root@fvdwsl-base:/ #

Bye

---edit---
Please to use the BBCode "code" (<=>[ code]your output[/code]) when you paste an output from your terminal. It is more readable -Jocko

[Jocko]

Hi maxdo

Now I understand better what is the issue and there are only two cases :
-1- Either you did not understood my previous posts

- plug the unformatted disk in 2d slot (so the right slot when you see the back side)

---edit---
In what slot you have the formatted disk by using fvdw-sl console?
it must be in the left slot when you see the back side

-2- Or there is an hardware issue : the wires are swapped between the two sata ports

The right configuration is:

2big2-slot-id.jpg

if it is the case 1 and according your output, you have the system disk (this one initialized with fvdw-sl console) in the right slot and its kernel name is badly sdb and the 2d disk is plugged in the left slot.
In this case, you need to swap the disks

if it is the case 2
Did you open the box or did you know if someone did it previously ?
if yes, you should swap the connections for the disks mapping cables

[maxdo]

Hello, thank for your BIG support....
so, following your photo, i have exactly the disk connect how in the picture.
So the disk with the OS installed on the left side, mean the empty disk on the right.

Do you think that i have inside inverted the cable SATA.....? maybe. i will try to move the disk in the opposite slot (so try to put the OS in the right, and the Empty disk on the left....

. i will came back and update you after terminate that.
thanks

[maxdo]

Bingo....
after invert the disk, now it was check in right way:


root@fvdwsl-base:/ # cat /proc/partitions
major minor #blocks name

1 0 4096 ram0
1 1 4096 ram1
1 2 4096 ram2
1 3 4096 ram3
1 4 4096 ram4
1 5 4096 ram5
1 6 4096 ram6
1 7 4096 ram7
1 8 4096 ram8
1 9 4096 ram9
1 10 4096 ram10
1 11 4096 ram11
1 12 4096 ram12
1 13 4096 ram13
1 14 4096 ram14
1 15 4096 ram15
31 0 500 mtdblock0
31 1 4 mtdblock1
8 0 976762584 sda
8 1 514080 sda1
8 2 514080 sda2
8 3 514080 sda3
8 4 1 sda4
8 5 835380 sda5
8 6 64260 sda6
8 7 514080 sda7
8 8 973474740 sda8
8 16 976762584 sdb
8 17 976759808 sdb1

BUT now the cron task, after the delete table, report a error write in the LOg:

root@fvdwsl-base:/ # cat /etc/.setup.fs/setupjob.log
<b>Setup task reset.sh is now running</b><br>
Found disk: sdb(STR607MS3VSDKS) <br>
Delete the partiton table on sdb: <br><b>Setup task reset.sh is restarting</b><br>
Found disk: sdb(STR607MS3VSDKS) <br>
Delete the partiton table on sdb: <br><b>Setup task reset.sh is restarting</b><br>
Found disk: sdb(STR607MS3VSDKS) <br>
Delete the partiton table on sdb: <br><b>Setup task reset.sh is restarting</b><br>
Found disk: sdb(STR607MS3VSDKS) <br>
Delete the partiton table on sdb: <br><b>Setup task reset.sh is restarting</b><br>
Found disk: sdb(STR607MS3VSDKS) <br>
Delete the partiton table on sdb: <br><b>Setup task reset.sh is restarting</b><br>
Found disk: sdb(STR607MS3VSDKS) <br>
Delete the partiton table on sdb: OK<br>
Create a new partiton ms-dos table on sdb: <br>
=>fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
<span style="color:red;"><b>Fail (creating ms-dos partition table failed)</b></span><br>
root@fvdwsl-base:/ # login as: root
Password:

Now i can delete the task crone and came back to normal configuration menu ( i can push the button exit)

so, what it is the issue now :|

thanks