Hi, sorry for reply just for a long time, had no time to try fixing. I have recreated rootfs / USB drive based on your instructions, but this time it has problems with the fdt image itself: ## Flattened Device Tree from Legacy Image at 01c00000 Image Name: Linux-5.13.6-kirkwood-tld-1 Created: 2023-09-04 12:50:18 UTC Image Type: ARM Linux Kernel Image (uncompressed)by hpjotr - uBoot
Thanks bodhi, it is solved kernel panic, but still hangs the boot at 'loading essential drivers' stage... NSA310> setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts $custom_params' NSA310> boot starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storaby hpjotr - uBoot
Hi, I have added the boot log: NSA310> boot Reset IDE: ide_preinit failed Partition Map for USB device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUID Type 1 2048 60086272 c418c1ac-01 83 ## Unknown partition table type 0 ## Unknown partition table type 0 ## Unknown partition table type 0 ## Unknown pby hpjotr - uBoot
Hi, thanks, followed guidance but still kernel panic because of root device problems: [ 10.534378][ T1] md: ... autorun DONE. [ 10.538606][ T1] VFS: Cannot open root device "(null)" or unknown-block(0, 0): error -6 [ 10.546877][ T1] Please append a correct "root=" boot option; here are the aby hpjotr - uBoot
Hi, I have followed your guidance, but still has the kernel panic after 'boot' command: [ 10.534378][ T1] md: ... autorun DONE. [ 10.538606][ T1] VFS: Cannot open root device "(null)" or unknown-block(0, 0): error -6 [ 10.546877][ T1] Please append a correct "root=" boot option; here are theby hpjotr - uBoot
Hi David, thanks, I have unplugged SATA HDD, only the USB is connected. changed the environment values, but same hang at boot: NSA310> printenv arcNumber=4022 baudrate=115200 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dby hpjotr - uBoot
Hi, meanwhile I have managed to unbrick the device, so at least uboot works. Created a Debian image (5.2.9) using this guide. The NAS now is trying to boot from the usb Debian, but hangs: NSA310> printenv[ 10.889811][ T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Unknown command 'printenv[' - try 'help' NSA310> [by hpjotr - uBoot
Hi, From a wrong flashing process I was able to unbrick my NSA310 (with another Linux box, loading uboot.kwb via kwboot, UART module cable) I have the console of NSA310> and I am able to load the uboot.kwb, but unable to set up the environment properly (using these files: uboot.2017.07-tld-1.nsa310.mtd0.kwb uboot.kwb uboot.2016.05-tld-1.environment.img uboot.img ) is that possible tby hpjotr - uBoot