Yadi-Update: Unable to mount root fs

Wie blitze ich ein Bild - Permanent Outgoing Incomes
wawersich
Neugieriger
Neugieriger
Beiträge: 3
Registriert: Sonntag 12. Dezember 2004, 11:01

Yadi-Update: Unable to mount root fs

Beitrag von wawersich »

Hi,

Hab folgendes Problem.
Hatte das 200410131913_yadi_squashfs_head_2x.img ohne Probleme am laufen.
Wollte dann auf das 200412081415_mtd1.img updaten - wie hier beschrieben:
http://www.yadi.org/anleitungen/install ... ino_update
Partition einspielen → root (Squashfs)

=> dbox bootet nicht mehr.

Code: Alles auswählen

®debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0  mID 01
debug: feID dd    gtxID 0b
debug: fpID 5a     dsID 01-a9.23.04.07.00.00-35
debug: HWrev X5  SWrev 0.81
debug: B/Ex/Fl(MB) 16/16/08
WATCHDOG reset enabled
dbox2:root> debug: 
BOOTP/TFTP bootstrap loader (v0.3)
debug: 
debug: Transmitting BOOTP request via broadcast
debug: Given up BOOTP/TFTP boot
boot net failed

Flash-FS bootstrap loader (v1.5)

Found Flash-FS superblock version 3.1
Found file /root/platform/nokia-dbox2/kernel/os in Flash-FS
debug: Got Block #0032
debug: Got Block #0004
debug: Got Block #0008
debug: Got Block #0012
debug: Got Block #0016
debug: Got Block #0020
debug: Got Block #0024
debug: Got Block #0028
debug: Got Block #0032


will verify ELF image, start= 0x800000, size= 153208
verify sig: 263
Branching to 0x40000


U-Boot 1.1.1 (TuxBox) (Oct 13 2004 - 17:26:29)

CPU:   PPC823ZTnnA at 67.200 MHz: 2 kB I-Cache 1 kB D-Cache
         *** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
Board: DBOX2, Nokia, BMon V1.0
       Watchdog enabled
I2C:   ready
DRAM:  32 MB
FLASH:  8 MB
Scanning JFFS2 FS: . done.

FB:    ready
LCD:   ready
In:    serial
Out:   serial
Err:   serial
Net:   SCC ETHERNET

Options:
  1: Console on null
  2: Console on ttyS0
  3: Console on framebuffer
Select option (1-3), other keys to stop autoboot:  0 
### FS (jffs2) loading 'vmlinuz' to 0x100000
Scanning JFFS2 FS: . done.

### FS load complete: 626322 bytes loaded to 0x100000
...............................................................
Un-Protected 63 sectors
## Booting image at 00100000 ...
   Image Name:   dbox2
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    626258 Bytes = 611.6 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
Linux version 2.4.27-dbox2 (ImageTeam§yadi.org) (gcc version 3.3.5) #8 Mi Okt 13 19:15:53 CEST 2004
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0 root=/dev/mtdblock3 rootfstype=squashfs
Decrementer Frequency = 252000000/60
m8xx_wdt: active wdt found (SWTC: 0xFFFF, SWP: 0x1)
m8xx_wdt: keep-alive trigger installed (PITC: 0x12C0)
Console: colour dummy device 80x25
Calibrating delay loop... 66.96 BogoMIPS
Memory: 30908k available (1064k kernel code, 336k data, 60k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch§atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
i2c-core.o: i2c core module version 2.6.1 (20010830)
i2c-dev.o: i2c /dev entries driver module version 2.6.1 (20010830)
CPM UART driver version 0.04
ttyS0 at 0x0280 is on SMC1 using BRGttyS1 at 0x0380 is on SMC2 using BRG2
pty: 256 Unix98 ptys configured
eth0: CPM ENET Version 0.2.dbox2 on SCC2, 00:50:9c:16:50:df
loop: loaded (max 8 devices)
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
D-Box 2 flash memory: Found 2 x16 devices at 0x0 in 32-bit mode
 Intel/Sharp Extended Query Table at 0x0035
cfi_cmdset_0001: Erase suspend on write enabled
Using word write method
Creating 7 MTD partitions on "D-Box 2 flash memory":
0x00000000-0x00020000 : "BR bootloader"
0x00020000-0x00040000 : "flfs (u-boot)"
0x00040000-0x000e0000 : "kernel (jffs2)"
0x000e0000-0x006a0000 : "root (squashfs)"
0x006a0000-0x00800000 : "var (jffs2)"
0x00020000-0x00800000 : "flash without bootloader"
0x00000000-0x00800000 : "complete flash"
Linux video capture interface: v1.00
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
attempt to access beyond end of device
1f:03: rw=0, want=6336, limit=5888
attempt to access beyond end of device
1f:03: rw=0, want=6336, limit=5888
attempt to access beyond end of device
1f:03: rw=0, want=6325, limit=5888
SQUASHFS error: sb_bread failed reading block 0x18b4
SQUASHFS error: Unable to read cache block Ä62d266:cb1Ü
SQUASHFS error: Unable to read inode Ä62d266:cb1Ü
SQUASHFS error: Root inode create failed
Kernel panic: VFS: Unable to mount root fs on 1f:03
 <0>Rebooting in 180 seconds..
Kann es an dem ".mtd1" liegen ?
mit den ".mtd3" files ging's immer problemlos.

Was ist eigentlich der Unterschied zwischen mtd1 und mtd3 ?

Danke ... Gruss ... Markus
essu
Tuxboxer
Tuxboxer
Beiträge: 2452
Registriert: Montag 21. Oktober 2002, 10:04

Beitrag von essu »

Du vermutest richtig: Von 1.10.x.x zu 2.0.x.x wurde das Partitionslayout geändert. root ist jetzt mtd1, vorher mt3. Um das aktuelle mtd1 einspielen zu können brauchst du zunächst als BaseImage 2.0.0.1. Update kann man nur innerhalb eines ReleaseCycles.
Schon gelesen ???
ENIGMA-DOC
wawersich
Neugieriger
Neugieriger
Beiträge: 3
Registriert: Sonntag 12. Dezember 2004, 11:01

Beitrag von wawersich »

Danke.

Genau das war's

Gruss ... Markus