so final words, I've tryed to change it to md0, doesn't boot now I've deledet mdo and changed only to /dev/sda1 to rootfs and it's booting another question the update to newr kernel doesn't work 2023-06-02 22:48:46 (15.4 MB/s) - 'linux-6.2.8-mvebu-tld-1-bodhi.tar.bz2' saved [37044194/37044194] root@debian:/boot# tar -xjf linux-6.2.8-mvebu-tld-1-bodhi.taby Chris - Debian
herby: U-Boot 2013.01_v1.04 (Apr 19 2020 - 23:10:38) Marvell version: 2014_T3.0p6 mvBoardIdIndexGet(boardId) = 1 Board: GrandTeton DB6820 SoC: MV88F6820 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU @ 1332 L2 @ 666 TClock @ 200 DDR @ 666 DDR 32 Bit Width, FastPath Memory Access, DLB Enabled,by Chris - Debian
done that, root@debian:~# mdadm --assemble --verbose /dev/md1 /dev/sda2 /dev/sdb2 mdadm: looking for devices for /dev/md1 mdadm: /dev/sda2 is identified as a member of /dev/md1, slot 0. mdadm: /dev/sdb2 is identified as a member of /dev/md1, slot 1. mdadm: added /dev/sdb2 to /dev/md1 as 1 mdadm: added /dev/sda2 to /dev/md1 as 0 mdadm: /dev/md1 has been started with 2 drives. root@debianby Chris - Debian
no, he only waited longer till he gave up but as i see the mdadm (RAID) is not started? U-Boot 2013.01_v1.04 (Apr 19 2020 - 23:10:38) Marvell version: 2014_T3.0p6 mvBoardIdIndexGet(boardId) = 1 Board: GrandTeton DB6820 SoC: MV88F6820 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU @ 1332 L2 @ 666 TClock @ 200by Chris - Debian
I'm sorry, here you go U-Boot 2013.01_v1.04 (Apr 19 2020 - 23:10:38) Marvell version: 2014_T3.0p6 mvBoardIdIndexGet(boardId) = 1 Board: GrandTeton DB6820 SoC: MV88F6820 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU @ 1332 L2 @ 666 TClock @ 200 DDR @ 666 DDR 32 Bit Width, FastPath Memoby Chris - Debian
still not working. no need to saveenv ? Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! LABEL=rootfs does not exist. Dropping to a shell! BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash) Enter 'helpby Chris - Debian
this is the bootlog with the usb U-Boot 2013.01_v1.04 (Apr 19 2020 - 23:10:38) Marvell version: 2014_T3.0p6 mvBoardIdIndexGet(boardId) = 1 Board: GrandTeton DB6820 SoC: MV88F6820 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU @ 1332 L2 @ 666 TClock @ 200 DDR @ 666 DDR 32 Bit Width, FastPath Meby Chris - Debian
> > So you want to boot into Debian rootfs on USB > first. Later you can boot with RAID rootfs with a > small change in evns. > > After you can boot into Debian on USB, switching > to boot RAID rootfs is simple. Maybe you could please tell me what are those changes?by Chris - Debian
that's exactly what I did. it boots from the stick but not from the hddby Chris - Debian
> > Yes. You can boot with the kernel files on USB, > and the rootfs on HDD. > so he doesn't boot from HDD RAID md0 only from stick here is the bootlog, maybe you see something what I am missing U-Boot 2013.01_v1.04 (Apr 19 2020 - 23:10:38) Marvell version: 2014_T3.0p6 mvBoardIdIndexGet(boardId) = 1 Board: GrandTeton DB6820 SoC: MV88F6820 Rev A0 runniby Chris - Debian
I've missed the last part. Now it booted. Thanks a lot Bodhi. BR Chrisby Chris - Debian
I've tried this but I use RAID and it does not see md0 Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/md0 does not exist. Dropping to a shell! BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash) Enterby Chris - Debian
Dear Bodhi > > I suggest you read the first 6 posts of this > thread. See if you want to follow how i5Js install > new u-boot so you can boot from USB drive. I know > it's a bit intimidating to read you have to do all > that. But as of now, you cannot upgrade kernel so > you're stuck with 5.11.5. > there are some problems with this description: 1. Iby Chris - Debian
Dear Bodhi, Unfortunately, I can't shrink the initrams because I'm definitely no expert. I'm a beginner and this is no option for me. I wanted only to not boot from USB. But if it's not possible then I will use a Stick no problem. Thank you very much for your help! Is there a way to uninstall the kernel 6 ? Because I have problems installing omv, and I think it isby Chris - Debian
I don't realy remember how I did it. At the begining I booted from USB, then I've found a way to write the boot procces in the NAND so that I don't need the USB. Here is boot log: BootROM - 1.73 Booting from NAND flash General initialization - Version: 1.0.0 Detected Device ID 6820 High speed PHY - Version: 2.0 Load WD GrandTeton Serdes Config: board SerDes lanesby Chris - Debian
BTW, I have 2 HDD in RAID. I need to select from where it should start. md0 is swap md1 is where the kernel/linux is installed md2 is data Avalaible boot options: 1. From encrypted rootfs 2. From custom device (You have 15 seconds for input) Choose boot option (1/2): 2 Enter your device path (i.e. /dev/sdc1): /dev/md1 Trying to boot from /dev/md1... BR Chrisby Chris - Debian
So here the serial output of dmesg right? Linux debian 5.11.5-mvebu-tld-1 #1 SMP PREEMPT Tue Mar 9 14:42:57 MSK 2021 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitby Chris - Debian
Serial not at the moment, I'm not Home. Hereby :) root@debian:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.11.5-mvebu-tld-1 (root@osaserver) (arm-linux-gnueabihf-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP PREEMPT Tue Mar 9 14:42:57 MSK 2021 [ 0.000000] CPU: ARMv7 Processor [414fc091] revisiby Chris - Debian
I’m sorry but for I already restarted my system. So it’s not available anymore root@debian:~# ls -lart /boot total 153120 -rwxr-xr-x 1 root root 5218232 Aug 7 2021 vmlinuz-5.13.8-mvebu-tld-1 -rw-r--r-- 1 root root 205052 Aug 7 2021 config-5.13.8-mvebu-tld-1 -rw-r--r-- 1 root root 4461631 Aug 7 2021 System.map-5.13.8-mvebu-tld-1 -rwxr-xr-x 1 root root 5218232 Aug 7 2by Chris - Debian
Dear Bodhi, I've managed to finish all the steps. But what do I do now with the uImage and uInitrd? After finishing, I still have the old kernel. Thanks!by Chris - Debian