No Shares management from Dashboard

[Jocko]

Ok,

Currently, I suggest you change nothing before checking some files version.

So the first steps are :
* to get an access via this app.
Please to read this topic Fvdw-sl console telnet does not connect ( standalone kernel)
In your case you need also to select the standalone kernel image: UIMAGE-3142-KIRKWOOD-158-standalone (and nothing else)

And of course, you have to follow step by step the action "Load a standalone kernel". Please to read carefully the related help.
* assemble the raid devices

and later I will give you some others instructions.

(Please to note I won't have free time next days up to Sunday)


---edit---
My post was to fvdw and this post can be read only by him. I think it is better you do not apply directly this trick without some checkings.

[carloph]

Ok, I continue sreading&tudying. I'll do not load anything on NAS up to next week.

Just a question: how to verify that all communications works between fvdw_sl console and NAS (permissions, firewalls, etc.) , without loading anything to NAS ?

Thanks

[Jocko]

Hi Carloph,

Here some details what you need to do after getting a telnet access on your NAS (See my previous post)

- You need to assemble a fs raid :
1/ run the command

Code: Select all

fvdw-sl-programs

This one loads a menu and select the option '4' 'Upload and extract glibc mini and tools'. Then some additionnal tools are uploaded (required to assemble the raid)
2/start the raid

Code: Select all

mdadm --assemble /dev/md1 /dev/sd[abcde]8

3/ mount it

Code: Select all

mkdir /md1
mount /dev/md1 /md1

Note: at each time you reboot the NAS, you need to repeat these steps to get again the raid /dev/md1

- download some original files for checking :

Code: Select all

cd /md1/etc/initng/runlevel
tftp -l default.runlevel -r default.runlevel.org -p ip-pc

(note the flag 'p' and not the flag 'g')
ip-pc is the IP address of your laptop
Then you should have now a file default.runlevel.org in the folder 'tftp' on your laptop

Code: Select all

cd /md1/etc/initng
cp sshd.i sshd.i.org
tftp -l sshd.i -r sshd.i.org -p ip-pc

Then you should have also a new file sshd.i.org in the folder 'tftp' on your laptop

- after getting these files, please to post them on the board

[carloph]

Very great job !!!!!

Just a question, from a non-expert-user: what does it mean, at the first step, "You need to assemble a fs raid" ? It means that the current RAID6 loaded on NAS, will be superseded/lost ?

Thanks

[Jocko]

Lacie firmware uses 5 raids: 4 on its fs and optionally one for the data volume

So currently you have your raid6 only on the partitions sd[a-e]2. The others are raid1 devices.

What I asked is to mount one of them (this one built on partitions sd[a-e]8)

[carloph]

I performed the preliminary trials (without running the NAS), but the WinFirewall installed on my PC, blocked some features of tftpd, dunc-open, etc.

I cannot disable the firewall, but I can move the NAS on a secondary-private LAN (162.168.10.xxx) using a PC where I can disable the win firewall.

Currently the NAS has a static IP; when I'll move it on the secondary-private LAN, I cannot activate any DHCP server. Question: do I have to change (from the LACIE DASHBOARD) the static IP of the NAS before starting the fvdw_sl console in the private LAN?

Thanks

[Jocko]

Hi Carloph

I performed the preliminary trials (without running the NAS), but the WinFirewall installed on my PC, blocked some features of tftpd, dunc-open, etc.

is it your home laptop or not ? if it is your personal laptop you should be able to disable it (or at least to grant rules on the executables used by fvdw-sl console)

Currently the NAS has a static IP; when I'll move it on the secondary-private LAN, I cannot activate any DHCP server. Question: do I have to change (from the LACIE DASHBOARD) the static IP of the NAS before starting the fvdw_sl console in the private LAN?

In fact having a DHCP server is useless with the later version. Now it is the standalone kernel himself which knows what IP it must use. You should only check if the IP xxx.yyy.zzz.251 (and 252) are not already used on your 2d LAN

Note:
WinFirewall has a very bad reputation :shock:

[carloph]

DONE, here are the files

Thanks

Carlo

----------------------------------------------------
CONTENT of default.runlevel.org

Code: Select all

initial
dbus
udev
hald
dhcdbd
logrotate
syslogd
klogd
raid
usb
NetworkManager
http
getty/1
sshd/generate_keys
#sshd
cron
unicorn
thumbd

------------------------------

CONTENT of sshd.i.org

Code: Select all

#!/sbin/itype
# This is a i file, used by initng parsed by install_service

service sshd/generate_keys {
   need = udev;
   env KEYGEN=/usr/bin/ssh-keygen;
   env RSA1_KEY=/etc/ssh/ssh_host_key;
   env RSA_KEY=/etc/ssh/ssh_host_rsa_key;
   env DSA_KEY=/etc/ssh/ssh_host_dsa_key;
   script start = {
      [ ! -s ${RSA1_KEY} ] && \
         ${KEYGEN} -q -t rsa1 -f ${RSA1_KEY} -C '' -N '' 2>&1 >/dev/null
      if [ ! -s ${RSA_KEY} ]
      then
         ${KEYGEN} -q -t rsa -f ${RSA_KEY} -C '' -N '' 2>&1 >/dev/null
         chmod 600 ${RSA_KEY}
         chmod 644 ${RSA_KEY}.pub
      fi
      if [ ! -s ${DSA_KEY} ]
      then
         ${KEYGEN} -q -t dsa -f ${DSA_KEY} -C '' -N '' 2>&1 >/dev/null
         chmod 600 ${DSA_KEY}
         chmod 644 ${DSA_KEY}.pub
      fi
   }
}

daemon sshd {
   need = sshd/generate_keys virtual/net;
   exec daemon = /usr/sbin/sshd;
   pid_file = /var/run/sshd.pid;
   forks;
   daemon_stops_badly;
}

[carloph]

Doubt: if I Shutdown the NAS, when I restart it, do I have to reload the StandaloneKernel from FVDW or now it is loaded by default ?

[Jocko]

Doubt: if I Shutdown the NAS, when I restart it, do I have to reload the StandaloneKernel from FVDW or now it is loaded by default ?

If you restart the nas you need to do all the previous steps (load the standalone kernel; load additional utility tools; assemble the raid and mount it).
Keep in mind that all your actions run on the memory and then are lost when you stop the nas

So according with your last post (please to use the BBcode "code" when you post such outputs, I edited your post), there is no change with your last lacie firmware version and you can use the trick to get a root shell access.

Download root-sshd.zip available in the topic: https://plugout.net/viewtopic.php?f=26&t=1402&p=23486#p23486 and unzip the file in the folder tftp (where you have the '.org' files). You should have two new files : default.runlevel and sshd.i
You need now to upload them to replace the lacie files.

I assume you have a telnet access and the raid1 mounted on the folder /md1
- backup the current lacie files

Code: Select all

cd /md1/etc/initng/runlevel
cp default.runlevel default.runlevel.org
cd /md1/etc/initng
cp sshd.i sshd.i.org


- upload the new files

Code: Select all

cd /md1/etc/initng/runlevel
tftp -l default.runlevel -r default.runlevel -g ip-pc

(Please to note this time you use the flag 'g') ip-pc is still the laptop ip

Code: Select all

cd /md1/etc/initng
tftp -l sshd.i -r sshd.i -g ip-pc

Then you can now restart the nas, do

Code: Select all

reboot -f

Next step is to check if you succeed to get a shell access.

As you use Windows OS, you need to install Putty https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html(use installer package)

To open a ssh session, read this page https://mediatemple.net/community/products/dv/204404604/using-ssh-in-putty-
But:
- replace the default port '22' by '2222'
- do not use the nas name as host name but its static IP (not the ip set with fvdw-sl console)
Credentials are :
- login as: root
- password : the same as you use with the admin account to open the web-interface

That's all