UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19

Hello,

I am getting mad, my dockstar is not booting a new squeeze install.
even a uboot update did not help.
Can anybody please give me a hint, what is going wrong?
Here is my netcat output:

*** Version 0.1 ***

*** listening on port 6666 ***

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 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: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            219 MiB
UBI: number of good PEBs:        1751
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             1730
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: .......  read_nand_cached: error reading nand off 0x8ecc00 size 8192 byte.......  read_nand_cached: error reading nand off 0x2445800 size 8192 byte done.
read_nand_cached: error reading nand off 0x8ed800 size 8192 bytes
off = 0x8ecd28 magic 0x1985 type 0xe002 node.totlen = 2912
read_nand_cached: error reading nand off 0x8ed600 size 8192 bytes
read_nand_cached: error reading nand off 0x2444200 size 8192 bytes
off = 0x2444088 magic 0x1985 type 0xe002 node.totlen = 2703
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

Regards, Dieter

Dieter,

Ignore all other error messages, they are supposed to be there. This is what matter:

Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd

You USB rootfs does not have uImage or uInitrd. If you'verecently run Jeff's installation or some others then look at the rootfs. Either copy them from a backup, or run the installation again.

Or if the other kernel files are there then run mkimage to generate uImage and uInitrd. This is an example only, please replace your kernel file names in these 2 commands:

cd /boot
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.18.5-kirkwood-tld-1 -d /boot/vmlinuz-3.18.5-kirkwood-tld-1 /boot/uImage 
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.18.5-kirkwood-tld-1 -d /boot/initrd.img-3.18.5-kirkwood-tld-1 /boot/uInitrd

If not sure, post the ls command output for the rootfs /boot directory:

ls -l /boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/28/2015 04:10AM by bodhi.

Hello Bodhi,

thank you very much for you support!

This is my boot directory:

System.map-2.6.32-5-kirkwood  initrd.img-2.6.32-5-kirkwood
config-2.6.32-5-kirkwood      vmlinuz-2.6.32-5-kirkwood

I ran Jeff's squeeze script, why doesn't it generate these files?
I don't have mkimage. Where do I get this from? Is this the problem?

I would like to use your versions, specially as I also have a oxnas device. But the installation is not so simple for me to understand.
I will have a try anyway! :-)

Regards, Dieter

Hello,

stupid me, found mkimage!

Did what you said. Getting now as far as "starting kernel", that is it. No ssh access, not found on the client list on my router?!?

Regards, Dieter

Hello,

maybe you could help me again.

I realised, that even the interfaces config was missing. So I dumped it completely.

I did rm -r * on the ext2 partition and took your

Quote

Linux Kernel 3.18 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs

Not I am getting again as far as

...
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2875844 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
6535284 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.18.5-kirkwood-tld-1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2875780 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.18.5-kirkwood-tld-1
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6535220 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

However, I can not access it. It does not show up on the router's device list?
"interfaces" is there and configured right?!?
The green light is green, not flashing.

I did not do anything for step 1, maybe that is the problem, but it was not clear to me?!?

So what can I do?

Regards, Dieter



Edited 2 time(s). Last edit at 03/28/2015 01:55PM by Dieter.

Dieter,

Try:

- Create a single EXT3 on USB
- Use the 3.16 rootfs, as is. Don't change fstab or anything.

It should boot with davygravy u-boot, which you've installed by running Jeff's script for squeeze/wheezy.

BTW, green LED means the kernel has booted. But rootfs can not be mounted for some reason.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/28/2015 02:34PM by bodhi.

Hello,

I did what you said and finally succeeded. THANK YOU!

I followed the

Quote

Updated 02 Sept 2014:

tutorial.

I have now a running debian! wow, super. I also installed now Jeff's rescue system, as I don't want to see the pogoplug stuff ever again.

But I am not 100% happy yet. I don't have any swap partition, How could I get one working?
And what is the advantage of the FDT-Version?
Should I update uboot?

Regards, Dieter

Dieter,

> But I am not 100% happy yet. I don't have any swap
> partition, How could I get one working?

It's simpler to use a swap file.

> And what is the advantage of the FDT-Version?

To be able to install newer kernel.

> Should I update uboot?

Depending on your needs, look at the sumary description in the u-boot thread and see if you need/want any of the new features since u-boot 2012.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello Bodhi,

thanks again for all the support so far!

could you please point me to a source, how to configure a swap file? Or could I simply use a general howto for debian?
Why is the swap partition not working. Would an updated uboot help?

Regards, Dieter

Dieter,

> could you please point me to a source, how to
> configure a swap file? Or could I simply use a
> general howto for debian?

I don't have a link but the instruction is simple enough:

Turn off swap

swapoff -a

Create the swap file named /swapfile1 with size 512K

dd if=/dev/zero of=/swapfile1 bs=1024 count=524288

Prepare the file for swap space

mkswap /swapfile1

Add this to /etc/rc.local so that it wil be turned on at startup

swapon /swapfile1

> Why is the swap partition not working. Would an
> updated uboot help?

Swap partition should work (not related to u-boot). Perhaps you've missed some steps, such as adding it to /etc/fstab.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)