Save original firmware for later restoration

[fvdw]

but in that case it should also happens when he uses only WDC25 in slot 1 and nothing in slot 2.
In this case he got 15-3 according earlier posts
when adding a second disk in slot 2 he got 15-3. It doesn't make sense

ps think you forgot a file in the above post (part 3)

[Jocko]

No I built the compressed file with only two files.

Note: I read also that WDC25 was formatted a long time ago (it's why it doesn't have a standard partitions table) and maybe there is also an old firmware image on its partition7

[matzi]

right now I am doing a backup of my files to the second disc. That will take a day. Transmission speed is 11.8MB/sec, is that OK?

After that we can go on finding the problem. Isn't there an easier way to find out what is on the different firmware partitions, like looking for significant files on it?

The WDC25 originally was setup end of 2012 for nwsp2.

[Jocko]

Yes we could add some command in rcS to write the list of device node in a file on (sda7) just before trying to mount sda1.

Then we can compare the two outputs before chroot and after and see if there are change.

If it's the issue then the outputs must be different as on sda1 the rcS script run another udevstarts...

The WDC25 originally was setup end of 2012 for nwsp2.

So it must have version 13.0 or 14.0 on the partition 7

[matzi]

OK this my rcS.

Please tell me what to midify?

[Jocko]

Matzi, where do you get this file because it is the version for 15-x.

If you get it from /etc/init.d this is normal but if you get this from sda7 (and so you have mounted this partition) that means that the firmware version on sda7 is right and my explanation is wrong. :fuming

So get rcS from sda7

Code: Select all

mkdir /tmp/sda7
mount /dev/sda7 /tmp/sda7

and then rcS is in the folder /tmp/sda7/etc/init.d

[matzi]

That has been the one from the running partition. The other is here:

[Jocko]

Attached the modified files

Indeed it is a very old version fvdwsl 11.0 with no udevstart before mounting sda1 or sda2.

So it creates a file list.log. To get access on it after rebooting, you need to mount the partition sda7

Code: Select all

mount /dev/sda7 /sda7-tmp

and the file is here

Code: Select all

/sda7-tmp/list.log

So be careful when you go to import the new rcS file. check if the file has still the linux format and do (sda7-tmp is already existing)

Code: Select all

mount /dev/sda7 /sda7-tmp
cp /share/1000/fvdw/rcS /sda7-tmp/etc/init.d                (I assume that new rcS is present in the share fvdw)
chmod 755 /sda7-tmp/etc/init.d/rcS

[matzi]

Hi Jocko,

the backup went ready so I could do the rcS test.
I could not access the disc with the mdified rcS and there is no list.log file!

All I found is this very short boot.log

start boot log
Sun Jun 8 23:24:38 GMT+1 2014
booting using sda1 file system...
rcS finished

The mentioned time stamp does not correspond to the files time stamp and both are not of today. I guess it did not process the modofied rcS.

[matzi]

If you think the issue is linked with an old fvdw version on sda7, why not just update it and check the results. But I would need an image for that. And we need to check if the image size suits to my sda7 size.