Re: How to save the original zImage and ramdisk.gz of an Intel NAS SS4000-E.
Re,
On Sun, Dec 12, 2010 at 08:16:26PM +0100, H wrote:
> Uploading a new zImage and ramdisk.gz with 'fis load' will erase the
> existing entries. Is there a way to save these first somewhere ?
I think yes.
Do the install without flashing your nas before (it's possible to load
d-i in ram by tftp/http/{z,y}modem, without any flashing).
Then, somewhere near the end of the install, before running
flash-kernel, switch to another console (or exec a shell) and have
access to the flash content through /dev/mtd? device files :
lothar:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "RedBoot"
mtd1: 00020000 00020000 "log"
mtd2: 00040000 00020000 "rammode"
mtd3: 00020000 00020000 "naskey"
mtd4: 00200000 00020000 "zImage"
mtd5: 00400000 00020000 "ramdisk.gz"
mtd6: 01880000 00020000 "vendor"
mtd7: 00080000 00020000 "wmdata"
mtd8: 00001000 00020000 "RedBoot config"
mtd9: 00020000 00020000 "FIS directory"
lothar:~# dd if=/dev/mtd4 of=./test
4096+0 enregistrements lus
4096+0 enregistrements écrits
2097152 octets (2,1 MB) copiés, 2,50811 s, 836 kB/s
lothar:~# file test
test: data
lothar:~# dd if=/dev/mtd5 of=./test1
8192+0 enregistrements lus
8192+0 enregistrements écrits
4194304 octets (4,2 MB) copiés, 4,72633 s, 887 kB/s
lothar:~# file test1
test1: gzip compressed data, from Unix, last modified: Sun Nov 21 04:30:17 2010
lothar:~#
It's basicaly the reverse of what flash-kernel is doing to write the
kernel/initrd permanently, so you should end with zImage and
ramdisk.gz.
N.B. : fis reloading them not tested...
Hih,
--
JFS.
Reply to: