Welcome! Log In Create A New Profile

Advanced

What version of Rescue am I running?

Posted by jcconnell 
Re: What version of Rescue am I running?
June 06, 2018 04:06PM
bodhi Wrote:
-------------------------------------------------------
> balanga Wrote:
> -------------------------------------------------------
>
> > Is it possible to mount NAND storage?
>
> Yes, if you are running my released kernel, NAND
> UBIS is already initialized (assuming that UBI
> file system is what you have on your NAND mtd),
> you just need to mount it.
>
> Assuming you want to mount mtd3 file system:
>
>
> mkdir -p  /tmp/nand/
> mount -t ubifs /dev/mtdblock3 /tmp/nand/
>
>
>
> If it has not been initialized (if running a
> different kernel other than my release), then you
> need to run ubiattach to bring it up before
> mounting:
>
> ubiattach /dev/ubi_ctrl -m 3
>

To be honest, I'm still very much in the dark about what I have installed, I'm just trying to find my way round it.

I tried the above commands suggested and got:-


mkdir -p  /tmp/nand/
mount -t ubifs /dev/mtdblock3 /tmp/nand/
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock3,
            missing codepage or helper program, or other error


ubiattach /dev/ubi_ctrl -m 3
ubiattach: error: cannot attach mtd3
                 error 19 (No such device)
Re: What version of Rescue am I running?
June 06, 2018 11:10PM
>
> I tried the above commands suggested and got:-
>

The command is an example when you want to mount mtd3.

> ubiattach /dev/ubi_ctrl -m 3
> ubiattach: error: cannot attach mtd3
> error 19 (No such device)

And this means you don't have mtd3.

In all *nix systems (Arch, Debian, BSD,...), when in doubt, get help:

ubiattach --help

Quote

ubiattach version 2.0.0 - a tool to attach MTD device to UBI.

Usage: ubiattach [<UBI control device node file name>]
[-m <MTD device number>] [-d <UBI device number>] [-p <path to device>]
[--mtdn=<MTD device number>] [--devn=<UBI device number>]
[--dev-path=<path to device>]
[--max-beb-per1024=<maximum bad block number per 1024 blocks>]
UBI control device defaults to /dev/ubi_ctrl if not supplied.
Example 1: ubiattach -p /dev/mtd0 - attach /dev/mtd0 to UBI
Example 2: ubiattach -m 0 - attach MTD device 0 (mtd0) to UBI
Example 3: ubiattach -m 0 -d 3 - attach MTD device 0 (mtd0) to UBI
and create UBI device number 3 (ubi3)
Example 4: ubiattach -m 1 -b 25 - attach /dev/mtd1 to UBI and reserve
25*C/1024 eraseblocks for bad block handling, where C is the flash
is total flash chip eraseblocks count, that is flash chip size in
eraseblocks (including bad eraseblocks). E.g., if the flash chip
has 4096 PEBs, 100 will be reserved.

-d, --devn=<number> the number to assign to the newly created UBI device
(assigned automatically if this is not specified)
-p, --dev-path=<path> path to MTD device node to attach
-m, --mtdn=<number> MTD device number to attach (alternative method, e.g
if the character device node does not exist)
-O, --vid-hdr-offset VID header offset (do not specify this unless you really
know what you are doing, the default should be optimal)
-b, --max-beb-per1024 maximum expected bad block number per 1024 eraseblock.
The default value is correct for most NAND devices.
Allowed range is 0-768, 0 means the default kernel value.
-h, --help print help message
-V, --version print program version

To list the mtds

cat /proc/mtd

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 07, 2018 04:41PM
jcconnell Wrote:
-------------------------------------------------------
>
> pacman -Syu uboot-tools
>

After running pacman -Syy a few days ago I'm now unable ti install anything! Everything I try ends up with 'keyring signature ..... is unknown trust'

I've gone round is circle for a couple of hours trying to remove /etc/pacman.d/gnupg and re-install keys but haven't stumbled on the correct solution yet. Wondered if you might have any advice....
Re: What version of Rescue am I running?
June 07, 2018 04:54PM
bodhi Wrote:
-------------------------------------------------------
> To list the mtds
>
>
> cat /proc/mtd
>

dev: size erasesize name
mtd0: 0010000 00020000 "u-boot"
mtd1 0ff00000 00020000 "rootfs"

Still not sure how to mount these...
Re: What version of Rescue am I running?
June 07, 2018 05:15PM
balanga Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > To list the mtds
> >
> >
> > cat /proc/mtd
> >
>
> dev: size erasesize name
> mtd0: 0010000 00020000 "u-boot"
> mtd1 0ff00000 00020000 "rootfs"
>
> Still not sure how to mount these...

Look back the instruction I wrote:

https://forum.doozan.com/read.php?4,58974,61239#msg-61239

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 07, 2018 11:43PM
Try:

mkdir -p  /tmp/nand_rootfs
mount -t ubi0:rootfs /dev/mtdblock1 /tmp/nand_rootfs

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 08, 2018 02:48PM
bodhi Wrote:
-------------------------------------------------------
> Try:
>
>
> mkdir -p  /tmp/nand_rootfs
> mount -t ubi0:rootfs /dev/mtdblock1
> /tmp/nand_rootfs
>


mount: unknown filesystem type 'ubi0:rootfs'

I tried all the options I could find for ubiattach but couldn't get anything to work.
Re: What version of Rescue am I running?
June 08, 2018 03:10PM
balanga Wrote:
-------------------------------------------------------
> jcconnell Wrote:
> -------------------------------------------------------
> >
> > pacman -Syu uboot-tools
> >
>
> After running pacman -Syy a few days ago I'm now
> unable ti install anything! Everything I try ends
> up with 'keyring signature ..... is unknown
> trust'
>
> I've gone round is circle for a couple of hours
> trying to remove /etc/pacman.d/gnupg and
> re-install keys but haven't stumbled on the
> correct solution yet. Wondered if you might have
> any advice....

Seems like I'm not the only one having these sort of problems...

https://archlinuxarm.org/forum/viewtopic.php?f=65&t=12796

Running:-
pacman-key --ini
pacman-key --populate archlinuxarm

fixed things today - it didn't work yesterday.



Edited 1 time(s). Last edit at 06/08/2018 03:16PM by balanga.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: