DS : help on error -19

Hi all,
i am facing an issue on my dockstar. Everything was ok i think, using http://jeff.doozan.com/debian/ . but i have unplugged my usb an after that i taped a 'reboot'.
now, it does not start on usb, neither without usb :

# nc -l -u -p 6666 & nc -u 192.168.1.100 6666
[1] 1841

U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
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'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
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: ........ done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

DS 's LED stay blinking orange.
Any help ?
Sincerly.
Arnaud

1up please.
Arnaud

1. Take your USB drive to another machine and see if it is recognized there. If so, fsck its file systems and make sure it is clean. If errors are found, pay attention to what is being removed, and if is important, make sure you restore it before trying to boot with that stick again.

2. How do you know it is not booting to the internal OS? If you haven't modified it on the NAND, it probably is. Some (most?) DHCP servers will assign the internal OS a different IP address than they assign the Debian load, so verify that it is not simply using a different IP address.

Good luck.

Hello restamp.
tks for your response.
good news.
1. usb is connected to my other main server. & is accessible:). code bellow.
2. DS is connected and boots properly :)
everything is fine !!!

except i think my usb is not so compatible with DS (Verbatim store N GO 4Go)

# fdisk -l

Disk /dev/sda: 34.3 GB, 34359738368 bytes
255 heads, 63 sectors/track, 4177 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005ed00

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        4036    32419138+  83  Linux
/dev/sda2            4037        4177     1132582+   5  Extended
/dev/sda5            4037        4177     1132551   82  Linux swap / Solaris

Disk /dev/sdb: 3999 MB, 3999268864 bytes
82 heads, 18 sectors/track, 5292 cylinders
Units = cylinders of 1476 * 512 = 755712 bytes
Disk identifier: 0xc3072e18

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1         513      378593+  83  Linux
/dev/sdb2             514         770      189666   82  Linux swap / Solaris
/dev/sdb3             771        5292     3337236   83  Linux
speak:/home/bzhchti# tune2fs -l /dev/sdb1
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          8246bd08-ef5b-4620-980a-3a7dc14412e3
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      ext_attr resize_inode dir_index filetype sparse_super
Filesystem flags:         unsigned_directory_hash
Default mount options:    (none)
Filesystem state:         not clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              94752
Block count:              378592
Reserved block count:     18929
Free blocks:              2
Free inodes:              80682
First block:              1
Block size:               1024
Fragment size:            1024
Reserved GDT blocks:      256
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2016
Inode blocks per group:   252
Filesystem created:       Sat Jan  1 06:17:59 2000
Last mount time:          Tue Apr  5 00:09:56 2011
Last write time:          Tue Apr  5 00:09:56 2011
Mount count:              3
Maximum mount count:      20
Last checked:             Sat Jan  1 06:17:59 2000
Check interval:           15552000 (6 months)
Next check after:         Thu Jun 29 07:17:59 2000
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Default directory hash:   half_md4
Directory Hash Seed:      9e99d700-f341-4f3c-a59d-c84eeadc2656

Well, you told me to run fsck, but i am not a linux expert. would you please help me on this.

Tks in advance for your help.
Arnaud

I'd try

# fsck -n /dev/sdb1

first to see if there are problems. If there are, you need to run the command without the '-n' argument and correct them. But, beware: If there is corruption, fsck will make the file system internally consistent, but not necessarily complete. It can remove corrupt files that are needed for the OS to boot or run properly. This is an unlikely, but possible, outcome.

Also, if you are mounting the third partition, you need to fsck that one, too. Once that is done, take the thumb drive back to the Dockstar and see if it boots. If it does, the likely reason it did not come up before was that Linux noted the problems with the file system and dumped a message onto the console to force an fsck, but of course without a console, that is impossible. If it still doesn't come up, either there is a problem with the root file system that was introduced by the corruption and ensuing fsck, or there is a problem with the thumb drive.

Good luck.

Dear Restamp, many thks for your help.
I will try tonight.
My point of view is th usb drive is not quiet compliant with dockstar. I also tryied on a pgoplug (pink), unsuccessufully.
I think that i will buy a hdd full compatible.
Anyway, Many thks.
Arnaud

Hi all, hi restamp, fsck did not solved, and i decided to re install all !

many tks.
arnaud