assuming slot 1 remains defective.
I compiled two kernels for you using a disk map in reversed order.
A standalone kernel UIMAGE-3142-5BIG2-reversed-standalone-186
A kernel to run the firmware UIMAGE-414133-KIRKWOOD-5big2R-3
This means
sda goes now in slot 5 = most righthand slot seen from back, so moved from slot 1 to slot 5
sdb goes in slot 4 (instead of slot 2)
sdc goes now in slot 3 (same as before)
sdd goes now in slot 2 (instead of slot 4)
sde goes now in slot 1 (instead of slot 5) (but will not work as slot 1 is defective so leave empty)
So for these special kernels with reversed disk maps the disks order seen from the back of the nas is as follow
- Code: Select all
name sde sdd sdc sdb sda
slot 1 2 3 4 5
Originally it was the other way around (sda slot 1 sdb slot 2 etc)
put both new kernels in the tftp folder of the fvdw-sl console (unzip the archives)
To install the firmware, put a disk in slot 5 (most righand side slot seen from back of nas), this is now sda
Load the new standalone kernel with reversed diskmap (UIMAGE-3142-5BIG2-reversed-standalone-186) using fvdw-sl console by chosen as action load and start standalone kernel (select the new standalone kernel)
when connected with telnet
give command
- Code: Select all
fvdw-sl-programs
choose install firmware for kirkwood and let install on sda
Let the installer finish the install and after it mention install successful do not close telnet,
we have to put first the new kernel that uses reversed disk map in sda6 as the installer has put the normal kernel in sda. If we don't do that the nas won't load the firmware.
To get the new kernel in sda6 give these commands in the telnet window
(replace in this command ip-of-your nas by the actual ip address of your pc as shown in fvdw-sl console)
- Code: Select all
busybox tftp -r UIMAGE-414133-KIRKWOOD-5big2R-3 -l UIMAGE-414133-KIRKWOOD-5big2R-3 -g ip-of-your-nas
dd if=UIMAGE-414133-KIRKWOOD-5big2R-3 of=/dev/sda
note in the tftp command the option "-l" is a small letter L so not the number 1, the -l means local.
when this kernel writing is completed successful reboot the nas with reboot -f and see if the firmware comes up
You do not have the required permissions to view the files attached to this post.