Cool! So the single quote was not working correctly with this u-boot. Go ahead and boot into Debian (does not matter which kernel), and cat /proc/cmdline cat /proc/mtdby bodhi - Debian
> I do not understand why It can't detect or mount > the usb... I am not sure why either! it could be the DTS difference. With the good boot: root@wdmycloud:~# cat /proc/cmdline console=ttyS0,115200 root=/dev/sda2 $mtdparts earlyprintk=serial See that the mtdparts variable was not expanded. This u-boot is really worse than I thought. So now to expose the mtdparts in Liby bodhi - Debian
This old u-boot is quite limited. 1. Change the bootargs to: setenv bootargs 'console=ttyS0,115200 root=/dev/sda2 $mtdparts earlyprintk=serial' And boot. Log into Debian, cat /proc/mtd cat /proc/cmdlineby bodhi - Debian
Hi Trond, Excellently done! Thanks for the write up. I'll add eSATA booting to the installation post.by bodhi - Debian
Martin, > First of all: when using stock u-boot with > self-built kernel+initrd ethernet WORKS!!! That's what I expected to see with stock u-boot + the DTS patch! > With your latest patch, which added the regulators > both drives are spinning (I did a ide reset in > u-boot and at that time the SATA2 drive started) > Unfortunately there are still no disks detectby bodhi - Debian
i5Js, It is not because of your built kernel. It is because of this stock u-boot lacks of parsing capability. > It has some improvements, and it seems he plays > with the nand creating more partitions, I guess > for stock kernel and Debian. Anyway, apart of > that, this time, it boots successfully, and it > detects the mtd partitions. Yes, usually you would see the Mby bodhi - Debian
Martin, QuoteI have so far failed to boot debian from stock u-boot. Will have to try more tomorrow. Now that's bad :) I thought I've asked to see Debian booting from stock u-boot, not your built u-boot. So what we observed in the last several tests were not what I was looking for or expected.by bodhi - Debian
i5Js, We'll enable the mtd partitions in Linux so that they are accessible for flashing kernel files. Again, in reference to the successful tftp boot: https://forum.doozan.com/read.php?2,67249,133459#msg-133459 This time change the envs a bit: setenv mtdparts 'mtdparts=pxa3xx_nand-0:5m(u-boot),5m@5m(kernel),5m@10m(uRamdisk),185m@15m(image.cfs),15m@200m(rescue_fw),20m@by bodhi - Debian
zebe, > Are you able to recommend any proven, WORKING > solution to xfce/lxd and vnc link to NSA325 > device? No, I can't recommend any solution, since I set up XFCE/xrdp many years ago just for experiment, and then stopped using it. What we have in the Wiki are also old, so things might have changed with later Debian version.by bodhi - Debian
i5Js, OK. So that proved the Ext2 driver is not working in this u-boot. Your log was not good. It got cut off on the right side, especially the important part (printenv). Please post the printenv output again and make sure that it's legible on your browser.by bodhi - Debian
Martin, > I tested with stock u-boot: > ide reset found the 7200 disk in sata 2. but not > the 5400 drive in sata 1. > > Then I exchanged the two disks: > it found the 5400 disk in sata 2 but not the 7200 > in sata 1. This means Syno u-boot does not power up the SATA 1 slot. So boot into Debian and verify that same SATA 2 slot is actually working. While you arby bodhi - Debian
i5Js, OK. tftp is just a temporary mode of booting. And you have problem with this u-boot regarding USB Ext2 driver. So the next logical thing to do is to boot from NAND. But before I help you with that, I think we need to try a bit more to see if we can get it to boot entirely from USB. And get some info along the way to see where things are on this box. In reference to the successfulby bodhi - Debian
Martin, > - one disk that failed to spin up on any of the > two sata ports alone in both of the ports. This is really weird. If a specific port works for one 3.5" HDD, it should work for another 3.5" HDD. With stock u-boot, can you see both HDDs? ide resetby bodhi - Debian
zebe, > - root account has to be the only ne on NSA325? No > USER account /and sudo additonally/ needed > eventually ? It is a headless NAS, i.e like a Ubuntu/Mint Linux system without a display. So yes, a normal user account should be created and used for daily stuff. OTOH, you should be root user while hacking, installing the system.by bodhi - Debian
i5Js, Let recap where you are, and why you have to boot a certain way (tftp, USB, SATA,...) and which kernel. And post serial boot log, too.by bodhi - Debian
i5Js, > I found why it was not working with the kernel 6, > it was the kernel config. In what way? > The sizes are perfect for the nand. @bodhi, any > tip to flash it? This is a NAS box, so you would want to update your kernel often. I always try to discourage people from storing kernel files in NAND. You dont really gain much using this approach. The exception isby bodhi - Debian
> 1) Is there on Debian anything eg like default > Zyxel's Web GUI to such devices? Not that I know off. > 2) Default root's password - 'root' can be altered > or MUST BE such ? Immediately after the 1st boot, change the root password to a strong password.by bodhi - Debian
Hi Schnee, > The problem is when I try to mount the NAND as > JFFS2 filesystem example > > mount -t jffs2 /dev/mtdblock1 > > I get the error that it is unknown file system. I see. Yes, JFFS2 has been not configured into this kernel (a long time ago, it was in). I think I might have removed it when there was a problem with the kernel size when we were booting witby bodhi - Debian
Martin, Try this patch to see if both SATA drives will be brought up.by bodhi - Debian
zebe, > OK, we re home. Working )) Cool! > > Only xfce4 via VNC does not seem to cooperate and > buttons/leds/beeps would need some fine tuning... > > Btw Can you recommend any working-proven > OpenMediaVault wiki ?? > or maybe NFS/CIFS wiki to have disk shares > auto-visible upon pluggin to LAN? /Linux/PC/ You can find the answers in the Wiki threaby bodhi - Debian
Daven McCalla, > I'm seeing a similar problem, where u-boot thinks > directories are empty that are not empty. Is this > a known issue with a known resolution? Yes. It mentioned in the rootfs release thread. Quote1. Format a new USB drive with a single Ext3 partition, and label it rootfs. If you are running the latest U-Boot for Kirkwood then you can use Ext4. But be awarby bodhi - uBoot
ix2USER, Boot again. This time interrupt serial console and get the listing of the envs. printenv And then continue to boot like you did before. Capture this entire serial console log and post here. Your log above did not have any line breaks so it is quite difficult to read. If you are using a Linux terminal, just highlight the text in the terminal and then copy and paste it to thby bodhi - Debian
Hi Trond, > Following you advice, I successfully did a first > install of Debian using > 'linux-5.19.2-mvebu-370xp-tld-1-bodhi.tar.bz2'. > The log is attached for reference. Thanks! I'll update the instruction to reflect that. > Bad block table found at page 65472, version 0x01 > Bad block table found at page 65408, version 0x01 > nand_read_bbt:by bodhi - Debian
i5Js , > Perhaps because I was not using the K6 uRamdisk?? Perhaps! try kernel 6.0.7 initramfs (you are booting a much newer Debian rootfs on USB than that ramdisk).by bodhi - Debian
Cool! Don't know when the new LTS kernel 6.x will be released (probably January). I might go for broke and try that :) OXNAS is well maintained now in mainline.by bodhi - uBoot
How to clone USB rootfs to SATA rootfs. 1. Backup your current USB rootfs on another Linux box using this backup/restore instruction: https://forum.doozan.com/read.php?2,12096,24034#msg-24034 And copy the backup tarball my-rootfs.tar.bz2 to the USB rootfs /boot folder. Sync, umount, and remove this USB rootfs. 2. Boot the box with the USB rootfs. And then plug in the HDD if it isby bodhi - Debian
zebe, > Just pulled out HDD and booting primary USB and > SSH link works...and hot-plugging HDD also maps > hdd partitions to /dev/sdb so... Yes, that was because the kernel on USB was used, but the mounted rootfs was still the HDD rootfs. So after you removed the HDD, the USB rootfs was mounted, and everything works. > Btw. Adjusting LEDS&beeps: in proper *.conf therby bodhi - Debian
Hi Trond, Sorry, looks like I've removed it by mistake while pugrging old files on my Dropbox. Please try using linux-5.19.2-mvebu-370xp-tld-1-bodhi.tar.bz2 (replace 5.8.5 with 5.19.2 in the instruction). It should work the same way.by bodhi - Debian
i5Js, Congrats! Now try tftp the umage from kernel 6.0.7-mvebu-tld-1 Quotehttps://forum.doozan.com/read.php?2,32146 Updated 09 Nov 2022: Kernel 6.0.7-mvebu-tld-1 package has been uploaded. and boot the same way.by bodhi - Debian
Martin, What type of HDD for disk 1 and 2? 2.5", or 3.5" HDD?by bodhi - Debian