* tftp or nfs?
@ 2011-08-20 10:08 Nataraj S Narayan
2011-08-20 20:42 ` Marc Kleine-Budde
0 siblings, 1 reply; 3+ messages in thread
From: Nataraj S Narayan @ 2011-08-20 10:08 UTC (permalink / raw)
To: barebox
Hi
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
UBI warning: ubi_ro_mode: switch to read-only mode
Couldnt or partially wrote data
write: Invalid argument
tftp failed: error -22
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: tftp or nfs? 2011-08-20 10:08 tftp or nfs? Nataraj S Narayan @ 2011-08-20 20:42 ` Marc Kleine-Budde 2011-08-22 5:26 ` Nataraj S Narayan 0 siblings, 1 reply; 3+ messages in thread From: Marc Kleine-Budde @ 2011-08-20 20:42 UTC (permalink / raw) To: Nataraj S Narayan; +Cc: barebox [-- Attachment #1.1: Type: text/plain, Size: 1241 bytes --] 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 | [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 262 bytes --] [-- Attachment #2: Type: text/plain, Size: 149 bytes --] _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: tftp or nfs? 2011-08-20 20:42 ` Marc Kleine-Budde @ 2011-08-22 5:26 ` Nataraj S Narayan 0 siblings, 0 replies; 3+ messages in thread From: Nataraj S Narayan @ 2011-08-22 5:26 UTC (permalink / raw) To: Marc Kleine-Budde; +Cc: barebox 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-08-22 5:26 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2011-08-20 10:08 tftp or nfs? Nataraj S Narayan 2011-08-20 20:42 ` Marc Kleine-Budde 2011-08-22 5:26 ` Nataraj S Narayan
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox