delete jffs2 partition and usb drive problems bug, then uStor00 as default

[ramik]

Since a couple of month I installed the 7170 firmware on my 7140, and it works great. I just noticed that now in Partitions page i see a JFFS2 partition, and i saw that in the latest trunk i used (5990) there is an option to delete the jffs2 partition during update, so i did this, fritz rebooted but the jffs2 partition was still there, BUT:

I was unable to find the usb partition, it vanished. checking the usb drive i found that the fat16 partition that i used as external storage for External packages and options was deleted (first 256 kb of the pen drive were all 0xFF).

Luckily i had a backup of the contents that i needed, so i reformatted the usb drive, put everything back and rebooted the fritz, and now i have a problem:

now it gets mounted as "uStor00" instead of the always used "uStor01", which messed all the options, as swap was defined to go to uStor01, the same for rrd and vnstat persistent folder.

how can i make it mount to uStor01 as before ?? or at least if I know that from now on it will always be uStor00 i will change options accordingly.

 

[RalfFriedl]

The name will be "uStor01" if it is the first partition on a device, "uStor00" if there are no partitions on a device and the file system starts at the beginning of the device.

If you want to use the name "uStor01", create a partition (using all available space) and restore your files to this partition. Or change your config to "uStor00".

 

[gismotro]

You can use the USB-Device by lable. I didn't tested it youst no, but it work. You can find more Infos in an other thread.

 

[olistudent]

The jffs2 partition is created/mounted at every boot. This check box should only delete its contents.

Regards
Oliver

 

[ramik]

About the uStor00, i reformated my usb drive with HP Usb format tool and now it mounts as before, uStor01.

and ok about the jffs2 partition, but what happened to me (usb partition delation) is related to selecting "delete jffs2 partition" or just an unlucky firmware update?

 

[RalfFriedl]

It should be unrelated, unless you can reproduce it.