Hi Craig,
I managed to destroy ramdisk.gz and zImage during my fooling around, and I
think you can combine several bits of information to remake your flash. What
follows is not exactly what I did, as I had only put bad images in my
ramdisk.gz and zImage. But, I think it's what you need to do.
First is the "fis list" output from my machine. Verify that the partitions on
your machine match these addresses and lengths. If they don't, STOP.
Name FLASH addr Mem addr Length Entry point
RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000
RedBoot config 0xF1FC0000 0xF1FC0000 0x00001000 0x00000000
FIS directory 0xF1FE0000 0xF1FE0000 0x00020000 0x00000000
rammode 0xF0060000 0x00200000 0x00040000 0x00200000
log 0xF0040000 0xF0040000 0x00020000 0x00000000
naskey 0xF00A0000 0xF00A0000 0x00020000 0x01008000
zImage 0xF00C0000 0x01008000 0x00200000 0x01008000
ramdisk.gz 0xF02C0000 0x01800000 0x00400000 0x01800000
vendor 0xF06C0000 0xF06C0000 0x01880000 0x01800000
wmdata 0xF1F40000 0xF1F40000 0x00080000 0x01800000
Next is the info that JFS provided: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"
Use the following as a format for what to do. Do Not overwrite the partitions
you still have. I don't know what the consequences would be. Just do this for
the ones you're missing.
For example, the ramdisk.gz partition: ("ramdisk.gz 0xF02C0000
0x01800000 0x00400000 0x01800000")
After doing all the control-C and ip-address and all the rest to get you to
where you can load the files from your PC do the following. Note that it
assumes you're using a webserver on your PC. "-m http" could be "-m xmodem" or
whatever is appropriate for you.
load -v -r -b 0x01800000 -m http mtd5
fis create -b 0x01800000 -l 0x00400000 -e 0x01800000 -r 0x01800000 -f
0xf02c0000 ramdisk.gzfis list
Make sure that the partition saved has gone to the right place in flash for the
right length and is named correctly as I have listed above.
What it did. The "load" command put mtd5 into memory at address 0x01800000.
The "fis create..." command put the image in memory at location 0x01800000 for
length 0x00400000 and named it ramdisk.gz. You would change the locations and
lengths as appropriate from the "fis list" output from my machine, above.
You can find the syntax for the fis commands at
"www.ecoscentric.com/ecospro/doc/html/ref/flash-image-system.html"
You can find the syntax for the redboot commands at
"www.ecos.sourceware.org/docs-2.0/ref/common-commands.html".
Disclaimer: I have no relationship with sourceware or ecos or any of that. I
just found them during a search.
If you run into problems, don't be afraid of contacting me off list.
Bob
From: craig guest <[email protected]>
To: [email protected]
Sent: Wednesday, November 11, 2015 3:13 PM
Subject: Re: SS4000E install problem
Hi All
Sorry if I'm seen as hijacking this thread but haven't see this much activity
on an ss4000e in a long time. Mine has been on a shelf for a long time. I
performed an fis init -f on it and have lost all my partitions except for
Redboot Redboot configfis directory
I have a backup copy of all the partitions but am unsure as to how to restore
them. They are named block1 block2 .... I have been able to load debian to it
and perform an install but it fails at saving to flash I am assuming this is
because the partitions are missing to flash to. Can somebody please help me
either restore the partitions or restore back to factory so I can try again. I
would really appreciate some help
Thanx
Craig
On Wed, Nov 11, 2015 at 1:54 PM, JF Straeten <[email protected]> wrote:
Hi Bob,
On Wed, Nov 11, 2015 at 06:28:07PM +0000, Bob Stewart wrote:
> It's not a matter of wanting to reinstall. It's a matter of wanting
> to know what's wrong. I tried all three of the wheezy images and I
> was unable to do an install with it. It gets to some point, can't
> remember the verbiage, and then it doesn't go any farther. It does
> consume input at that point, and clears the screen about every
> second. But it doesn't actually do an install.
Ah yes, it's to understand. Strange, indeed...
> Can you tell me if your fan ever shuts off?
Never completely, I think ( but frankly I ve'never investigated
either : I don't hear them unless the machine is at load or the temp
very higt outside and I was far enough for my needs).
> If I understand this correctly, your fan should continue to run at
> increased speed until the temp reaches 20C.
Are the values real temp or just in the range proposed by the
hardware, regardless or real temp ? (I'm not sure...)
> Mine won't run at that temp unless the case is off. And my fan
> doesn't run at a reduced speed as far as I can tell. It's either
> fully on or fully off.
I will try to make more attention at this... I think it's a graduation
in the running, but not sure either...
The only thing I remember fort sure is that without fancontrol at all,
the fan are fully on, and the noise become a real nuisance. But I'm
happy with fancontrol configured like it is.
A+
--
JFS.
