Re: [Gumstix-users] UBIFS boot fails to work on latest release

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

You are right on time :) I was in a middle writing letter to you. Googling
shows that I am not the only one having this issue. Looks like 2.6.37
doesn't have this problem, but I haven't tested it as I think is still in
heavy development?

ubinize.cfg: vol_name=overo-rootfs

2048 would disable pages, but I think did do anything, but I am soon gonna
test it again.

On MMC I had my old 2.6.34 which still could access UBIFS partition after
flashing, but after updating MMC to 2.6.36, no more:

root@overo:~# ubiattach /dev/ubi_ctrl -m 4
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       0
UBI: volume 0 ("overo-rootfs") re-sized from 562 to 1973 LEBs
UBI: attached mtd4 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            249 MiB
UBI: number of good PEBs:        1996
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: 1996
UBI: number of PEBs reserved for bad PEB handling: 19
UBI: max/mean erase counter: 2/1
UBI: image sequence number:  1902834807
UBI: background thread "ubi_bgt0d" started, PID 4346
UBI device number 0, total 1996 LEBs (257531904 bytes, 245.6 MiB), available
0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
root@overo:~# mkdir -p /mnt/root
root@overo:~# mount -t ubifs ubi0:overo-rootfs /mnt/root
mount: ubi0:overo-rootfs already mounted or /mnt/root busy
root@overo:~# mount -t ubifs ubi0:overo-rootfs /mnt/root
mount: ubi0:overo-rootfs already mounted or /mnt/root busy

syslog:

Feb 20 14:19:24 overo UBI: attaching mtd4 to ubi0
Feb 20 14:19:24 overo UBI: physical eraseblock size:   131072 bytes (128
KiB)
Feb 20 14:19:24 overo UBI: logical eraseblock size:    129024 bytes
Feb 20 14:19:24 overo UBI: smallest flash I/O unit:    2048
Feb 20 14:19:24 overo UBI: sub-page size:              512
Feb 20 14:19:24 overo UBI: VID header offset:          512 (aligned 512)
Feb 20 14:19:24 overo UBI: data offset:                2048
Feb 20 14:19:25 overo UBI: max. sequence number:       0
Feb 20 14:19:25 overo gluebi (pid 4345): gluebi_resized: got update
notification for unknown UBI device 0 volume 0
Feb 20 14:19:25 overo UBI: volume 0 ("overo-rootfs") re-sized from 562 to
1973 LEBs
Feb 20 14:19:25 overo UBI: attached mtd4 to ubi0
Feb 20 14:19:25 overo UBI: MTD device name:            "rootfs"
Feb 20 14:19:25 overo UBI: MTD device size:            249 MiB
Feb 20 14:19:25 overo UBI: number of good PEBs:        1996
Feb 20 14:19:25 overo UBI: number of bad PEBs:         0
Feb 20 14:19:25 overo UBI: max. allowed volumes:       128
Feb 20 14:19:25 overo UBI: wear-leveling threshold:    4096
Feb 20 14:19:25 overo UBI: number of internal volumes: 1
Feb 20 14:19:25 overo UBI: number of user volumes:     1
Feb 20 14:19:25 overo UBI: available PEBs:             0
Feb 20 14:19:25 overo UBI: total number of reserved PEBs: 1996
Feb 20 14:19:25 overo UBI: number of PEBs reserved for bad PEB handling: 19
Feb 20 14:19:25 overo UBI: max/mean erase counter: 2/1
Feb 20 14:19:25 overo UBI: image sequence number:  1902834807
Feb 20 14:19:25 overo UBI: background thread "ubi_bgt0d" started, PID 4346
Feb 20 14:19:25 overo logger: udev/mount.sh [/dev/mtdblock5] is blacklisted,
ignoring
Feb 20 14:19:38 overo UBIFS DBG (pid 4365): ubifs_get_sb: name
ubi0:overo-rootfs, flags 0x0
Feb 20 14:19:38 overo UBIFS DBG (pid 4365): ubifs_get_sb: opened ubi0_0
Feb 20 14:19:52 overo ntpd_initres[4294]: host name not found: pool.ntp.org
Feb 20 14:20:01 overo ntpd[4291]: synchronized to LOCAL(0), stratum 14
Feb 20 14:20:01 overo ntpd[4291]: kernel time sync status change 0001
Feb 20 14:23:54 overo ntpd_initres[4294]: host name not found: pool.ntp.org
Feb 20 14:26:46 overo syslog-ng[4295]: Log statistics;
processed='center(queued)=1846', processed='center(received)=401',
processed='destination(messages)=267', processed='destination(mailinfo)=0',
processed='destination(mailwarn)=0', processed='destination(console)=0',
processed='destination(ppp)=0', processed='destination(authlog)=12',
processed='destination(user)=1', processed='destination(lpr)=0',
processed='destination(daemon)=30', processed='destination(uucp)=0',
processed='destination(cron)=0', processed='destination(kern)=357',
processed='destination(console_all)=401', processed='destination(mail)=0',
processed='destination(xconsole)=0', processed='destination(debug)=389',
processed='destination(syslog)=389', processed='destination(newserr)=0',
processed='destination(newscrit)=0', processed='destination(newsnotice)=0',
processed='destination(mailerr)=0', processed='source(src)=401',
processed='source(net)=0'
Feb 20 14:31:57 overo ntpd_initres[4294]: host name not found: pool.ntp.org
Feb 20 14:35:54 overo UBIFS DBG (pid 4366): ubifs_get_sb: name
ubi0:overo-rootfs, flags 0x0
Feb 20 14:35:54 overo UBIFS DBG (pid 4366): ubifs_get_sb: opened ubi0_0

sakoman wrote:
> 
> On Sun, Feb 20, 2011 at 4:45 AM, David Abdurachmanov
>  wrote:
>> I moved from older release (2.6.34 kernel) to latest one with 2.6.36. And
>> UBIFS seems not to work anymore. I flash my NAND and I can mount UBIFS
>> partitions and access files. Trying to boot from NAND fails. Both kernels
>> has save UBIFS config options enabled with identical values. Everything
>> is
>> set up exactly as in old version. Any ideas what's getting wrong here?
>> Modifications for u-boot env:
>>
>> setenv nandroot 'ubi0:overo-rootfs ubi.mtd=4,512'
>> setenv nandrootfstype ubifs
>>
>> OR
>>
>> setenv nandroot 'ubi0:overo-rootfs ubi.mtd=4'
>> setenv nandrootfstype ubifs
> 
> It has been many months since I've worked with ubifs on Overo, but my
> notes from back then indicated I used:
> 
> Overo # setenv nandrootfstype ubifs
> Overo # setenv nandroot ubi0:rootfs ubi.mtd=4,2048
> 
> I'm working with the 2.6.38rc series at the moment, so later this week
> I'll take some time and see how ubifs is working on the most recent
> upstream.
> 
> Steve
> 
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
> 
> 

-- 
View this message in context: http://old.nabble.com/UBIFS-boot-fails-to-work-on-latest-release-tp30970435p30971644.html
Sent from the Gumstix mailing list archive at Nabble.com.