367 replies to this topic

[betacentauri]

Thanks!!

But there is a second rootfs. Which one is the correct one? And why are there 2 rootfs devices???
(the "rootfs (redundant)" is not the problem, because the name differs).

[Pedro_Newbie]

Sorry, I don't know, I presume the first one is the correct one

[betacentauri]

This is the second box with 2 rootfs I see. I didn't wanted to add a box recognition to my tool. But I fear I need to, if these boxes should be able to use it. Currently I only look at the mtd device names.

@all: Does someone know why there are 2 rootfs devices? Is one for recovery or something like that?

[rtzhjgg0]

But did you test it from within the plugin with the blue restore button?

So, I'm back again
Yes, I testet now to flash with FullBackup but after auto-rebooting the box is not bootable and have to be flashed again over USB-stick.

Attached Files

•  automaticfullbackup26_pli4duo2_C.jpg   26.79KB   51 downloads
•  automaticfullbackup26_pli4duo2_D.jpg   35.35KB   50 downloads

[betacentauri]

Thanks for the test even when it didn't work.

Edited by betacentauri, 13 August 2013 - 19:25.

[pieterg]

@all: Does someone know why there are 2 rootfs devices? Is one for recovery or something like that?

two? I count three...

And what strikes me as odd is the 1f000 erasesize of the last partition. That's not a valid nand blocksize.

[Pedro_Newbie]

The solo2 has a similar structure

 

root@vusolo2:~# cat /proc/mtd             
dev:    size   erasesize  name            
mtd0: 0e100000 00020000 "rootfs"          
mtd1: 0e100000 00020000 "rootfs(redundant)"
mtd2: 00700000 00020000 "kernel"          
mtd3: 00100000 00020000 "mac"             
mtd4: 0d694000 0001f000 "rootfs"          
root@vusolo2:~#                          

Edited by Pedro_Newbie, 13 August 2013 - 20:28.

[betacentauri]

Yes, 3. But mtd0 and mtd1 are the same:

mtd0: 3d900000 00020000 "rootfs"
mtd1: 3d900000 00020000 "rootfs(redundant)"

And they have different names. So for me it's ok. If you say, that 1f000 is no valid blocksize then this helps me a lot. Then I can use this for recognitition (even when it's not really nice).

[betacentauri]

The solo2 has a similar structure

 

root@vusolo2:~# cat /proc/mtd             
dev:    size   erasesize  name            
mtd0: 0e100000 00020000 "rootfs"          
mtd1: 0e100000 00020000 "rootfs(redundant)"
mtd2: 00700000 00020000 "kernel"          
mtd3: 00100000 00020000 "mac"             
mtd4: 0d694000 0001f000 "rootfs"          
root@vusolo2:~#                          

 

Strange. A user has reported that my tool works on a solo2. And then here the user reported that it don't work on a duo2. But the layout looks quite the same. So when I see this, I would say that it should work on both or on none of them...

[Pedro_Newbie]

I did test it on the Solo2 and the image flashed just fine and rebooted also automatic.

Other users also tested your tool on a solo2 a couple of weeks ago and that also went well

[Pedro_Newbie]

Could this something have to do with this: http://code.vuplus.c...c039f621d1b0361

 

[betacentauri]

Yes, maybe. Thanks for the link!

The big question is now whether the patched version also works for the other boxes...

[pieterg]

Yes, 3. But mtd0 and mtd1 are the same:

mtd0: 3d900000 00020000 "rootfs"
mtd1: 3d900000 00020000 "rootfs(redundant)"

Not necessarily, proc mtd does not show the partition offsets.

[Pedro_Newbie]

Here is some info about the various mtd from the solo2, maybe this can be of any use?

mtd0
Name:                           rootfs
Type:                           nand
Eraseblock size:                131072 bytes, 128.0 KiB
Amount of eraseblocks:          1800 (235929600 bytes, 225.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size:                  2048 bytes
OOB size:                       64 bytes
Character device major/minor:   90:0
Bad blocks are allowed:         true
Device is writable:             true
Default UBI VID header offset:  2048
Default UBI data offset:        4096
Default UBI LEB size:           126976 bytes, 124.0 KiB
Maximum UBI volumes count:      128
 
mtd1
Name:                           rootfs(redundant)
Type:                           nand
Eraseblock size:                131072 bytes, 128.0 KiB
Amount of eraseblocks:          1800 (235929600 bytes, 225.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size:                  2048 bytes
OOB size:                       64 bytes
Character device major/minor:   90:2
Bad blocks are allowed:         true
Device is writable:             true
Default UBI VID header offset:  2048
Default UBI data offset:        4096
Default UBI LEB size:           126976 bytes, 124.0 KiB
Maximum UBI volumes count:      128
 
mtd2
Name:                           kernel
Type:                           nand
Eraseblock size:                131072 bytes, 128.0 KiB
Amount of eraseblocks:          56 (7340032 bytes, 7.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size:                  2048 bytes
OOB size:                       64 bytes
Character device major/minor:   90:4
Bad blocks are allowed:         true
Device is writable:             true
Default UBI VID header offset:  2048
Default UBI data offset:        4096
Default UBI LEB size:           126976 bytes, 124.0 KiB
Maximum UBI volumes count:      128
 
mtd3
Name:                           mac
Type:                           nand
Eraseblock size:                131072 bytes, 128.0 KiB
Amount of eraseblocks:          8 (1048576 bytes, 1024.0 KiB)
Minimum input/output unit size: 2048 bytes
Sub-page size:                  2048 bytes
OOB size:                       64 bytes
Character device major/minor:   90:6
Bad blocks are allowed:         true
Device is writable:             true
Default UBI VID header offset:  2048
Default UBI data offset:        4096
Default UBI LEB size:           126976 bytes, 124.0 KiB
Maximum UBI volumes count:      128
 
mtd4
Name:                           rootfs
Type:                           ubi
Eraseblock size:                126976 bytes, 124.0 KiB
Amount of eraseblocks:          1772 (225001472 bytes, 214.6 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size:                  2048 bytes
Character device major/minor:   90:8
Bad blocks are allowed:         false
Device is writable:             true
Default UBI VID header offset:  2048
Default UBI data offset:        4096
Default UBI LEB size:           122880 bytes, 120.0 KiB
Maximum UBI volumes count:      128

[betacentauri]

Yes, 3. But mtd0 and mtd1 are the same:

mtd0: 3d900000 00020000 "rootfs"
mtd1: 3d900000 00020000 "rootfs(redundant)"

Not necessarily, proc mtd does not show the partition offsets.

Yes, you're right. Can I find the partition offsets somewhere? In pedro_newbies output I also can't see them.

[pieterg]

The dmesg output (right after booting) will show all mtd partitions (including offsets)

[betacentauri]

@pieterg: Thanks!

@pedro_newbie: Sorry to ask you again, but I have no solo2 or duo2. Can you please post dmesg output or send it to me? Thanks!!

[Dimitrij]

ver. 2.7

-small bug fix

[Dimitrij]

ver. 2.8

-OFG binary updated to version 1.1

[Dimitrij]

nere