Re: What version of Rescue am I running? June 06, 2018 05:06PM |
Registered: 7 years ago Posts: 337 |
> mkdir -p /tmp/nand/ > mount -t ubifs /dev/mtdblock3 /tmp/nand/ >>
> ubiattach /dev/ubi_ctrl -m 3 >
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 07, 2018 12:10AM |
Admin Registered: 13 years ago Posts: 19,010 |
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
cat /proc/mtd
Re: What version of Rescue am I running? June 07, 2018 05:41PM |
Registered: 7 years ago Posts: 337 |
> pacman -Syu uboot-tools >
Re: What version of Rescue am I running? June 07, 2018 05:54PM |
Registered: 7 years ago Posts: 337 |
Re: What version of Rescue am I running? June 07, 2018 06:15PM |
Admin Registered: 13 years ago Posts: 19,010 |
> > cat /proc/mtd > >>
Re: What version of Rescue am I running? June 08, 2018 12:43AM |
Admin Registered: 13 years ago Posts: 19,010 |
mkdir -p /tmp/nand_rootfs mount -t ubi0:rootfs /dev/mtdblock1 /tmp/nand_rootfs
Re: What version of Rescue am I running? June 08, 2018 03:48PM |
Registered: 7 years ago Posts: 337 |
> mkdir -p /tmp/nand_rootfs > mount -t ubi0:rootfs /dev/mtdblock1 > /tmp/nand_rootfs >
Re: What version of Rescue am I running? June 08, 2018 04:10PM |
Registered: 7 years ago Posts: 337 |
> > pacman -Syu uboot-tools > >>
pacman-key --ini pacman-key --populate archlinuxarm