mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Nataraj S Narayan <natarajsn@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: tftp or nfs?
Date: Mon, 22 Aug 2011 05:26:30 +0000	[thread overview]
Message-ID: <CAK8HZO+b3eRwCawDwnU_CjMPSinuW1d8QcOSBt_7wE15WRa=vg@mail.gmail.com> (raw)
In-Reply-To: <4E501C1A.5090003@pengutronix.de>

Hi Marc

Is it a tough job to add 'ubiformat' to barebox?  Also a ubifsmount?

I have been getting hell lots of ubi errors in Linux also.

These began when I changed a from Micron Nand to Samsung Nand. We have
been trying to change the 'wait states' in the kernel code. But still
the same issues.

regards

Nataraj

NAND 0device: Manufacturer ID: x2c, Chip ID: 0xda (Micron NAND 256MiB
3,3V 8-bit)

NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB
3,3V 8-bit) AT91 NAND: 8-bit

UBI error: ubi_io_read: error -74 (ECC error) while reading 129024
bytes from PEB 517:2048, read 129024 bytes
usb 1-1: new full speed USB device number 2 using at91_ohci
UBIFS: recovery needed
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
uncorrectable error :
UBI error: ubi_io_read: error -74 (ECC error) while reading 106496
bytes from PEB 782:2048, read 106496 bytes
UBIFS error (pid 1): ubifs_recover_leb: LEB 225 scanning failed
VFS: Cannot open root device "ubi0:root" or unknown-block(0,0)
On Sat, Aug 20, 2011 at 8:42 PM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> On 08/20/2011 12:08 PM, Nataraj S Narayan wrote:
>> Unable to download and write a 30Mb ubifs file over tftp.  Any other
>> preferred method of writing to ubi volume?
>>
>> Usb mass store doesn't mount.
>>
>> regards
>>
>> Nataraj
>>
>> barebox@Atmel at91sam9263-ek:/ tftp rootfs.ubifs /dev/ubi0.root
>> warning: No MAC address set. Using random address 4A:01:CD:DA:A9:3C
>> phy0: Link is up - 100/Full
>> TFTP from server 192.168.0.110 ('rootfs.ubifs' -> '/dev/ubi0.root')
>>         #################################################UBI error: ubi_io_writs
>> UBI warning: ubi_eba_write_leb: failed to write data to PEB 603189552
>
> your PED (physical erase block) 603189552 seems to have a problem....
> Although the number itself is quite big: 603.189.552.
>
> Boot Linux and reformat the ubi.
>
>> UBI warning: ubi_ro_mode: switch to read-only mode
>> Couldnt or partially wrote data
>> write: Invalid argument
>>
>> tftp failed: error -22
>
> cheers, Marc
>
> --
> Pengutronix e.K.                  | Marc Kleine-Budde           |
> Industrial Linux Solutions        | Phone: +49-231-2826-924     |
> Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |
>
>

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2011-08-22  5:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-20 10:08 Nataraj S Narayan
2011-08-20 20:42 ` Marc Kleine-Budde
2011-08-22  5:26   ` Nataraj S Narayan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK8HZO+b3eRwCawDwnU_CjMPSinuW1d8QcOSBt_7wE15WRa=vg@mail.gmail.com' \
    --to=natarajsn@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=mkl@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox