Dashboard opens with blank only

[Jocko]

Hi

Surely itype is sensitive about the carriage return code. It is not the same between windows and linux. So if you create this file on a windows laptop and upload it on your nas. It may fail to read it.

So the best way is to create it directly on the nas, so

Code: Select all

echo -e "#!/sbin/itype\ndaemon telnetd {\nneed = virtual/net;\nexec daemon = /usr/sbin/telnetd -l /bin/sh ;\n forks;\ndaemon_stops_badly;\n}" >/md8/etc/initng/telnetd.i

if you run

Code: Select all

cat /md8/etc/initng/telnetd.i

you should get the expected output

Code: Select all

#!/sbin/itype
daemon telnetd {
   need = virtual/net;
   exec daemon = /usr/sbin/telnetd -l /bin/sh ;
   forks;
   daemon_stops_badly;
}

(keep exactly the string and the double quote)

[fariaslcfs]

I used the linux editor 'vi'. So, the output is:

Code: Select all

root@(fvdw-kirkwood):/md8/etc/initng/runlevel # cat /md8/etc/initng/telnetd.i
#!/sbin/itype
daemon telnetd {
        need = virtual/net;
        exec daemon = /usr/sbin/telnetd -l /bin/sh ;
        forks;
        daemon_stops_badly;
}


Now, shall I reboot Lacie, open a telnet session, and run items #3 and #4 of the previous listing?

[fvdw]

Just executed items #7 and #8.
What shall I do now? Just boot Lacie normally and then try a telnet session?

Yes if your actiins were succesful you should boot the 5big2 normally and try to connect to it with a telnet client

[fvdw]

You could use the telnet client of the fvdw-sl console but use the ip address your router has assigned to it.

[fariaslcfs]

Connection to nnn.nnn.nnn.nnn/telnet refused...

I see that default.runlevel is a list with a lot of tasks.
'telnetd' line comes at the end.
If one of the previous tasks fails to run, it could prevent 'telnetd' to work, isn't it?

Code: Select all

initial
dbus
udev
hald
clock
dhcdbd
logrotate
syslogd
klogd
swap
modules
mountfs
mountuserfs
raid
usb
hostname
NetworkManager
http
getty/1
#sshd
cron
unicorn
thumbd
telnetd
~
~
~
~
~
~
- default.runlevel 1/24 4%


P.S.: I found that NetworkManager file is empty. Would that has something to do with Lacie dashboard shown in brower as a blank frame?

[fvdw]

If you get connection refused it means that telnet is running but it doesn't accept connections. Also it means lacie firmware is running. To get telnet accepting connections is a setup issue, mayby mijzelf can help here. Later today I will look in my archive to see if I can find some info about this. I had a nas running lacie firmware and I struggled to get telnet acces. And from memory I don't remember how I solved that

[fvdw]

Did not find useful info for enabling telnet. But we could also try to to get ssh server.

To enable ssh access and reset the password for user root to the same as the default password of the user admin (which you know) proceed as follow

Unpack the files in the zip archive attached and put the files in the tftp folder of the fvdw-sl console
Load and start the standalone kernel, assemble the sdx8 raid array and mount it (I assume you use /dev/md1 respectively /md1 as mount point

replace existing files on md1 (sdx8 arrray) by the ones in the attached archive
Upload them using tftp command in standalone kernel, cd to the corresponding folder first to make you life easy

the file "default.runlevel" goes into folder
/md1/etc/initng/runlevel/

Code: Select all

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


replace ip-pc by actual ip address of your pc, you can check before uploading the new file if in the folder were you are a file is present with sam name using ls -al command

the file "shadow" goes into folder
/md1/etc

Code: Select all

cd /md1/etc
tftp -l shadow -r shadow -g ip-pc
cd /


the file "user.py" goes into folder
/md1/usr/lib/python2.6/site-packages/unicorn/authentication/local

Code: Select all

cd /md1/usr/lib/python2.6/site-packages/unicorn/authentication/local
tftp -l user.py -r user.py -g ip-pc
cd /


Changing this last file, user.py is only required to prevent that when you change a password of a user using the dashboard that the password for user root is reset to original value instead of the the default password for user admin
If you do not set user passwords there is no need to change this file.

Reboot and you should be able to connect via ssh with user root and as password the default password of user admin

[fariaslcfs]

To enable ssh access and reset the password for user root to the same as the default password of the user admin (which you know) proceed as follow

Actually, I know the password of my Lacie account (not "Admin") which has administrative rights.
However, I am not sure if I know the password of the "Admin" account itself.
Could I connect with log name and password, or it will always be "Admin" only and its respective password?

Unpack the files in the zip archive attached and put the files in the tftp folder of the fvdw-sl console
Load and start the standalone kernel, assemble the sdx8 raid array and mount it (I assume you use /dev/md1 respectively /md1 as mount point

I used /md8 after sd[abcde]8 array. It must be /md1 or doesn't matter?

Reboot and you should be able to connect via ssh with user root and as password the default password of user admin

The connection is made with the same telnet window?

[fariaslcfs]

After doing @fvdw instructions , booting Lacie and scanning the Lacie IP, one found: "HTTPs, Tunnel is OpenSSL SSLv3: lighttpd 1.4.22".
Opening Lacie IP in a browser with HTTPS resulted in the same useless blank dashboard frame.

[fvdw]

You can use md8 as name instead of md1
Of course you need to adapt the tftp commands accordingly.

The connection is made with the same telnet window?

No you must use a ssh client like for instance putty. Default ssh port is 22. If you connect it will ask for user and password, use as user root and password you used to login in webinterface. If that fails try other combinations