plugout.net

I've tried to install fvdw-sl in my old Lacie 5Big Network (version 1), but cannot get to the end of it.

I've removed 4 disks (only number one is left).

I run everything, it boots, the script runs till completion, but after reboot I cannot connect to any IP address in the range 192.168.0.* and the scanning doesn't find the NAS.

installer.log:

fvdw-sl-installer log
tftpd ip address 192.168.0.5
getting required programs from tftp server 192.168.0.5
Dialog installed
xterm installed
mke2fs-ext3 present
gdisk present
Start fvdw-sl firmware installer version 4.0
cpuinfo= LaCie 5Big1 Network
selected nas type 5big1 platform orion
selected disk /dev/sda
gpt support bootloader selected no
selected partion table type msdos
Deleting old msdos partiton table
deleting msdos partition succeeded

create new partiton table
create ms-dos partiton table
max cylinder 60801
ms-dos partiton scheme disk last cylinder 60800 (-1)
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.


The number of cylinders for this disk is set to 60801.
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)

Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (9-60801, default 60801):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (73-60801, default 60801):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (137-60801, default 60801):
Command (m for help): Partition number (1-4): Hex code (type L to list codes): Changed system type of partition 3 to 82 (Linux swap)

Command (m for help): Command action
e extended
p primary partition (1-4)
Selected partition 4
First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (201-60801, default 60801):
Command (m for help): First cylinder (201-60800, default 201): Last cylinder or +size or +sizeM or +sizeK (209-60800, default 60800):
Command (m for help): First cylinder (201-60800, default 201): Last cylinder or +size or +sizeM or +sizeK (321-60800, default 60800):
Command (m for help): First cylinder (201-60800, default 201): Last cylinder or +size or +sizeM or +sizeK (337-60800, default 60800):
Command (m for help): First cylinder (201-60800, default 201): Last cylinder or +size or +sizeM or +sizeK (409-60800, default 60800):
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
creating ms-dos partiton table succeeded
format partition 5
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
52304 inodes, 208845 blocks
2088 blocks (1.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=213909504
7 block groups
32768 blocks per group, 32768 fragments per group
7472 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840

Writing inode tables: 0/71/72/73/74/75/76/7done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
formatting sda5 succeeded
writing kernel to partition 6
mounting sda 5 succeeded
getting kernel from tftp server
writing kernel to partition 6
3989+1 records in
3989+1 records out
2042704 bytes (1.9MB) copied, 0.260703 seconds, 7.5MB/s
writing kernel to partition 6 succeeded
Getting firmware image from tftp server
firmware disk image uploaded succesfully\n
format partition 7
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
128520 inodes, 514080 blocks
5140 blocks (1.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
63 block groups
8192 blocks per group, 8192 fragments per group
2040 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

Writing inode tables: 0/63 1/63 2/63 3/63 4/63 5/63 6/63 7/63 8/63 9/6310/6311/6312/6313/6314/6315/6316/6317/6318/6319/6320/6321/6322/6323/6324/6325/6326/6327/6328/6329/6330/6331/6332/6333/6334/6335/6336/6337/6338/6339/6340/6341/6342/6343/6344/6345/6346/6347/6348/6349/6350/6351/6352/6353/6354/6355/6356/6357/6358/6359/6360/6361/6362/63done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
formatting sda7 succeeded
mounting partition succeeded
extracting firmware base files
./
./.mpd
./clunc/
./clunc/clunc
./clunc/clunc-org
./clunc/clunc-open
./.ssh
./direct-usb
./var/
./share/
./sys/
./sbin/
[... shortened ...]
./lib/modules/3.14.2/rpcsec_gss_krb5.ko
correcting firmware image for 5big1 succeeded\n
write default database to partition 5
uploading default database on partition 5 succeeded
extraction and installing of the default database on partition 5 succeeded
format partition 8 shared folder partition
formating partition 8 succeeded
create shared folder public on partition 8
Installation completed

Output of fdisk -l:

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 9 72 514080 83 Linux
/dev/sda2 73 136 514080 83 Linux
/dev/sda3 137 200 514080 82 Linux swap
/dev/sda4 201 60800 486769500 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 60800 485098740 83 Linux

Any suggestion?

in which slot is the system disk installed, ssen from the back. It should be in the most lefthand side slot

Yes, the only plugged hard disk is the one in slot 1, that is the leftmost one.

Hi

So we go to check if the firmware is really loaded on nas booting.

Stop your nas and start fvdw-sl console.
Select as action "load the standalone kernel...". which allow you to get a telnet console
When connected with the telnet client that pops up when the standalone kernel is loaded and started successfully , give the following commands on the command line

Code: Select all

mkdir sda7
mount /dev/sda7 /sda7
cat /sda7/boot.log

Done. The file is there:

start boot log
is a physical machine
detect and set platform
5big1
5big1
UIMAGE-3142-5BIG1-33
Current kernel: 3.14.2 #33 Sun Nov 15 23:37:25 CET 2020
device 5big1
family 5big1
Arm: found valid system disk sda
system disk = sda
mount dev/pts
update dev nodes
booting using root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
start buttons control daemon
device = 5big1
source = buttons-5big1
buttons-5big1 version 1 daemon started
parent proces pid = 625 parent proces stop
initializing date
Mon Jan 1 12:00:00 UTC 2018
configuration partition is rightly mounted
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
configure loopback network interface
setting reboot and standby
5big1
rebootd-isp1
5big1
standbyd-isp1
start fan
starting php based setup routines step 1
* Initialize the volatile db file... [ OK ]
* Starting udevd... [ OK ]
* Finishing restore RAID devices... [ OK ]
* Found database configuration file... [ OK ]
* Updating Disks database... [ OK ]
* Starting mount of volumes...
- Mounting volume Vol-A: [ OK ]
* Finishing mount of volumes... [ OK ]
* Generating Hosts File... [ OK ]
* Configuring System Hostname... [ OK ]
* Configuring LAN interface... [ OK ]
* Initializing Timezone... [ OK ]
* Starting web server... [ OK ]
* Starting mount of internal USB ...
* Finishing mount internal USB ... [ OK ]
* Configuring Disks... [ OK ]
* Configuring Samba... [ OK ]
* Configuring System Users...
Root password: use default password
Set users, linux and samba accounts [ OK ]
* Starting Fvdw-sl Discovery Daemon... [ OK ]
start rpcbind service
starting php based setup routines step 2
* Starting dropbear... [ OK ]
* Kill temporary dropbear... [ OK ]
starting php based setup routines step 3
* Starting daemon update Hosts File... [ OK ]
* Starting mount of remote shares...
* Finishing mount shares... [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
This is fvdw-sl version: fvdw-sl 18.3
built on: February 20 2024

LAN IP address: (DHCP)

Port configuration:

LAN -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files away from ram disk to prevent hanging samba server

It looks fine to me... :scratch

Indeed it seems your installation is right (Fw not corrupted) and the issue may be on the iface setup side.

The current setting is : nas gets its ip from a dhcp service. So do you have enable it on your router ?

Argh! I'm an idiot... The router is directly connected to my PC and was setup (previous configuration) to be on 192.168.0.3...

Can I set it for using a fixed IP? Otherwise I'll connect to a router to provide a DHCP server.

Currently you can not set a static IP on the NAS.

First you have to enable an DHCP service on your LAN which will allow you to login in the firmware web interface.

Then from the LAN setup, you can set a static IP on the nas (DNS/mask...) according to your subnet. After you can stop the dhcp service

Ok, I've started a DHCP server on my Windows machine (https://www.dhcpserver.de) and it worked like a charm. Donation sent!

Now I'll abuse your patience some more: I'm trying to access the Samba share which was created by default. I tried to use "Map network drive" to the resource, but the response is "You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack. [...]"
Does fvdw-sl support SMB2 or better SMB3? This would be my primary method for connecting to the NAS.

Second problem. I set up SSH, but my client (Bitvise SSH Client) reports:
14:18:43.372 The SSH connection has terminated with error. Reason: Error class: LocalSshDisconn, code: KeyExchangeFailed, message: FlowSshTransport: no mutually supported inbound MAC algorithm. Local list: hmac-sha2-256,hmac-sha2-512. Remote list: hmac-sha1-96,hmac-sha1,hmac-md5.
I enabled hmac-sha1 and the connection went through. Is it possible to update the ssh methods? (not urgent!)

:thumbup

It is fvdw which handles donation and will add you in the donators group

This allows you to install the samba 4 package with support smb2 and smb3 protocols

About hashing mechanic we do not plan to update the supported list in a short term on ssh server which is a tiny app (dropbear)