about ubiformat mtdblock

about ubiformat mtdblock

[tommy]

hi,dear all!

My kernel version is 2.6.24 ,patch ubifs !

I met error on ubiformat .
Following is my step!


# ./ubiformat /dev/mtd2 -f /ubi.img
ubiformat: mtd2 (NAND), size 654311424 bytes (624.0 MiB), 262144
eraseblocks of 262144 bytes (256.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 2495 -- 100 % complete
ubiformat: 2496 eraseblocks have valid erase counter, mean value is 0
ubiformat: flashing eraseblock 383 -- 100 % complete
ubiformat: formatting eraseblock 2495 -- 100 % complete
# ./ubiattach /dev/ubi_ctrl -m 2
vmalloc is used.
UBI: physical eraseblock size:   262144 bytes (256 KiB)
UBI: logical eraseblock size:    258048 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: volume 0 ("ubifs0") re-sized from 407 to 2468 LEBs
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "File System"
UBI: MTD device size:            624 MiB
UBI: number of good PEBs:        2496
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 2496
UBI: number of PEBs reserved for bad PEB handling: 24
UBI: max/mean erase counter: 2/1
UBI: background thread "ubi_bgt0d" started, PID 306
UBI device number 0, total 2496 LEBs (644087808 bytes, 614.2 MiB),
available 0 LEBs (0 bytes), LEB size 258048 bytes (252.0 KiB)
# mount -t ubifs ubi0_0 /tmp/
UBIFS error (pid 307): ubifs_read_superblock: on-flash format version
is 4, but software only supports up to version 3
mount: mounting ubi0_0 on /tmp/ failed: Invalid argument


can anyone help me ?thanks!

Re: about ubiformat mtdblock

[Artem Bityutskiy]

On Fri, 2009-06-26 at 18:03 +0800, tommy wrote:
> hi,dear all!
> 
> My kernel version is 2.6.24 ,patch ubifs !
> 
> I met error on ubiformat .
> Following is my step!
> 
> 
> # ./ubiformat /dev/mtd2 -f /ubi.img
> ubiformat: mtd2 (NAND), size 654311424 bytes (624.0 MiB), 262144
> eraseblocks of 262144 bytes (256.0 KiB), min. I/O size 2048 bytes
> libscan: scanning eraseblock 2495 -- 100 % complete
> ubiformat: 2496 eraseblocks have valid erase counter, mean value is 0
> ubiformat: flashing eraseblock 383 -- 100 % complete
> ubiformat: formatting eraseblock 2495 -- 100 % complete
> # ./ubiattach /dev/ubi_ctrl -m 2
> vmalloc is used.
> UBI: physical eraseblock size:   262144 bytes (256 KiB)
> UBI: logical eraseblock size:    258048 bytes
> UBI: smallest flash I/O unit:    2048
> UBI: VID header offset:          2048 (aligned 2048)
> UBI: data offset:                4096
> UBI: volume 0 ("ubifs0") re-sized from 407 to 2468 LEBs
> UBI: attached mtd2 to ubi0
> UBI: MTD device name:            "File System"
> UBI: MTD device size:            624 MiB
> UBI: number of good PEBs:        2496
> UBI: number of bad PEBs:         0
> UBI: max. allowed volumes:       128
> UBI: wear-leveling threshold:    4096
> UBI: number of internal volumes: 1
> UBI: number of user volumes:     1
> UBI: available PEBs:             0
> UBI: total number of reserved PEBs: 2496
> UBI: number of PEBs reserved for bad PEB handling: 24
> UBI: max/mean erase counter: 2/1
> UBI: background thread "ubi_bgt0d" started, PID 306
> UBI device number 0, total 2496 LEBs (644087808 bytes, 614.2 MiB),
> available 0 LEBs (0 bytes), LEB size 258048 bytes (252.0 KiB)
> # mount -t ubifs ubi0_0 /tmp/
> UBIFS error (pid 307): ubifs_read_superblock: on-flash format version
> is 4, but software only supports up to version 3
> mount: mounting ubi0_0 on /tmp/ failed: Invalid argument
> 
> 
> can anyone help me ?thanks!

Could you please update your UBI/UBIFS:
git://git.infradead.org/~dedekind/ubifs-v2.6.24.git

See here:
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_source

There were many serious bug-fixes, sou it is a good idea to update
ubifs.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

Re: about ubiformat mtdblock

[tommy]

HI,dear sir !

i have pathed my 2.6.24 BSP with ubifs-2.6.24-git!

It work ok ,but when kernel booting  ,it also say error:
0x00000000-0x00040000 : "Bootloader"
0x00040000-0x00840000 : "Kernel"
0x00840000-0x13440000 : "Rootfs"
0x13440000-0x40000000 : "data"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   262144 bytes (256 KiB)
UBI: logical eraseblock size:    258048 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "Rootfs"
UBI: MTD device size:            300 MiB
UBI: number of good PEBs:        1200
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             5
UBI: total number of reserved PEBs: 1195
UBI: number of PEBs reserved for bad PEB handling: 12

UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   301916160 bytes (294840 KiB, 287 MiB, 1170
LEBs)
UBIFS: journal size:       14966784 bytes (14616 KiB, 14 MiB, 58 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  4952683 bytes (4836 KiB)
VFS: Mounted root (ubifs filesystem).

UBIFS error (pid 628): ubifs_get_sb: cannot open "rootfs", error -22

when it mount ok,also say error "cannot open 'rootfs' ",sir ?

thanks !
On 五, 2009-06-26 at 13:46 +0300, Artem Bityutskiy wrote:
> On Fri, 2009-06-26 at 18:03 +0800, tommy wrote:
> > hi,dear all!
> > 
> > My kernel version is 2.6.24 ,patch ubifs !
> > 
> > I met error on ubiformat .
> > Following is my step!
> > 
> > 
> > # ./ubiformat /dev/mtd2 -f /ubi.img
> > ubiformat: mtd2 (NAND), size 654311424 bytes (624.0 MiB), 262144
> > eraseblocks of 262144 bytes (256.0 KiB), min. I/O size 2048 bytes
> > libscan: scanning eraseblock 2495 -- 100 % complete
> > ubiformat: 2496 eraseblocks have valid erase counter, mean value is 0
> > ubiformat: flashing eraseblock 383 -- 100 % complete
> > ubiformat: formatting eraseblock 2495 -- 100 % complete
> > # ./ubiattach /dev/ubi_ctrl -m 2
> > vmalloc is used.
> > UBI: physical eraseblock size:   262144 bytes (256 KiB)
> > UBI: logical eraseblock size:    258048 bytes
> > UBI: smallest flash I/O unit:    2048
> > UBI: VID header offset:          2048 (aligned 2048)
> > UBI: data offset:                4096
> > UBI: volume 0 ("ubifs0") re-sized from 407 to 2468 LEBs
> > UBI: attached mtd2 to ubi0
> > UBI: MTD device name:            "File System"
> > UBI: MTD device size:            624 MiB
> > UBI: number of good PEBs:        2496
> > UBI: number of bad PEBs:         0
> > UBI: max. allowed volumes:       128
> > UBI: wear-leveling threshold:    4096
> > UBI: number of internal volumes: 1
> > UBI: number of user volumes:     1
> > UBI: available PEBs:             0
> > UBI: total number of reserved PEBs: 2496
> > UBI: number of PEBs reserved for bad PEB handling: 24
> > UBI: max/mean erase counter: 2/1
> > UBI: background thread "ubi_bgt0d" started, PID 306
> > UBI device number 0, total 2496 LEBs (644087808 bytes, 614.2 MiB),
> > available 0 LEBs (0 bytes), LEB size 258048 bytes (252.0 KiB)
> > # mount -t ubifs ubi0_0 /tmp/
> > UBIFS error (pid 307): ubifs_read_superblock: on-flash format version
> > is 4, but software only supports up to version 3
> > mount: mounting ubi0_0 on /tmp/ failed: Invalid argument
> > 
> > 
> > can anyone help me ?thanks!
> 
> Could you please update your UBI/UBIFS:
> git://git.infradead.org/~dedekind/ubifs-v2.6.24.git
> 
> See here:
> http://www.linux-mtd.infradead.org/doc/ubifs.html#L_source
> 
> There were many serious bug-fixes, sou it is a good idea to update
> ubifs.
> 

Re: about ubiformat mtdblock

[Artem Bityutskiy]

On Sat, 2009-06-27 at 11:49 +0800, tommy wrote:
> HI,dear sir !
> 
> i have pathed my 2.6.24 BSP with ubifs-2.6.24-git!
> 
> It work ok ,but when kernel booting  ,it also say error:
> 0x00000000-0x00040000 : "Bootloader"
> 0x00040000-0x00840000 : "Kernel"
> 0x00840000-0x13440000 : "Rootfs"
> 0x13440000-0x40000000 : "data"
> UBI: attaching mtd2 to ubi0
> UBI: physical eraseblock size:   262144 bytes (256 KiB)
> UBI: logical eraseblock size:    258048 bytes
> UBI: smallest flash I/O unit:    2048
> UBI: VID header offset:          2048 (aligned 2048)
> UBI: data offset:                4096
> UBI: attached mtd2 to ubi0
> UBI: MTD device name:            "Rootfs"
> UBI: MTD device size:            300 MiB
> UBI: number of good PEBs:        1200
> UBI: number of bad PEBs:         0
> UBI: max. allowed volumes:       128
> UBI: wear-leveling threshold:    4096
> UBI: number of internal volumes: 1
> UBI: number of user volumes:     1
> UBI: available PEBs:             5
> UBI: total number of reserved PEBs: 1195
> UBI: number of PEBs reserved for bad PEB handling: 12
> 
> UBIFS: mounted UBI device 0, volume 0, name "rootfs"
> UBIFS: file system size:   301916160 bytes (294840 KiB, 287 MiB, 1170
> LEBs)
> UBIFS: journal size:       14966784 bytes (14616 KiB, 14 MiB, 58 LEBs)
> UBIFS: media format:       w4/r0 (latest is w4/r0)
> UBIFS: default compressor: lzo
> UBIFS: reserved for root:  4952683 bytes (4836 KiB)
> VFS: Mounted root (ubifs filesystem).
> 
> UBIFS error (pid 628): ubifs_get_sb: cannot open "rootfs", error -22
> 
> when it mount ok,also say error "cannot open 'rootfs' ",sir ?

-22 is -EINVAL, not sure what happened. Try to send a better bug report,
see here:
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_how_send_bugreport

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

Re: about ubiformat mtdblock

[tommy]

HI,Dear sir !

i have a question!

I have patched your 2.6.24-ubifs-git on my ARM11 platform !

it have succeed run and stable !

My rootfs have a /etc/fstab file !

# stock fstab - you probably want to override this with a machine
specific one

rootfs               /                    auto       defaults
1  1
proc                 /proc                proc       defaults
0  0
devpts               /dev/pts             devpts     mode=0620,gid=5
0  0
#usbdevfs             /proc/bus/usb        usbdevfs   noauto
0  0
tmpfs                /var                 tmpfs      defaults
0  0
tmpfs                /mnt/ram           tmpfs      defaults
0  0

if  i enable "rootfs   /  auto  defaults 1 1 ",when kernel
booting ,ubifs driver will say "UBIFS error (pid 628): ubifs_get_sb:
cannot open "rootfs", error -22"!

if i disable "#rootfs / auto deafults 1 1 ",when kernel booting ,ubifs
driver never say error ,
can you explain it ?

because my old ubifs patched driver never say any error even if  it is
enable  !
 

On 六, 2009-06-27 at 14:32 +0300, Artem Bityutskiy wrote:
> On Sat, 2009-06-27 at 11:49 +0800, tommy wrote:
> > HI,dear sir !
> > 
> > i have pathed my 2.6.24 BSP with ubifs-2.6.24-git!
> > 
> > It work ok ,but when kernel booting  ,it also say error:
> > 0x00000000-0x00040000 : "Bootloader"
> > 0x00040000-0x00840000 : "Kernel"
> > 0x00840000-0x13440000 : "Rootfs"
> > 0x13440000-0x40000000 : "data"
> > UBI: attaching mtd2 to ubi0
> > UBI: physical eraseblock size:   262144 bytes (256 KiB)
> > UBI: logical eraseblock size:    258048 bytes
> > UBI: smallest flash I/O unit:    2048
> > UBI: VID header offset:          2048 (aligned 2048)
> > UBI: data offset:                4096
> > UBI: attached mtd2 to ubi0
> > UBI: MTD device name:            "Rootfs"
> > UBI: MTD device size:            300 MiB
> > UBI: number of good PEBs:        1200
> > UBI: number of bad PEBs:         0
> > UBI: max. allowed volumes:       128
> > UBI: wear-leveling threshold:    4096
> > UBI: number of internal volumes: 1
> > UBI: number of user volumes:     1
> > UBI: available PEBs:             5
> > UBI: total number of reserved PEBs: 1195
> > UBI: number of PEBs reserved for bad PEB handling: 12
> > 
> > UBIFS: mounted UBI device 0, volume 0, name "rootfs"
> > UBIFS: file system size:   301916160 bytes (294840 KiB, 287 MiB, 1170
> > LEBs)
> > UBIFS: journal size:       14966784 bytes (14616 KiB, 14 MiB, 58 LEBs)
> > UBIFS: media format:       w4/r0 (latest is w4/r0)
> > UBIFS: default compressor: lzo
> > UBIFS: reserved for root:  4952683 bytes (4836 KiB)
> > VFS: Mounted root (ubifs filesystem).
> > 
> > UBIFS error (pid 628): ubifs_get_sb: cannot open "rootfs", error -22
> > 
> > when it mount ok,also say error "cannot open 'rootfs' ",sir ?
> 
> -22 is -EINVAL, not sure what happened. Try to send a better bug report,
> see here:
> http://www.linux-mtd.infradead.org/doc/ubifs.html#L_how_send_bugreport
> 

Re: about ubiformat mtdblock

[Artem Bityutskiy]

On Mon, 2009-06-29 at 10:14 +0800, tommy wrote:
> HI,Dear sir !
> 
> i have a question!
> 
> I have patched your 2.6.24-ubifs-git on my ARM11 platform !
> 
> it have succeed run and stable !
> 
> My rootfs have a /etc/fstab file !
> 
> # stock fstab - you probably want to override this with a machine
> specific one
> 
> rootfs               /                    auto       defaults
> 1  1
> proc                 /proc                proc       defaults
> 0  0
> devpts               /dev/pts             devpts     mode=0620,gid=5
> 0  0
> #usbdevfs             /proc/bus/usb        usbdevfs   noauto
> 0  0
> tmpfs                /var                 tmpfs      defaults
> 0  0
> tmpfs                /mnt/ram           tmpfs      defaults
> 0  0
> 
> if  i enable "rootfs   /  auto  defaults 1 1 ",when kernel
> booting ,ubifs driver will say "UBIFS error (pid 628): ubifs_get_sb:
> cannot open "rootfs", error -22"!
> 
> if i disable "#rootfs / auto deafults 1 1 ",when kernel booting ,ubifs
> driver never say error ,
> can you explain it ?
> 
> because my old ubifs patched driver never say any error even if  it is
> enable  !

Can you mount it when you use the mount utility directly?

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

Re: about ubiformat mtdblock

[tommy]

No
root@localhost:/# mount
rootfs on / type rootfs (rw)
ubi0:ubifs1 on / type ubifs (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
ubi0:ubifs1 on /dev/.static/dev type ubifs (rw)
tmpfs on /dev type tmpfs (rw)
ubi1:data on /media type ubifs (rw)
tmpfs on /var type tmpfs (rw)
root@localhost:/# 

On 二, 2009-06-30 at 17:51 +0300, Artem Bityutskiy wrote:
> On Mon, 2009-06-29 at 10:14 +0800, tommy wrote:
> > HI,Dear sir !
> > 
> > i have a question!
> > 
> > I have patched your 2.6.24-ubifs-git on my ARM11 platform !
> > 
> > it have succeed run and stable !
> > 
> > My rootfs have a /etc/fstab file !
> > 
> > # stock fstab - you probably want to override this with a machine
> > specific one
> > 
> > rootfs               /                    auto       defaults
> > 1  1
> > proc                 /proc                proc       defaults
> > 0  0
> > devpts               /dev/pts             devpts     mode=0620,gid=5
> > 0  0
> > #usbdevfs             /proc/bus/usb        usbdevfs   noauto
> > 0  0
> > tmpfs                /var                 tmpfs      defaults
> > 0  0
> > tmpfs                /mnt/ram           tmpfs      defaults
> > 0  0
> > 
> > if  i enable "rootfs   /  auto  defaults 1 1 ",when kernel
> > booting ,ubifs driver will say "UBIFS error (pid 628): ubifs_get_sb:
> > cannot open "rootfs", error -22"!
> > 
> > if i disable "#rootfs / auto deafults 1 1 ",when kernel booting ,ubifs
> > driver never say error ,
> > can you explain it ?
> > 
> > because my old ubifs patched driver never say any error even if  it is
> > enable  !
> 
> Can you mount it when you use the mount utility directly?
> 

Re: about ubiformat mtdblock

[Artem Bityutskiy]

On Wed, 2009-07-01 at 08:54 +0800, tommy wrote:
> No
> root@localhost:/# mount
> rootfs on / type rootfs (rw)
> ubi0:ubifs1 on / type ubifs (rw)
> proc on /proc type proc (rw)
> sysfs on /sys type sysfs (rw)
> ubi0:ubifs1 on /dev/.static/dev type ubifs (rw)
> tmpfs on /dev type tmpfs (rw)
> ubi1:data on /media type ubifs (rw)
> tmpfs on /var type tmpfs (rw)
> root@localhost:/# 

I mean can you mount it if you do it by hand, not via
fstab. I.e., call mount -t ubifs ...

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

Re: about ubiformat mtdblock

[tommy]

my kernel command line is booting from ubif0_0 (rootfs),can't mount
again ,because ubifs0_0 is also in / 
On 三, 2009-07-01 at 12:50 +0300, Artem Bityutskiy wrote:
> On Wed, 2009-07-01 at 08:54 +0800, tommy wrote:
> > No
> > root@localhost:/# mount
> > rootfs on / type rootfs (rw)
> > ubi0:ubifs1 on / type ubifs (rw)
> > proc on /proc type proc (rw)
> > sysfs on /sys type sysfs (rw)
> > ubi0:ubifs1 on /dev/.static/dev type ubifs (rw)
> > tmpfs on /dev type tmpfs (rw)
> > ubi1:data on /media type ubifs (rw)
> > tmpfs on /var type tmpfs (rw)
> > root@localhost:/# 
> 
> I mean can you mount it if you do it by hand, not via
> fstab. I.e., call mount -t ubifs ...
> 

Re: about ubiformat mtdblock

[Artem Bityutskiy]

On Wed, 2009-07-01 at 18:43 +0800, tommy wrote:
> my kernel command line is booting from ubif0_0 (rootfs),can't mount
> again ,because ubifs0_0 is also in / 

Here you may find a way to mount UBIFS via kernel boot parameters:

http://www.linux-mtd.infradead.org/faq/ubifs.html#L_mount_ubifs

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

Re: about ubiformat mtdblock

[tommy]

Uncompressing
Linux.........................................................................................
Linux version 2.6.24.2 (root@tommy-desktop) (gcc version 4.1.2) #123 Wed
Jul 1 11:54:02 CST 2009
CPU: ARMv6-compatible processor [410fb766] revision 6 (ARMv7),
cr=00c5387f
Machine: SMDK6410
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writeback
....................
CPU0: D VIPT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
26924
Kernel command line: root=ubi0:rootfs rootfstype=ubifs ubi.mtd=2
console=ttySAC0,115200
Trying to install chained interrupt handler for IRQ0
Trying to install chained interrupt handler for IRQ1
Trying to install chained interrupt handler for IRQ32
Trying to install chained interrupt handler for IRQ33
PID hash table entries: 512 (order: 9, 2048 bytes)
timer tcon=00600d00, tcnt 103c3, tcfg 00000450,00000040, usec 00001340
Console: colour dummy device 80x30
console [ttySAC0] enabled
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 106MB = 106MB total
Memory: 103552KB available (3452K code, 307K data, 104K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 64 bytes
NET: Registered protocol family 16
S3C DMA-pl080 Controller Driver, (c) 2006-2007 Samsung Electronics
Total 32 DMA channels will be initialized.
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
Power Domain Framework initialized
kdpmd created
NetWinder Floating Point Emulator V0.97 (extended precision)
Kernel DPM daemon thread started
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
PWM channel 1 set g_tcnt = 1000, g_tcmp = 250 
S3C_LCD clock got enabled :: 133.000 Mhz
LCD TYPE :: LTE480WV will be initialized
Window[0] - FB1: map_video_memory: clear ff200000:000bb800
            FB1: map_video_memory: dma=56100000 cpu=ff200000
size=000bb800
Console: switching to colour frame buffer device 100x30
fb0: s3cfb frame buffer device
Window[1] - FB1: map_video_memory: clear ff2bd000:000bb800
            FB1: map_video_memory: dma=56200000 cpu=ff2bd000
size=000bb800
fb1: s3cfb frame buffer device
S3C ADC driver, (c) 2007 Samsung Electronics
S3C ADC driver successfully probed !
s3c-uart.0: s3c_serial0 at MMIO 0x7f005000 (irq = 37) is a S3C
s3c-uart.1: s3c_serial1 at MMIO 0x7f005400 (irq = 38) is a S3C
s3c-uart.2: s3c_serial2 at MMIO 0x7f005800 (irq = 39) is a S3C
s3c-uart.3: s3c_serial3 at MMIO 0x7f005c00 (irq = 40) is a S3C
dm9000 Ethernet Driver
dm9000: read correct id 0x90000a46
eth0: dm9000 at f7600300,f7600304 IRQ 74 MAC: 00:22:44:66:88:aa
Driver 'sd' needs updating - please use bus_type methods
S3C NAND Driver, (c) 2007 Samsung Electronics
S3C NAND Driver is using hardware ECC.
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB
3,3V 8-bit)
Creating 4 MTD partitions on "NAND 1GiB 3,3V 8-bit":
0x00000000-0x00040000 : "Bootloader"
0x00040000-0x00840000 : "Kernel"
0x00840000-0x13440000 : "ubi"
0x13440000-0x40000000 : "data"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   262144 bytes (256 KiB)
UBI: logical eraseblock size:    258048 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "ubi"
UBI: MTD device size:            300 MiB
UBI: number of good PEBs:        1200
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             5
UBI: total number of reserved PEBs: 1195
UBI: number of PEBs reserved for bad PEB handling: 12
UBI: max/mean erase counter: 2/1
UBI: background thread "ubi_bgt0d" started, PID 220
s3c2410-ohci s3c2410-ohci: S3C OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 47, io mem 0x74300000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...

USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for
generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
mice: PS/2 mouse device common for all mice
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c2410-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
S3C PWM Driver, (c) 2006-2007 Samsung Electronics
i2c /dev entries driver
[s3c_hsmmc_probe]: s3c-hsmmc.0: at 0xc7800000 with irq 56. clk src:
sclk_DOUTmpll_mmc0
s3c-hsmmc: card inserted.
[s3c_hsmmc_probe]: s3c-hsmmc.1: at 0xc7a00000 with irq 57. clk src:
sclk_DOUTmpll_mmc1
can NOT find sdio card! 
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.15 (Tue Nov 20
19:16:42 2007 UTC).
ASoC version 0.13.1
WM9713/WM9714 SoC Audio Codec 0.12
...................
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jketreno@linux.intel.com>
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
s3c2410-rtc s3c2410-rtc: setting system clock to 2022-01-02 19:30:22 UTC
(1641151822)
open_ubi name ubi0:rootfs<5>UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   301916160 bytes (294840 KiB, 287 MiB, 1170
LEBs)
UBIFS: journal size:       14966784 bytes (14616 KiB, 14 MiB, 58 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  4952683 bytes (4836 KiB)
VFS: Mounted root (ubifs filesystem).
Freeing init memory: 104K
mmc1: new SDIO card at address 0001
INIT: version 2.86 booting
.udev/ already exists on the static /dev!
Starting the hotplug events dispatcher udevd
Synthesizing the initial hotplug events
Waiting for /dev to be fully populated
mount: mounting proc on /proc failed: Device or resource busy
WARNING: Couldn't open directory /lib/modules/2.6.24.2: No such file or
directory
FATAL: Could not open /lib/modules/2.6.24.2/modules.dep.temp for
writing: No such file or directory
modprobe: FATAL: Could not load /lib/modules/2.6.24.2/modules.dep: No
such file or directory

Starting portmap daemon: portmap.
Nothing to be done
INIT: Entering runlevel: 5
Starting Dropbear SSH server: modprobe: FATAL: Could not
load /lib/modules/2.6.24.2/modules.dep: No such fiy

dropbear.
modprobe: FATAL: Could not load /lib/modules/2.6.24.2/modules.dep: No
such file or directory

Starting system message bus: dbus.
Starting Hardware abstraction layer hald
Starting NetworkManager daemon: NetworkManager.
Starting syslogd/klogd: done
slim script starting...
/usr/sbin/alsactl: set_control:989: warning: name mismatch (PCM Playback
Volume/Line In Volume) for control5
/usr/sbin/alsactl: set_control:991: warning: index mismatch (0/0) for
control #5
mount file name: /
mount file name: /
mount file name: /proc
mount file name: /mnt/.psplash
mount file name: /sys
mount file name: /dev/.static/dev
mount file name: /dev
mount file name: /var
jhr******:zapit: /mnt/.psplash
jhr******:umount rlt 0
Creating Server Authority...

mid-linux (red) 1.0 
 s3c_serial0

mid-fun login:  



ps:

if my board nfs boot ,not ubifs boot,following is ok!
nfs@root:ubiattach /dev/ubi_ctrl -m 2
nfs@root:mount -t ubifs ubi0_0 /mnt /
it it ok!

but i don't know /etc/fstab 's rootfs mount can cause ubifs say error!
On 三, 2009-07-01 at 13:45 +0300, Artem Bityutskiy wrote:
> On Wed, 2009-07-01 at 18:43 +0800, tommy wrote:
> > my kernel command line is booting from ubif0_0 (rootfs),can't mount
> > again ,because ubifs0_0 is also in / 
> 
> Here you may find a way to mount UBIFS via kernel boot parameters:
> 
> http://www.linux-mtd.infradead.org/faq/ubifs.html#L_mount_ubifs
> 

Re: about ubiformat mtdblock

[Artem Bityutskiy]

On Wed, 2009-07-01 at 18:58 +0800, tommy wrote:
> ps:
> 
> if my board nfs boot ,not ubifs boot,following is ok!
> nfs@root:ubiattach /dev/ubi_ctrl -m 2
> nfs@root:mount -t ubifs ubi0_0 /mnt /
> it it ok!

Try adding:

ubi.mtd=0 root=ubi0_0 rootfstype=ubifs

to the kernel boot line.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

Re: about ubiformat mtdblock

[tommy]

THANKS!~
Kernel command line: console=ttySAC0,115200 ubi.mtd=2 root=ubi0_0
rootfstype=ubifs

mount: mounting proc on /proc failed: Device or resource busy      
WARNING: Couldn't open directory /lib/modules/2.6.24.2: No such file or
directory
FATAL: Could not open /lib/modules/2.6.24.2/modules.dep.temp for
writing: No such file or directory
modprobe: FATAL: Could not load /lib/modules/2.6.24.2/modules.dep: No
such file or directory

modprobe: FATAL: Could not load /lib/modules/2.6.24.2/modules.dep: No
such file or directory

open_ubi name rootfs<3>UBIFS error (pid 576): ubifs_get_sb: cannot open
"rootfs", error -22 

root@localhost:/etc/rcS.d# vi S35mountall.sh
#
# Mount local filesystems in /etc/fstab. For some reason, people
# might want to mount "proc" several times, and mount -v complains
# about this. So we mount "proc" filesystems without -v.
#
test "$VERBOSE" != no && echo "Mounting local filesystems..."
mount -at nonfs,nosmbfs,noncpfs 2>/dev/null

root@localhost:/etc/rcS.d# cat ../fstab
# stock fstab - you probably want to override this with a machine
specific one

rootfs               /                    auto       defaults
1  1
proc                 /proc                proc       defaults
0  0
devpts               /dev/pts             devpts     mode=0620,gid=5
0  0
#usbdevfs             /proc/bus/usb        usbdevfs   noauto
0  0
tmpfs                /var                 tmpfs      defaults
0  0
tmpfs                /mnt/ram           tmpfs      defaults
0  0

# uncomment this if your device has a SD/MMC/Transflash slot
#/dev/mmcblk0p1       /media/card          auto
defaults,sync,noauto  0  0



On 三, 2009-07-01 at 14:06 +0300, Artem Bityutskiy wrote:
> On Wed, 2009-07-01 at 18:58 +0800, tommy wrote:
> > ps:
> > 
> > if my board nfs boot ,not ubifs boot,following is ok!
> > nfs@root:ubiattach /dev/ubi_ctrl -m 2
> > nfs@root:mount -t ubifs ubi0_0 /mnt /
> > it it ok!
> 
> Try adding:
> 
> ubi.mtd=0 root=ubi0_0 rootfstype=ubifs
> 
> to the kernel boot line.
> 

Re: about ubiformat mtdblock

[tommy]

hi,dear sir !

i met a new question in UBIFS rootfs system !

when i inser a SD card in my board ,system say error :
UBIFS error (pid 1809): ubifs_get_sb: cannot open "/dev/mmcblk0", error
-22

what cause this error ?

On 二, 2009-06-30 at 17:51 +0300, Artem Bityutskiy wrote:
> On Mon, 2009-06-29 at 10:14 +0800, tommy wrote:
> > HI,Dear sir !
> > 
> > i have a question!
> > 
> > I have patched your 2.6.24-ubifs-git on my ARM11 platform !
> > 
> > it have succeed run and stable !
> > 
> > My rootfs have a /etc/fstab file !
> > 
> > # stock fstab - you probably want to override this with a machine
> > specific one
> > 
> > rootfs               /                    auto       defaults
> > 1  1
> > proc                 /proc                proc       defaults
> > 0  0
> > devpts               /dev/pts             devpts     mode=0620,gid=5
> > 0  0
> > #usbdevfs             /proc/bus/usb        usbdevfs   noauto
> > 0  0
> > tmpfs                /var                 tmpfs      defaults
> > 0  0
> > tmpfs                /mnt/ram           tmpfs      defaults
> > 0  0
> > 
> > if  i enable "rootfs   /  auto  defaults 1 1 ",when kernel
> > booting ,ubifs driver will say "UBIFS error (pid 628): ubifs_get_sb:
> > cannot open "rootfs", error -22"!
> > 
> > if i disable "#rootfs / auto deafults 1 1 ",when kernel booting ,ubifs
> > driver never say error ,
> > can you explain it ?
> > 
> > because my old ubifs patched driver never say any error even if  it is
> > enable  !
> 
> Can you mount it when you use the mount utility directly?
> 

Re: about ubiformat mtdblock

[tommy]

thanks,i know ubifs !

When i inser a sd card ,ubifs say error ,i can't undertand!
UBIFS error (pid 1809): ubifs_get_sb: cannot open "/dev/mmcblk0", error

can you explain ?
-
On 四, 2009-07-02 at 17:55 +0800, Ivan Chan wrote:
> Hi,
> 
> The ubifs/ubi should work on NAND device but not a SD card.
> SD card should use vfat.
> 
> Regards,
> Ivan
> 
> On Thu, Jul 2, 2009 at 5:39 PM, tommy<jiujin.hong@mid-fun.com> wrote:
> > hi,dear sir !
> >
> > i met a new question in UBIFS rootfs system !
> >
> > when i inser a SD card in my board ,system say error :
> > UBIFS error (pid 1809): ubifs_get_sb: cannot open "/dev/mmcblk0", error
> > -22
> >
> > what cause this error ?
> >
> > On 二, 2009-06-30 at 17:51 +0300, Artem Bityutskiy wrote:
> >> On Mon, 2009-06-29 at 10:14 +0800, tommy wrote:
> >> > HI,Dear sir !
> >> >
> >> > i have a question!
> >> >
> >> > I have patched your 2.6.24-ubifs-git on my ARM11 platform !
> >> >
> >> > it have succeed run and stable !
> >> >
> >> > My rootfs have a /etc/fstab file !
> >> >
> >> > # stock fstab - you probably want to override this with a machine
> >> > specific one
> >> >
> >> > rootfs               /                    auto       defaults
> >> > 1  1
> >> > proc                 /proc                proc       defaults
> >> > 0  0
> >> > devpts               /dev/pts             devpts     mode=0620,gid=5
> >> > 0  0
> >> > #usbdevfs             /proc/bus/usb        usbdevfs   noauto
> >> > 0  0
> >> > tmpfs                /var                 tmpfs      defaults
> >> > 0  0
> >> > tmpfs                /mnt/ram           tmpfs      defaults
> >> > 0  0
> >> >
> >> > if  i enable "rootfs   /  auto  defaults 1 1 ",when kernel
> >> > booting ,ubifs driver will say "UBIFS error (pid 628): ubifs_get_sb:
> >> > cannot open "rootfs", error -22"!
> >> >
> >> > if i disable "#rootfs / auto deafults 1 1 ",when kernel booting ,ubifs
> >> > driver never say error ,
> >> > can you explain it ?
> >> >
> >> > because my old ubifs patched driver never say any error even if  it is
> >> > enable  !
> >>
> >> Can you mount it when you use the mount utility directly?
> >>
> >
> >
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/
> >
>