fvdw-sl firmware on a Network Space MAX

[morgand]

Hello,

Just wanted to give my feedback here:

I installed the fvdw-sl firmware on a Network Space MAX (2*2TB disks) and it is working.

The problem is that you only see one disk (although you check both disk in SMART menu).

I guess the trick to do this is deleting partitions on both disks.

- Launch the fvdw-sl-console
- Select standalone kernel, load and start
- Once the kernel is loaded, use fdisk on both sda and sdb to delete any partitions, write changes.
- Start again but this time choose install firmware. In my case I choose "I have a Network Space classic or lite", not LaCie firmware, disk is empty, no support for GPT.

After the installation, I was able to use my device with the new firmware.
I guess the LaCie firmware is installed on both disks since I never deleted sdb partitions before and wasn't able to use the firmware (still boot LaCie firmware, even after install).

I'm quite new to this but I hope this can help with future development.

[Jocko]

Hi morgand,

Thanks for the feedback.

The problem is that you only see one disk (although you check both disk in SMART menu).

Maybe we can resolve this by editing the NAS database.

Could you post the output of this command

Code: Select all

fdisk -l

[morgand]

Well, thanks for making this nice firmware :-)

I'll get back to it tomorrow and post the result.

[morgand]

Hi,

Here is the result:

Code: Select all

root@(none):/ # fdisk -l

Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               9          72      514080  83 Linux
/dev/sda2              73         136      514080  83 Linux
/dev/sda3             137         200      514080  82 Linux swap
/dev/sda4             201      243201  1951905532+  5 Extended
/dev/sda5             209         312      835380  83 Linux
/dev/sda6             321         328       64260  83 Linux
/dev/sda7             337         400      514080  83 Linux
/dev/sda8             409      243201  1950234772+ 83 Linux

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
root@(none):/ #


I can tell that there was some partitions on sdb before I delete them.

Let me know if you need me to perform some testing, like entering other commands or installing something else.
The disk is not used right now.

Thanks.

[Jocko]

[Warning]First, I see that you used custom settings for Advanced Format disk with sda partition table.
You do it because you are sure to have this disk type
If yes, you made an error for partition 8 (and sda4): the right end value would be : 243200 (instead of 243201)
Did you get a misalignment alert when you created it ?[/Warning]

So sdb is now empty.

I propose you to make a mirror of your sda disk. (Could be useful in few next releases when we will implement the RAID feature)

So as you use now our firmware, you have a ssh access and you can directly create the partition table of the sdb disk.

Open a putty window on your PC and connect you with this login :root and password : giveit2me

Create the new table with the command fdisk and the same custom settings for AF disk that you used for the sda disk (step i in the howtodo) . Be careful, check that you set the sdb disk !
Note : if you are sure to have AF disks use the value 243200 as end value for sdb8 and sdb4. I will explain you later how to fix partition sda8 with the right value.

Format the sdb8 partition.

Code: Select all

mke2fs -j -m 1 /dev/sdb8

After doing it post these outputs

Code: Select all

fdisk -l /dev/sdb
and
/usr/sbin/smartctl -a /dev/sda | grep -i serial | awk '{print $3}'
/usr/sbin/smartctl -a /dev/sdb | grep -i serial | awk '{print $3}'
and
/usr/sbin/smartctl -a /dev/sda | grep 'Device Model' | cut -f 2 -d : | tr -s " " (Note there one space betwen the double quotes)
/usr/sbin/smartctl -a /dev/sdb | grep 'Device Model' | cut -f 2 -d : | tr -s " "
and
df /dev/sdb8

And send me a pm (I changed your profile to allow you to do it) with your NAS database. Note if you already made some changes in the configuration as create account,..., the nas database contains some private data.

I assume that you have yet kept the share public. So do these commands in Putty :

Code: Select all

cp /rw_fs/etc/nas_conf_db.xml /share/1000/public
chmod a+w /share/1000/public/nas_conf_db.xml

and send me the file which are now in the public share (you must zip it before).

In the next step, I will send you the changed Nas database to see the 2d disk in the web interface.
Note : do not upgrade the firmware because it is useless (you need a version not yet released)

[morgand]

Well, I didn't set AF on the disk. What I remember is:

- Delete any partitions on sda and sdb using fdisk (i remember having a message saying something about incompatibilities with some old filesystems.
- Install firmware, not LaCie original firmware on disk, empty disk, not GPT and no support for it

I can do the whole installation again to be sure if you want.

One sure thing, I messed up a lot with the device (wasn't very careful as I was in a hurry).
I first ended with the LaCie firmware and my RAID messed up and when I try to recreate it, I can't use the whole 4TB capacity of the two disk.
So that's why I ended up deleting partitions in sdb too.

Let me know if you want me to continue, but I dunno what is the AF setting.

[Jocko]

So you don't have AF disks and you can keep the value 243201

as you used the fvdw-sl console the step i for creating manually the partition table is :

Code: Select all

fdisk /dev/sdb
use the command: n
it will respond with
command action
e extended
p primary (1-4)
type p as command and hit enter
now you get as response
Partition number (1-4):
type 1 behind it and hit enter
then you get as response
first cylinder 1-243201, default 1):
type 9 behind it and hit enter
response
last cylinder or...:
type 72 behind it and hit enter
create partition 2
n
p
2
73
136
create partition 3
n
p
3
137
200
make partition 3 type swap
type t as command
enter partition number 3
enter as hex code 82
create partition 4 (this is an extended partition)
n
e <---note the difference !!
4
201
243201
create partition 5 (no choice possible anymore for primary of extended, the additional partition will be made automatically in the extended partition)
n
209
312
create partition 6
n
321
328
create partition 7
n
327
400
create partition 8
n
409
243201
Now use the command p and see if the result is right

If the partition table is the same than sda  then use the command w to write the table to disk

[morgand]

Alright, so here is the message I was referring to earlier:

Code: Select all

fdisk /dev/sdb

The number of cylinders for this disk is set to 243201.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

I used sda partitions scheme to create sdb

Now for the results:

Code: Select all

fdisk -l /dev/sdb

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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      243201  1951905532+  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      243201  1950234772+ 83 Linux


Code: Select all

root@fvdwsl-base:/ # /usr/sbin/smartctl -a /dev/sda | grep -i serial | awk '{pri
nt $3}'
5YD0PM5D
root@fvdwsl-base:/ # /usr/sbin/smartctl -a /dev/sda | grep -i serial | awk '{pri
nt $3}'
5YD0PM5D
root@fvdwsl-base:/ # /usr/sbin/smartctl -a /dev/sda | grep 'Device Model' | cut
-f 2 -d : | tr -s " "
 ST2000DL001-9VT156
root@fvdwsl-base:/ # /usr/sbin/smartctl -a /dev/sdb | grep 'Device Model' | cut
-f 2 -d : | tr -s " "
 ST2000DL001-9VT156
root@fvdwsl-base:/ # df /dev/sdb8
Filesystem           1K-blocks      Used Available Use% Mounted on
df: /dev/sdb8: can't find mount point


Edit: I am unable to PM. I tried to logoff and restart browser. Same result.

[Jocko]

Ok,

About pm I will fix it.

you made a small error about the right command to get the serial number of the sdb disk

Code: Select all

/usr/sbin/smartctl -a /dev/sdb | grep -i serial | awk '{print $3}'

(you didn't change sda !)

And on my side, I made also an error. Currently sdb8 is not mounted. So do

Code: Select all

df /dev/sda8

[Jocko]

Now, you would be able to send pm