Error Reading Superblock On Volume
HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware > Linux - Embedded & Single-board computer [SOLVED] "Error reading superblock on volume 'ubi:rootfs'!" User Name Remember Me? Password Linux - Embedded & Single-board computer This forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 11-07-2013, 11:19 AM #1 littlebigman Member Registered: Aug 2008 Posts: 499 Rep: "Error reading superblock on volume 'ubi:rootfs'!" Hello, I'm no Linux expert, and have a problem booting a SheevaPlug whose PSU I replaced with a new one after the original blew up. Does someone know what is keeping Debian6 from booting, and what I could try? Thank you. Here's what U-boot says in the console: Code: Marvell>> reset resetting ... U-Boot 2011.12 (Mar 11 2012 - 18:59:46) Marvell-Sheevaplug - eSATA - SD/MMC SoC: Kirkwood
Timing Data Converters Development Tools Digital Signal Processors (DSP) DLP® Products & MEMS Embedded Software Interface Isolation Logic Microcontrollers OMAP™ Applications Processors (Read Only) Power Management RF & Digital Radio Sensor Products Haptics & Touch Wireless Connectivity /etc Support Blogs Analog Wire Analog: The real world Behind the Wheel ConnecTIng Wirelessly Enlightened: The TI DLP® Blog Fully Charged Industrial Strength Launch Your Design Learn E2E Motor Drive & Control MSP Low-Power Plays On http://www.linuxquestions.org/questions/linux-embedded-and-single-board-computer-78/error-reading-superblock-on-volume-'ubi-rootfs'-4175483754/ the Grid Power House Precision Hub The Process Think. Innovate TI Live @... Tools Insider University Program Groups Corporate Citizenship TI University Program Russian E2E (сообщество E2E) Japanese E2E (日本語コミュニティ) Learn E2E Launch Your Design Motor Drive & Control Videos More Cancel Sitara™ Processors Sitara Processors Forum Mentions Tags More Cancel Sign In https://e2e.ti.com/support/arm/sitara_arm/f/791/p/377339/1328882 to Post Sign In to Post Cancel Go to Processors Forums Amplifiers Switches & Multiplexers Applications Processors Clock and Timing Data Converters Development Tools Digital Signal Processors (DSP) DLP® Products & MEMS Embedded Software Interface Isolation Logic Microcontrollers OMAP™ Applications Processors (Read Only) Power Management RF & Digital Radio Sensor Products Haptics & Touch Wireless Connectivity /etc Support Announcements Amplifiers Switches & Multiplexers Applications Processors Clock and Timing Data Converters Development Tools Digital Signal Processors (DSP) DLP® Products & MEMS Embedded Software Interface Isolation Logic Microcontrollers OMAP™ Applications Processors (Read Only) Power Management RF & Digital Radio Sensor Products Haptics & Touch Wireless Connectivity /etc Support More Cancel Not Answered AM335X - Problems with UBIFS from U-Boot Intellectual 350 points anthony barrera Hello,I am running some experiments with UBIFS support in U-BOOT. Here is my setup:----------------------------------------------------------------------------------------------------------------------------AM335X Custom hardware based on BeagleBoneBlack, but with NAND instead of eMMC.Spansion SCL NAND S34ML01G2u-boot-2013.10-ti2013.12.01 taken from TI SDK ti-sdk-am335x-evm-07.00.00.00-----------------------------------------------------------------------------------------------------------------------------Following instructions found on:http://processors.wiki.t
> Hi u-booters, > > I have a short script in my u-boot environment which chooses which of > two ubifs partitions to boot > by attempting to read a release https://www.mail-archive.com/u-boot@lists.denx.de/msg79346.html file in each one. > > Unfortunately, after an unclean shutdown sometimes the ubifsmount > fails. (By "unclean shutdown" > I mean that the board was power cycled while doing some low bandwidth https://support.criticallink.com/redmine/boards/28/topics/2893 > logging.) > > The strange thing is that Linux has no problem mounting the partition > as its root filesystem. This is > very confusing because it looks like the ubifs error reading implementation in > u-boot is just a copy of the one in Linux. > > Has anyone else seen this problem? > > I've now managed to repro this problem and add some debug. It looks like u-boot is simply running out of memory whilst trying to mount a filesystem that "needs recovery". (Error -12 is -ENOMEM.) The partition it is mounting is 240MB, but only error reading superblock about 40MB full. The debug output is below after the "ubifsmount" command: U-Boot 2011.06-00009-g3b6754e-dirty (Mar 08 2012 - 16:30:13) OpenRD-Base SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0 88E6351 Initialized on egiga0 Marvell>> ubi part rootfs 2048 Creating 1 MTD partitions on "nand0": 0x000001000000-0x000010000000 : "mtd=2" UBI: attaching mtd1 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 126976 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 2048 (aligned 2048) UBI: data offset: 4096 UBI: attached mtd1 to ubi0 UBI: MTD device name: "mtd=2" UBI: MTD device size: 240 MiB UBI: number of good PEBs: 1913 UBI: number of bad PEBs: 7 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: 1913 UBI: number of PEBs reserved for bad PEB handling: 19 UBI: max/mean erase counter: 7/1 Marvell>> ubifsmount rootfs UBIFS: recovery needed UBIFS error (pid 0): replay_bud: insert_node failed: err=-12 UBIFS error (pid 0): replay_buds: replay_bud failed: err=-12 UBIFS err
over 3 years ago What's the procedure for creating and writing the Linux UBIFS rootfs to the AM3354 512MB NAND? What ECC is used for the UBIFS partitions? -Kim Replies (18) RE: Writing UBIFS rootfs to AM3354 with 512MB NAND - Added by Tim Iskander over 3 years ago KimTI has a few pages on this.. check out http://processors.wiki.ti.com/index.php/UBIFS_SupportAs long as you program the ubifs from linux there should not be an issue.There is currently a disconnect between ECC used by u-boot and that used by linux on the 4kB page size NAND devices (like the 512MB NAND)cheers/Tim RE: Writing UBIFS rootfs to AM3354 with 512MB NAND - Added by Kim Weller over 3 years ago Hi Tim, I've been following this steps and it looks like the ubi.img is writing to NAND, but I get error 28 (No space left on device) when trying to attach. Here are my steps for writing ubi.img: root@mityarm335x:~# ubiformat /dev/mtd8 -f ubi.img -s 1024 -O 4096 ubiformat: mtd8 (nand), size 528220160 bytes (503.8 MiB), 2015 eraseblocks of 262144 bytes (256.0 KiB), min. I/O size 4096 bytes libscan: scanning eraseblock 2014 -- 100 % complete ubiformat: 2015 eraseblocks are supposedly empty ubiformat: flashing eraseblock 15 -- 100 % complete ubiformat: formatting eraseblock 2014 -- 100 % complete root@mityarm335x:~# ubiattach /dev/ubi_ctrl -m 8 -O 4096 ubiattach: error!: cannot attach mtd8 error 28 (No space left on device) root@mityarm335x:~# flash_erase /dev/mtd8 0 0 Erasing 256 Kibyte @ 1f780000 -- 100 % complete root@mityarm335x:~# mtdinfo /dev/mtd8 mtd8 Name: File System Type: nand Eraseblock size: 262144 bytes, 256.0 KiB Amount of eraseblocks: 2015 (528220160 bytes, 503.8 MiB) Minimum input/output unit size: 4096 bytes Sub-page size: 1024 bytes OOB size: 224 bytes Character device major/minor: 90:16 Bad blocks are allowed: true Device is writable: true root@mityarm335x:~# ubiformat /dev/mtd8 -f ubi.img -s 1024 -O 4096 ubiformat: mtd8 (nand), size 528220160 bytes (503.8 MiB), 2015 eraseblocks of 262144 bytes (256.0 K