I don’t care, but, I remember too, in other threads, you didn’t recommend to flash the nand, and that is the reason I am using an USB key. Right now, there is no stock FW in the nand, just the rescue partition to flash it, but even, there is a chance to boot from usb with a rescue firmware and reflash the nand.by i5Js - Debian
Yes, you could flash the nand,perhaps @bodhi could help here.by i5Js - Debian
Trust me, it was a nightmareby i5Js - Debian
bodhi Wrote: ------------------------------------------------------- > i5Js, > > Do you have another low power ARM board, such as > the rPi? > > I'm curious to know what'll happen if you connect > the serial converter to that ARM board and wired > only GND+RXD+TXD to this EX2 Ultra NAS. I did it: I have used a rPi2, rPi2, MacBook Pro (aluminum) andby i5Js - Debian
I have added some changes. BTW, I bought this and this and both needed the 3.3v connected, without it, I could see the boot process, but I could not type.by i5Js - Debian
bodhi Wrote: ------------------------------------------------------- > Quote** Console: It's a must; you need an FT23RL > USB UART converted. There are a lot on amazon. You > can check this blog for more details (Thanks Nico) > > > ** Minicom for Linux or putty for windows. I have > always used minicom. > > This is really not accurate. You can use anyby i5Js - Debian
bodhi Wrote: ------------------------------------------------------- > Hi i5Js, > > Thanks for writing this up! I will review it for > you. > > But it is annoying to read and quite hard to > follow because the Steps are not in the same post! > There is no good reason for each step to be in a > separate post. No problem, I found the time, so I wrote it. Tby i5Js - Debian
Final words. As I said, it took me over two months to figure it out. While it was frustrating at times, and sometimes I wanted to give up, it's great to see it work. My big thanks go out to Bodhi and Gisab for helping me and teaching me everything to fix my issues. I hope this guide helps, you don't need two months, Let's party!by i5Js - Debian
6.- Open Media Vault. The easy one, follow their instructionsby i5Js - Debian
5.- Kernel and rootfs We are almost there. You only need to follow this bodhi's post Linux Kernel 6.0.7 MVEBU package and Debian armhf rootfs Make the USB key like he says, once it's ready, we can change some envs (Credits to bodhi) setenv usbActive 0 setenv usbType 3 Then let it boot automatically: Marvell>> setenv bootargs "console=ttyS0,115200 root=/dev/sdaby i5Js - Debian
4.- U-Boot. bodhi's note on 12 Apr 2024: While CyberPK's modded u-boot is a good build, this part of the installation need to be a bit more elaborate in the instruction. Please post question if you are installing this box. CyberPK did an incredible job, you can find all the details and the patched version here Basically, the stock u-boot disables saving environment settings, aby i5Js - Debian
3.- Debian Recovery Mode. You don't have to do it, but it's useful if you need to recover your data. You only need to flash this firmware. The stock firmware will be rewritten, so it won't be available. But you'll get a busbox with md tools, telnet, and everything you need to troubleshoot.by i5Js - Debian
2.- Boot from USB The box can be booted with a USB key. Make sure it's in FAT32, and copy these files to the root folder. Connect it to port 2 (very important because using the stock u-boot, port 1 is disabled) and hold the reset button while you turn on the NAS. The console port will show you the boot process. Bonus: If your box is bricked, you can always fix it using this method, buby i5Js - Debian
1.- Serial Console. It's a must. You will need it to debug everything. It was my first pain because I had no skills to solder the wires. Here you can find the pinouts. There are some lessons learned here: 1.- Thanks to Gisab, I realized that a MacBook Pro isn't the best option for working. The noise was a problem, so use a raspberry or a plastic laptop if you're on the saby i5Js - Debian
The guide is the result of two months of work, testing, and failures. There were a lot of thanks during those days, all of this wouldn't be possible without their help, so they deserve credit too. Disclaimer. I'm not responsible if you lose your data, and neither are all the guys in this guide. We're voiding the warranty. What do we need? ** USB key. Always MBR, do not fby i5Js - Debian
Well finally it is complete. I have the box ready an working with OMV 6. And it works great!! I want to thank you Bodhi for all your help, all the time you have spent with me! I will try to write down a guide with all my steps, advices, and of course all my mistakes Perhaps it would take time because the Christmas, family and work, but for sure I will Stay tune Be cool! Besby i5Js - Debian
Quote No need to do all that. You are all done, except for this u-boot envs accessiblity in Debian. I think I need it, now, by default, it boots from tftp.by i5Js - Debian
Hi, Great explanation, thanks, With the custom kernel I can print the env Perhaps I would need to install u-boot tool? Anyway, I think everything is set and working fine. Could you please help me setting the env to boot automatically from USB? I found a guy that seems you helped too, with the following, but I don’t know if they could work with mine setenv set_bootargby i5Js - Debian
I have updated to kernel 6, but not difference. Uncompressing Linux... done, booting the kernel. [ 0.000000][ T0] Booting Linux on physical CPU 0x0 [ 0.000000][ T0] Linux version 6.0.7-mvebu-tld-1 (root@tldDebian) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1.0 SMP PREEMPT Tue Nov 8 16:49:35 PST 2022 [ 0.000000][ T0] CPU: ARMv7 Proceby i5Js - Debian
I guess the leds issue is my fault, because there are no drives connected yet. I don't know why with the other kernel, the leds are on. Anyway, the output root@debian:~# ls -l /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Dec 16 23:32 . drwxr-xr-x 54 root root 0 Dec 16 23:32 .. lrwxrwxrwx 1 root root 0 Dec 16 23:35 wdmcex2u:hdd1:blue -> ../../devices/platform/gpio-leds/ledsby i5Js - Debian
New boot with your stuff: Marvell>> boot (Re)start USB... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found 5236595 bytes read in 458 ms (10.9 MiB/s) 9649885 bytes reaby i5Js - Debian
Hahaha trust me, I have tried, but sometimes when I paste a log, it says the post is too long, but sometimes it’s ok. So I don’t know what’s going on Honestly, I can’t remember if the MAC address was working beforoe, but sure the leds didn’tby i5Js - Debian
one more about zram root@wdnas:/var/log.hdd# zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram2 lzo 500.6M 344K 6.2K 72K 2 /tmp /dev/zram1 lzo 500.6M 4K 76B 4K 2 /dev/zram0 zstd 50M 10.2M 313.6K 676K 2 /var/logby i5Js - Debian
root@wdnas:~# mount /dev/sda1 on / type ext3 (rw,noatime,nodiratime,errors=remount-ro,commit=600) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,noexec,size=4096k,nr_inodes=65536,mode=755) tmpfs on /dev/shm type tmpfs (rw) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpby i5Js - Debian
This time, everything but console-setup service has worked as expected, even the real Mac address and the leds. This custom uses the Armbian ZRAM, to avoid use swap, and to not use the usb for logging. I am not sure, but it write them to the usb (the storage device) when you turn off the board. root@wdnas:~# cat /proc/cmdline console=ttyS0,115200 root=LABEL=rootfs mtdparts=pxa3xx_nand-0:5mby i5Js - Debian
Marvell>> boot (Re)start USB... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found 4523065 bytes read in 453 ms (9.5 MiB/s) 4841674 bytes read in 467 ms (9.9 MiB/s) ## Boby i5Js - Debian
New attempt, using the custom kernel and filesystem from this GitHub (customised for Ex2-Ultra) and new usb key Marvell>> setenv usbActive 0 Marvell>> setenv usbType 3 Marvell>> usb start (Re)start USB... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices..by i5Js - Debian
[ 3.580667] ata1: SATA link down (SStatus 0 SControl 300)by i5Js - Debian
[ 1.932899] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)by i5Js - Debian
dmesg if helps; root@debian:~# dmesgby i5Js - Debian