Please Help, 5Big Network 2 upgrade attempt gone wrong

[hvymetal86]

I've gotten u-boot to work, and the kernel to load (successfully I think, the window closes automatically), but then telnet fails and never gives the login prompt.

(Images were too large and the forum disallowed them in the IMG tags)
U-Boot:
https://drive.google.com/uc?export=view&id=0B5x7lw1_KgjVb1hFUU9kNFRWZDg

Kernel Load:
https://drive.google.com/uc?export=view&id=0B5x7lw1_KgjVNUYzNmFzMG8ybzQ

Telnet Failure:
https://drive.google.com/uc?export=view&id=0B5x7lw1_KgjVQUNoNWNVb09aWGs

[Jocko]

Can you try again by deactivated your firewall and the antivirus

[hvymetal86]

Tried that but still got the same thing:
https://drive.google.com/uc?export=view&id=0B5x7lw1_KgjVMmY5Y0xQaWl2eFE

And then I figured it out as I was typing this post. I was using the LAN 2 port on the 5Big Network 2. Switching it to the LAN 1 port got telnet to connect and login!

[hvymetal86]

Ok, got a good bit farther.

• Deleted existing partitions with gdisk
• Created new partitions with gdisk and wrote to the drive
• Formatted the partitions 7,8, and 9
• TFTP'd the mkfs.xfs file over

But then I ran into an error formatting partition 2 with it:

Code: Select all

root@fvdw-sta-kirkwood:/ # tftp -l /sbin/mkfs.xfs -r mkfs.xfs -g 192.168.1.105
mkfs.xfs             100% |****************************************************************|   337k  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # chmod 755 /sbin/mkfs.xfs
root@fvdw-sta-kirkwood:/ # mkfs.xfs /dev/sda2
mkfs.xfs: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
root@fvdw-sta-kirkwood:/ # /sbin/mkfs.xfs /dev/sda2
/sbin/mkfs.xfs: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
root@fvdw-sta-kirkwood:/ # ls -lha /sbin/mkfs.xfs
-rwxr-xr-x    1 root     root      337.8K May 19 14:48 /sbin/mkfs.xfs


I know the tftp of the file was successful and that my chmod command worked (see above). From the other thread vmosa had an issue with mkfs.xfs as well but it's not the same as this error and I tried both the short and long paths to it (see above, long path was what worked in the other thread). I also tried using the find command to locate the missing file:

Code: Select all

root@fvdw-sta-kirkwood:/ # find librt.so.1
find: librt.so.1: No such file or directory


Thanks for the help so far, I'm very grateful for it and the progress!

[Jocko]

:scratch

As it seems that your NAS succeeded to upload the kernel, the telnet server should be running.

Did you try several times to upload the kernel standalone version (so do again fully the sequence: stop the nas,....).

if you have several enabled network interface on your laptop, keep only one and I advise you not to use wireless connection.

[Jocko]

So we post our message in the same time.

Indeed, the standalone kernel handle only one LAN port.

for mkfs.xfs you need to wait fvdw.

[Jocko]

!	Important, before destroying/making partition table or formatting a partition, you must check that the device nodes in /dev are updated. Indeed Lacie does not use standard settings for its nodes

so read the content of /proc/partitions which contains the right major ninor value for each partition and check the output of

Code: Select all

ls -l /dev/sd[abcde]

To update the node you must upload udevstart herehttp://plugout.net/viewtopic.php?f=7&t=1271&p=18801#p18801

set run permissions and run it. of course you need to repeat it at each boot.

[hvymetal86]

I think I fixed/figured out the mkfs.xfs issue. It was missing two components from it's shared libraries and I got them from the glibc-mini-mkfs.xfs-25feb14.tar file in the console's tftp directory. I did the following and then got the command to work at the end:

Code: Select all

root@fvdw-sta-kirkwood:/ # tftp -l /glibc-mini-mkfs.xfs-25feb14.tar -r glibc-mini-mkfs.xfs-25feb14.tar -g 192.168
.1.105
glibc-mini-mkfs.xfs- 100% |****************************************************************|  2519k  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # mkdir glibc-mini-mkfs.xfs-25feb14
root@fvdw-sta-kirkwood:/ # tar -C /glibc-mini-mkfs.xfs-25feb14 -xvf glibc-mini-mkfs.xfs-25feb14.tar
./
./usr/
./usr/lib/
./usr/lib/libuuid.so
./usr/lib/libuuid.so.1.3.0
./usr/lib/libgcc_s.so.1
./usr/lib/libuuid.so.1
./bin/
./sbin/
./sbin/mkfs.xfs
./lib/
./lib/libutil.so.1
./lib/libc-2.17.so
./lib/librt.so.1
./lib/librt-2.17.so
./lib/libc.so.6
./lib/libm-2.17.so
./lib/libpthread.so.0
./lib/ld-linux.so.3
./lib/ld-2.17.so
./lib/libutil-2.17.so
./lib/libpthread-2.17.so
./lib/libm.so.6
root@fvdw-sta-kirkwood:/ # cp /glibc-mini-mkfs.xfs-25feb14/lib/librt.so.1 /lib/librt.so.1
root@fvdw-sta-kirkwood:/ # /sbin/mkfs.xfs /dev/sda2
/sbin/mkfs.xfs: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory
root@fvdw-sta-kirkwood:/ # cp /glibc-mini-mkfs.xfs-25feb14/lib/libpthread.so.0 /lib/libpthread.so.0
root@fvdw-sta-kirkwood:/ # /sbin/mkfs.xfs /dev/sda2
meta-data=/dev/sda2              isize=256    agcount=4, agsize=244055989 blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=976223953, imaxpct=5
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal log           bsize=4096   blocks=32768, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=0
realtime =none                   extsz=4096   blocks=0, rtextents=0

I then got rid of the .tar and directory I had unpacked it into:

Code: Select all

rm /glibc-mini-mkfs.xfs-25feb14.tar
rm -rf /glibc-mini-mkfs.xfs-25feb14

I'm going to continue with fvdw's instructions in the other thread from right after the "format partiton 2; Code: mkfs.xfs /dev/sda2" step.

[Jocko]

The right command is just

Code: Select all

tar -C / -xvf glibc-mini-mkfs.xfs-25feb14.tar

And keep in mind that if you don't update the dev nodes :
sda is the middle disk
sdc is the first left disk
sdd is the first right disk

So you have sdc - sdb - sda -sde -sdd (from left to right)

[hvymetal86]

Ok so I successfully finished the instructions in this post: viewtopic.php?f=26&t=1402#p9338

The NAS rebooted when I told it to but it has not come online or gotten an IP as I can see from my router. Current status is the single drive's light is solid blue and the front button/light is blinking blue changing every 1 second. This seems to be the same thing vmosa experienced (but he couldn't format /sda2 initially). I'm going to try the following post next: viewtopic.php?f=26&t=1402&start=20#p9393