Dashboard opens with blank only

[fvdw]

Not good news. I suggest you try what mijzelf suggested. To see if you can get lacie firmware running and access it via ssh and see if lacie kernel can repair it.

[fariaslcfs]

I collected @Mijzelf instructions:

1. assemble & mount the raid array formed by /dev/sd[abcde]8;
2. add a start script for the already installed telnet daemon.

However, what would be the exact commands to do #1? An md directory must be created? A swap is necessary?
And for #2, I found that using the command 'vi' opens an editor, but @Mijzelf mentions to add the file telnetd.i to <mountpoint-of-array>/etc/initng/. This mountpoint is the path available when starting the telnet session ('root@(fvdw-kirkwood):/ #') or there are additional commands to reach it? Furthermore, I saw that the subdir 'initng' does not exist, so it must be created?

[fvdw]

You must assemble the array just like you did the others.
After mounting that array you should found the /etc/initg file in the mountpoint (mijzelf made a type error he mentioned intig while it must be initg)

[fariaslcfs]

You must assemble the array just like you did the others.
After mounting that array you should found the /etc/initg file in the mountpoint (mijzelf made a type error he mentioned intig while it must be initg)

So, the assembling would fit in the action #5 of the previous list of commands?

[fvdw]

Yes but don't create swap just assembe and mount

[fariaslcfs]

Just to make the things fully clear - assuming that the server was turned off and on - is it correct the following sequence of commands, or one may discard some of them?

1. using standalone kernel version 3.9.5; run the fvdw-sl-programs to upload mini glibc and tools;
   

   Code: Select all

   cd /
tftp -r fvdw-sl-programs.sh -l fvdw-sl-programs.sh -g ip-pc
chmod 755 fvdw-sl-programs.sh
/fvdw-sl-programs.sh

2. load and use udevstart.sh;
   

   Code: Select all

   cd /sbin
tftp -r udevstart.sh -l udevstart.sh -g ip-pc
chmod 755 udevstart.sh
udevstart.sh
ls -l /dev/sd*

3. assemble md4;
   

   Code: Select all

   gdisk -l /dev/sdd
mdadm --assemble --run /dev/md4 /dev/sd[abcde]2
cat /proc/mdstat

4. try to mount md4;
   

   Code: Select all

   cd /
mkdir /md4
/usr/sbin/mount -t xfs /dev/md4 /md4

5. assemble the raid array md8:
   

   Code: Select all

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

6. try to mound md8;
   

   Code: Select all

   mkdir /md8
/usr/sbin/mount -t xfs /dev/md8 /md8

7. Add a file telnetd.i to /md8/etc/initg/ with the content:
   

   Code: Select all

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

8. add a line 'telnetd' to /md8/etc/initg/runlevel/default.runlevel:
   

   Code: Select all

   echo telnetd >> /md8/etc/initg/runlevel/default.runlevel

[Jocko]

Hi
So now you want to know if you can mount md4 after running xfs_repair

Two remarks :
- at step2: gdisk command is useless (with ls -l /dev/sd* We already have information about the dev nodes)
- step 6 and higher are currently useless

[fariaslcfs]

Hi @Jocko

Hi
So now you want to know if you can mount md4 after running xfs_repair

Actually, the xfs_repair on md4 was unsuccessful.
@fvdw suggested to try @mijzelf recommendation, which are #7 and #8 of the previous list.

[fvdw]

Hi @Jocko

Hi
So now you want to know if you can mount md4 after running xfs_repair

Actually, the xfs_repair on md4 was unsuccessful.
@fvdw suggested to try @mijzelf recommendation, which are #7 and #8 of the previous list.

Correct

[Jocko]

Sorry I did not notice your previous message.

Please to note I do not know what login must be used with the telnet server of Lacie firmware.