lacie 5 big network v.1 please support for fvdw

[fvdw]

:punk

all disks detected

you should have the web interface availbale now as as ssh server

PS DO NOT FORGET ABOUT THE FAN !

in the webinterface you should be able to see temperature of disk in slot 1 (disk setup menu)

Connet via ssh and give on the command line the command

Code: Select all

fdisk -l

and post output, it should find all 5 disks..

[taetae]

ok then if you do not need to test ra remain all so ...

cmq remember that with the standalone kernel tenet was not

[taetae]

Temperature Guard Hard Disk

Current setting: disabled, temperature limit 50 °C, WOL disabled
Information: Current HDD temperature = 28 °C
Max HDD temperature reached since last boot = 28 °C
Max HDD temperature ever reached = 56 °C


fan not work

[fvdw]

ok then if you do not need to test ra remain all so ...

cmq remember that with the standalone kernel tenet was not

only the above mentioned check with fdisk

With the standalone kernel we will deal later with to see if we can get that running. For the moment we can proceed with this one and use the web interface for upgrading. Only I need to make a package dedicated for the 5big1 !

[fvdw]

Temperature Guard Hard Disk

Current setting: disabled, temperature limit 50 °C, WOL disabled
Information: Current HDD temperature = 28 °C
Max HDD temperature reached since last boot = 28 °C
Max HDD temperature ever reached = 56 °C


fan not work

keep an eye on it and see if the fan comes on if the HD rises.
I don't know the trigger point of the controller but I would expect that it comes in above 40 oC.
if it still doesn't come on when we reach 50 oC then we need to find the cause why this fan is not running.
Think running the nas without the fan and having 5 diks operational will not be possible without the fan , it will overheat if the fan doesn't come on.
Unfortunate I did not find yet which gpio pin to set to start/stop the fan. i read that similar systems from lacie have a temp controlled fan that is operated from independent circuit not using kernel. There are a few pins that can be used to detect if the fan is running or not but also a trigger, maybe the last is the one to be set. I will look at it when you are on your business trip. Must be possible to solve

[taetae]

fan and once booted the button on / standby / off


ssh console

Code: Select all

/$ fdisk -l
Disk /dev/sde: 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/sde1               1      243202  1953512448   7 HPFS/NTFS
Disk /dev/sdd: 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/sdd1               1      243202  1953512448   7 HPFS/NTFS
Disk /dev/sdc: 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/sdc1               1      243202  1953512448   7 HPFS/NTFS
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               1      243202  1953512448   7 HPFS/NTFS
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1          64      513056  83 Linux
/dev/sda2              65         128      514080  83 Linux
/dev/sda3             129         192      514080  82 Linux swap
/dev/sda4             193       60801   486841792+  5 Extended
/dev/sda5             193         292      802226  83 Linux
/dev/sda6             293         293        7008+ 83 Linux
/dev/sda7             294         357      513056  83 Linux
/dev/sda8             358       60801   485515406  83 Linux

[taetae]

ok then we feel at the end of October ... hello and thank you for the experience

[fvdw]

perfect.

The disks 2TB seems to be formatted in ntfs. That we will need to change to ext3 but I guess that will be after your return.
Its time consuming to format 4 TB disks.
Ps there is no need to dismount the disk for this we can do it using ssh connecting and the linux available in the firmware.
This will be the commands needed
Change partition type
for each disk to be formatted use fdisk, for example sdb

Code: Select all

fdisk /dev/sdb


It will repsond with

Code: Select all

Command (m for help):

type command "t" behind this prompt (without the quotes)
it will ask which partition you want to change type, choose: 1
then choose the right id, in this case choose: 83 ( this is linux type)
then enter the command: "w" (without the quotes to write the new partition table to disk
repeat for the other 3 disks

Now format them

Code: Select all

mke2fs -j -m 1 /dev/sdb1
mke2fs -j -m 1 /dev/sdc1
mke2fs -j -m 1 /dev/sdd1
mke2fs -j -m 1 /dev/sde1

Note all data (if present on those disks will be erased but I guess these will be empty

ps ntfs is not a linux format and will give a very poor writing performance, it cannot be used for system disk in our firmware on this moment , ext3 format is standard we use in our firmware.

[fvdw]

yep to be continued as soon as you are back , have a safe trip

[taetae]

yep to be continued as soon as you are back , have a safe trip

It will not be possible to ext4??

ps hd if I divide it into partitions may be legally seen by the firmware?