Dear bodhi: I try to do the fourth time to whole new job. 1. do disk_create which used shv's: ox820-sata-uboot.tar.gz. 2. tar -xjf for Latest released rootfs: Debian-4.14.180-oxnas-tld-1-rootfs-bodhi.tar.bz2 (17 May 2020) 3. please see the file tree to confirm that (especially file datetime) root@ubuntu:/media/popo/rootfs# ls -al 總計 96 drwxr-xr-x 21 root root 4096 8月by Popo - Rescue System
bodhi: Also, I would try installing OpenWRT and OMV, maybe even stg202? . I will try any system related to ox820nas. See if you can suggest anything else. Because I can ignore the nand content now. I can boldly try to install any system on this machine. And verify its effect to see if it can be successful. I'd also like to know if other kits have the same issues we have. I also planby Popo - Rescue System
bodhi Wrote: ------------------------------------------------------- > Popo, > > > > > > > So if your MTDs are not what defined in > u-boot > > > envs mtdparts, then there is something wrong. > > You > > > should check uImage to see if it is the > > original > > > (without DTB appended). > > > > > >by Popo - Rescue System
After these three days of research and study. I successfully restored all data in mtd0/mtd1. I will make a note here first, and also give a big warning and pre-processing suggestions to those friends who suddenly cannot mount UBIFS. Of course, this is a very big title that involves UBIFS format knowledge. Fortunately, with the efforts of many people, I found some useful tools and scripts duringby Popo - Rescue System
Hi, Ray : Please refer this post , after you edit this dts file, please use dtc to compile it and replace the file in /boot/dts/ox820-akitio.dtb. dtc -I dts -O dtb ox820-akitio.dts > ox820-akitio.dtb reboot dtc in the device-tree-compiler package, please apt install it first. about RTC, can you see the module to be opened ? grep CONFIG_RTC_DRV_DS1307 config-5.4.224-oxnasby Popo - Rescue System
rayknight Wrote: ------------------------------------------------------- > QuotePopo > BTW, my machine is not DC01. My machine is the > same OEM product as OpenWRT and Ray's machine. > It's just that I don't have the RTC on the > motherboard. > > > Are you sure you have no RTC on the motherboard? > I posted a link to an image of my board whichby Popo - Rescue System
bodhi Wrote: ------------------------------------------------------- > Popo, > > > But everything goes as you said and I am always > > ready to move on to the next phase of my > research. > > MTDs defintiion is still wrong. > > > [ 7.744972] 2 fixed-partitions partitions found > on MTD device 41000000.nand-controller > [ 7.753582] Cby Popo - Rescue System
bodhi Wrote: ------------------------------------------------------- > Quote[ 7.747243] mtd: no closing ) found in > partition name > > OK so that's the problem with the MTD partitions. > Let's play with it a bit > > In serial console, > > setenv mtdparts > 'mtdparts=41000000.nand:39680k(Boot),-(Data)' > printenv > > andby Popo - Rescue System
> > In serial console, > > setenv mtdparts > 'mtdparts=41000000.nand:39680k(Boot),-(Data)' > printenv > > and boot > > boot > Uncompressing Linux... done, booting the kernel. [ 0.000000][ T0] Booting Linux on physical CPU 0x0 [ 0.000000][ T0] Linux version 5.4.224-oxnas-tld-1 (root@tldDebian) (gcc version 10.2.1 20210110by Popo - Rescue System
> ==== > > Question: do you really have anything to copy from > the stock rootfs? or you just want to see if you > can read it? > > If you don't have anything important to save, then > perhaps you should back up this mtd1 with nanddump > (do not use dd), and use flash_erase to > wipe it, and then create a new UBIFS file system > on it. For me,by Popo - Rescue System
Drew Nucci Wrote: ------------------------------------------------------- > Awesome, thank you for the info!!! I'm sorry if I > seem a bit clueless (I am!)... I will try this > tomorrow and see what I can get working... thanks > again for taking the time to explain that to me! I need the original FW to be the last resort to flash my nand. I encountered the same probby Popo - Debian
bodhi Wrote: ------------------------------------------------------- > QuoteI am pretty sure that there is no ubi.ko > module in the Kernel and rootfs packages you > provided on DropBOX. > > Because it is a builtin kernel module > > # grep UBIFS config-5.4.224-oxnas-tld-1 > > CONFIG_UBIFS_FS=y > > > Therefore you have successfully attached it &by Popo - Rescue System
bodhi Wrote: ------------------------------------------------------- > QuoteMy Akitio mycloud mini / DC01(sell by > Silver) motherboard, > it has no battery,no clock , so that I2C initial > module for "dallas,ds1307" will be stuck. > just remove this node from the tree device. > all good for booting. > > Cool! so yours is a variation of the originalby Popo - Rescue System
bodhi Wrote: ------------------------------------------------------- > Stock > > > mtd0: 10000000 00020000 "NAND 256MiB 3,3V 8-bit" > mtd1: 026c0000 00020000 "Boot partition" > mtd2: 0d940000 00020000 "Data Partition" > > > So we change the env > > In serial console: > > setenv mtdparts > 'mtdparts=by Popo - Rescue System
One more thing .. I know that why the kernel stuck at booting when we use ox820-akitio.dtb. i2c-gpio { compatible = "i2c-gpio"; gpios = <0x11 0x09 0x00 0x11 0x0a 0x00>; pinctrl-names = "default"; pinctrl-0 = <0x12>; i2c-gpio,delay-us = <0x0a>; #address-cells = <0x01>; #size-cells = <0x00>; rtc@68 { compatibleby Popo - Rescue System
Finally, I took a little tricky hacking on the device tree OX820 # run ide_set_bootargs OX820 # run dt_bootm ## Booting kernel from Legacy Image at 60500000 ... Image Name: Linux-5.4.224-oxnas-tld-1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5589592 Bytes = 5.3 MiB Load Address: 60008000 Entry Point: 60008000 Verifying Checksum ... OK ## Lby Popo - Rescue System
bodhi I went back and redone everything again, and now I use NFS to mount rootfs for use. The original HDD can only be booted as U-BOOT. And boot to tftp to download uImage/uInitrd/dtb file and then boot, and successfully mount rootfs in NFS mode. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.4.224-oxnas-tld-1 (root@tldDebian) (gcc version 10.2.1 2021011by Popo - Rescue System
Drew Nucci Wrote: ------------------------------------------------------- > Hello, I have also bricked my Akitio mycloud mini. > I am an amature at figuring out hw to use > jtag/uart/spi to flash my rom back to the tsop48 > chip on the board. I have been using a raspberry > pi pico with code installed on it from various > githubs to try and figure out how to flash the &gby Popo - Debian
bodhi , still no more information .... U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - 14:31:34) Boot device: SATA Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020a plla_ctrl1 : 00330000 plla_ctrl2 : 0065008b plla_ctrl3 : 000000f1 PLLA Set Bus 0: OK Device 0: ** File not found /boot/bootargs.bin ** U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18by Popo - Rescue System
new bootargs No more information.... U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - 14:31:34) Boot device: SATA Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020a plla_ctrl1 : 00330000 plla_ctrl2 : 0065008b plla_ctrl3 : 000000f1 PLLA Set Bus 0: OK Device 0: ** File not found /boot/bootargs.bin ** U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18by Popo - Rescue System
> U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - > 14:31:34) > Boot device: SATA > Attempting to set PLLA to 850 MHz ... > plla_ctrl0 : 0000020a > plla_ctrl1 : 00330000 > plla_ctrl2 : 0065008b > plla_ctrl3 : 000000f1 > This could be the source of some of your problems. The Akito MyCloud Mini was designed for 750 MHz, not 850 MHz so this difference could bby Popo - Rescue System
Hi, bodhi : finally, I got 3.0GBps ! this is the 'magic string' in the args to kernel. [ 0.000000][ T0] Kernel command line: root=LABEL=rootfs rootfstype=ext3 console=ttyS0,115200 mem=256M libata.force=3.0G poweroutage=yes elevator=cfq [ 0.000000][ T0] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear) [ 0.000000][ T0] Inode-cache hashby Popo - Rescue System
I see you already have the correct bootargs Yes, this is a good habit. Anyone who is an experienced Linux player knows this. It originated after RedHat 7 or 8 later ? and some say it came from UFS, BSD disklabel (FreeBSD partition tables) support. If grub and fstab still mount the disk according to the old markings, it will cause the system to be unable to boot. BTW, SoC should be able tby Popo - Rescue System
Good work! so far the booting looks good. As long as you can boot with SATA u-boot from HDD raw sector, you have many options. Now you can boot the USB rootfs, too. I suspect the kernel stuck at that point might be because it is too old or becasue the overlock 850Mhz. But I need to look at my notes to see. I'll be back shortly. I try to remove HDD from this box, and plug USB stickby Popo - Rescue System
Hi, bodhi , I appreciate your guidance and help over the past week!! Thank you so much ! I will try to write down the entire process from the accident to the perfect solution during Christmas into a detailed operation step. A complete supplement and update for the Topics I have browsed. After upgrading to Bookworm, I did some restriction testing. First: I noticed that HDD speed ...by Popo - Rescue System
Hi, bodhi : I got some trouble with EXT3 for u-boot. Everytime, after I force shutdown (kernel boot stuck ....kernel panic .....blablabla.....) Next time , I power on , uImage seems load ok , but stuck in 'Uncompressing Linux ........ done, booting the kernel' I must do 'mkimage' or 'copy backup' uImage/uInitrd again . It's very scary! I willby Popo - Rescue System
OK, I had already upgrade to bookworm 12 NOTICE!!! PLEASE REMEMBER Enough Space!!!! root@iSharing:/# df -h Filesystem Size Used Avail Use% Mounted on udev 117M 0 117M 0% /dev tmpfs 25M 248K 24M 2% /run /dev/sda1 7.4G 1.3G 6.2G 17% / tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 49M 0 49M 0% /dev/shm tmpfby Popo - Rescue System
OK, I had already upgrade to bullseye 11.8 root@iSharing:~# cat aptkey apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 605C66F00D6C9793 \ 0E98404D386FA1D9 648ACFD622F3D138 root@iSharing:~# cat /etc/debian_version 11.8 root@iSharing:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VEby Popo - Rescue System
Hi, bodhi : Network now linked to 1Gbps root@iSharing:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports autoby Popo - Rescue System
as my source.list root@iSharing:/etc/apt# cat sources.list deb http://opensource.nchc.org.tw/debian buster main deb-src http://opensource.nchc.org.tw/debian buster main deb http://security.debian.org/debian-security oldstable-security main contrib non-free deb-src http://security.debian.org/debian-security oldstable-security main contrib non-free deb http://opensource.nchc.org.by Popo - Rescue System