Quantcast
Channel: Linux Device Hacking - uBoot
Viewing all articles
Browse latest Browse all 903

Problem booting NSA325v2 on HDD (1 reply)

$
0
0
Dear bodhi,

first of all a big thank you for your great work!

I used your 2016.05 U-Boot on my NSA325v2 and everything went fine so far.
I am also using your Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on my USB-Stick which is also working well.

As this new U-Boot should be able to boot ext4 rootfs i wanted to switch to an ext4 rootfs on the left sata disk which becomes sda when i remove the usbstick.

Because the harddisk is 3TB i made a clean GPT partition table and created partition 1 with 50GB and formatted it with ext4 and labeled it rootfs.
Then i followed your instructions for installing the rootfs on the stick by using the partition i just created on the disk.
After removing the stick it starts to boot but then gives kernel panic.

Here is the end of the output before it stops

[    1.253586] usb usb2: Product: xHCI Host Controller
[    1.258482] usb usb2: Manufacturer: Linux 4.4.0-kirkwood-tld-1 xhci-hcd
[    1.265138] usb usb2: SerialNumber: 0000:01:00.0
[    1.270348] hub 2-0:1.0: USB hub found
[    1.274179] hub 2-0:1.0: 2 ports detected
[    1.278648] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    1.283951] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[    1.291442] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.299690] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[    1.306521] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.313853] usb usb3: Product: xHCI Host Controller
[    1.318755] usb usb3: Manufacturer: Linux 4.4.0-kirkwood-tld-1 xhci-hcd
[    1.325414] usb usb3: SerialNumber: 0000:01:00.0
[    1.330584] hub 3-0:1.0: USB hub found
[    1.334405] hub 3-0:1.0: 2 ports detected
[    1.339173] mousedev: PS/2 mouse device common for all mice
[    1.345090] i2c /dev entries driver
[    1.349188] rtc-pcf8563 0-0051: chip found, driver version 0.4.4
[    1.359673] rtc rtc0: invalid alarm value: 2017-2-29 22:74:0
[    1.365547] rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc0
[    1.374822] hidraw: raw HID events driver (C) Jiri Kosina
[    1.380545] drop_monitor: Initializing network drop monitor service
[    1.387065] NET: Registered protocol family 17
[    1.391744] Key type dns_resolver registered
[    1.396649] registered taskstats version 1
[    1.400798] Loading compiled-in X.509 certificates
[    1.405679] zswap: loaded using pool lzo/zbud
[    1.410881] Key type encrypted registered
[    1.416726] rtc-pcf8563 0-0051: setting system clock to 2017-02-21 09:53:50 UTC (1487670830)
[    1.427005] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    1.434691] Please append a correct "root=" boot option; here are the available partitions:
[    1.443297] 1f00          131072 mtdblock0  (driver?)
[    1.448378] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    1.456681] CPU: 0 PID: 1 Comm: swapper Not tainted 4.4.0-kirkwood-tld-1 #1
[    1.463670] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[    1.469983] [<c0016784>] (unwind_backtrace) from [<c00129f8>] (show_stack+0x10/0x14)
[    1.477761] [<c00129f8>] (show_stack) from [<c00c2200>] (panic+0x80/0x214)
[    1.484669] [<c00c2200>] (panic) from [<c07d9280>] (mount_block_root+0x204/0x24c)
[    1.492182] [<c07d9280>] (mount_block_root) from [<c07d93b4>] (mount_root+0xec/0x118)
[    1.500047] [<c07d93b4>] (mount_root) from [<c07d9504>] (prepare_namespace+0x124/0x184)
[    1.508086] [<c07d9504>] (prepare_namespace) from [<c07d8e9c>] (kernel_init_freeable+0x208/0x258)
[    1.517002] [<c07d8e9c>] (kernel_init_freeable) from [<c05b16b4>] (kernel_init+0x8/0xe4)
[    1.525127] [<c05b16b4>] (kernel_init) from [<c000f090>] (ret_from_fork+0x14/0x24)
[    1.532730] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Unfortunately i am not able to get all output as i am using my raspi with "sudo screen /dev/ttyAMA0 115200" to get to the console and the first parts are no longer available.

Something i must be doing wrong but couldnt find it yet.

Here is my printenv output:

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:48:40 -0700)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0
NSA325> printenv
ide_rootfstype ext4
arcNumber=4495
baudrate=115200
bootargs=root=/dev/nfs nfsroot=: ip=::::::off
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb ide
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-nsa325.dtb
ethact=egiga0
ethaddr=00:00:00:00:00:00
ide_rootfstype=ext4
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 2715/131068 bytes

Thanks in advance for any hint on that failure.

sascha

Viewing all articles
Browse latest Browse all 903

Latest Images

Trending Articles



Latest Images