Search the Community

Showing results for tags 'emmc'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
  • Community/Newbie forums
    • Board does not start
    • Off-topic
    • Reviews, Tutorials, Hardware hacks
    • Help wanted
    • TV boxes
  • Hobbyists forums
    • P2P help
    • Feature Requests
  • Bug tracker - supported boards and images only
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner A64, H5, H6 and H616
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Board Bring Up
    • Armbian Project Administration
    • Development
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android fanboys's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues
  • Kobol Forum's Helios4
  • Kobol Forum's Helios64

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Location


Interests

Found 5 results

  1. Hi together, iam realy desperate and hope someone can help me with my problem. I think something crashed while I disconnected the USB-Cable in U-Boot Mode with helios64. Now Iam not able to see my m.2 SATA SSD in U-Boot Mode as USB Storage in my PC. I use the U-Boot mode from a SD-Card with a boot image. When I start some armbian System from SD-Card the m.2 SSD is visible and ready to use. I dont know what kind of logs do you need for my Problem. Sorry for that. :-( The only thing I want to do is to use my SATA m.2 SSD as armbian system drive with OpenMediaVault again. best regards sommer11 Infos to my device: https://wiki.kobol.io/helios64/intro/ SD-Card Image for U-Boot Mode: https://wiki.kobol.io/helios64/files/u-boot/helios64_sdcard_u-boot-only.img.xz
  2. Hello everyone, I’m starting this message by apologizing for my poor English (I am French) and also by informing you that I am a newbie with Linux. I have a big problem with my NAS Helios64. At first, I thought this problem was caused by OMV. So I went to the OMV forum to explain my situation. I created the following topic: https://forum.openmediavault.org/index.php?thread/40252-many-problems-after-an-update/&pageNo=1 . There, a kind moderator (macom) asked me to enter some instructions to try to pinpoint the root of the problem. After giving him some outputs, he told me: "For me it looks like your SD card is dead." My installation is not on an SD card but on the eMMC chip of the Helios64. (I followed the Kobol wiki instructions exactly from here : https://wiki.kobol.io/helios64/install/emmc/ ) After that, my NAS has become unreachable. I can no longer log into the OMV Dashboard. I cannot reach the NAS by SSH either. I can just tell you that all the LED lights on the NAS are solid blue. No red diode on. Is the eMMC chip of my NAS dead? Is there a solution that would prevent me from losing all the data stored on the hard drives? (They are in RAID1 and they are encrypted with the OMV LUKS encryption plugin) (I have not made a data backup elsewhere ... I know, big mistake!) I thank in advance all those who will take the time to help me.
  3. Hello there! I'm trying to boot from USB using Armbian, specifically LibreELEC, but it doesn't boot, it boots to Armbian, Armbian detects the USB but when i disconnect it and I connect it again, it turns off then turn on but to Armbian again The thing is, how can I boot from USB? Or how can I boot or install LibreELEC/CoreELEC while having Armbian on the eMMC?
  4. Hi guys, thanks in advance for helping. I flashed a usb (32G Lexar) with the image Armbian_20.10_Arm-64_buster_current_5.9.0.img.xz Next I booted up via the "Update&Backup" on a T95K Pro based on Amlogic S912 with 16G of internal storage and 2G of ram. After apt-get update and apt-get upgrade I decided to move Armbian from the USB to the internal storage (emmc) So I ran the file "install-aml.sh" getting this output: Start script create MBR and filesystem /dev/mmcblk0 Start backup u-boot default 4+0 records in 4+0 records out 4194304 bytes (4.2 MB, 4.0 MiB) copied, 4.45454 s, 942 kB/s Start create MBR and partittion Start restore u-boot 442+0 records in 442+0 records out 442 bytes copied, 0.00476152 s, 92.8 kB/s 8191+0 records in 8191+0 records out 4193792 bytes (4.2 MB, 4.0 MiB) copied, 0.177546 s, 23.6 MB/s Done Start copy system for eMMC. Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24) done. Cppying BOOT...cp: error writing '/ddbr/install/zImage': No space left on device done. Edit init config...sed: couldn't flush /ddbr/install/extlinux/sedVudiPh: No space left on device done. done. Formatting ROOT partition... /dev/mmcblk0p2 contains a ext4 file system labelled 'ROOT_EMMC' last mounted on /ddbr/install on Sun Jul 4 17:10:59 2021 e2fsck 1.44.5 (15-Dec-2018) ROOT_EMMC: clean, 11/863264 files, 80826/3447552 blocks done. Copying ROOTFS. Copy BIN Create DEV Copy ETC Copy HOME Copy LIB Copy LIB64 Create MEDIA Create MNT Copy OPT Create PROC Copy ROOT Create RUN Copy SBIN Copy SELINUX Copy SRV Create SYS Create TMP Copy USR Copy VAR Copy fstab ******************************************* Complete copy OS to eMMC ******************************************* This is the output of lsdisk after running the script root@armbian:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 1 29.8G 0 disk |-sda1 8:1 1 512M 0 part /boot `-sda2 8:2 1 29G 0 part / mmcblk0 179:0 0 14.6G 0 disk |-mmcblk0p1 179:1 0 488M 0 part `-mmcblk0p2 179:2 0 13.2G 0 part mmcblk0boot0 179:32 0 4M 1 disk mmcblk0boot1 179:64 0 4M 1 disk zram0 254:0 0 50M 0 disk /var/log zram1 254:1 0 929.2M 0 disk [SWAP] However, after shutdown system and powered it up without the usb I get the following output: U-Boot 2020.07-dirty (Jul 26 2020 - 13:24:26 +0200) hexdump-gxl Model: hexdump usbkbd/hdmi u-boot gxl SoC: Amlogic Meson GXM (S912) Revision 22:a (82:2) Net: eth0 ethernet@c9410000 starting USB... Bus dwx3@c9000000: Register 3000140 NbrPorts 3 Starting the controller USB XHCI 1.00 scanning bus dwx3@c9000000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage device(s) found ## Error insterting "stdin" variable, errno=22 Card did not respond to voltage select! Card did not respond to voltage select! ** No partition table - mmc 1 ** ** No partition table - mmc 1 ** Hit any key to stop autoboot: [3-2-1-0] Card did not respond to voltage select! switch to partitions #0, OK mmc1 is current device ** No partition table - mmc 1 ** MMC Device 2 not found no mmc device at solt 2 Device 0: unknown device ethernet@c9410000 Waiting for PHY auto negotiation to complete........ TIMEOUT! Could not initialize PHY ethernet@c9410000 missing enviroment variable: pxeuuid missing enviroment variable: bootfile Retrieving file: pxelinux.cfg/00000000 *** COMMENT *** LOOPING OVER THESE 6 LINES TO INFINITY *** If I boot up with the usb inserted it goes fine, without it no. Output of ls -ls /dev/ root@armbian:/# ls dev -ls total 0 0 crw-r--r-- 1 root root 10, 235 Jul 4 17:41 autofs 0 drwxr-xr-x 2 root root 740 Jul 4 17:41 block 0 drwxr-xr-x 2 root root 60 Jan 1 1970 bsg 0 crw-rw---- 1 root disk 10, 234 Jul 4 17:41 btrfs-control 0 drwxr-xr-x 3 root root 60 Jan 1 1970 bus 0 crw-rw---- 1 root video 251, 0 Jul 4 17:41 cec0 0 crw-rw---- 1 root video 251, 1 Jul 4 17:41 cec1 0 drwxr-xr-x 2 root root 3620 Jul 4 17:42 char 0 crw------- 1 root root 5, 1 Jul 4 17:52 console 0 crw------- 1 root root 10, 60 Jul 4 17:41 cpu_dma_latency 0 crw------- 1 root root 10, 203 Jul 4 17:41 cuse 0 drwxr-xr-x 7 root root 140 Jan 1 1970 disk 0 drwxr-xr-x 2 root root 80 Jan 1 1970 dma_heap 0 drwxr-xr-x 3 root root 120 Jul 4 17:41 dri 0 crw-rw---- 1 root video 29, 0 Jul 4 17:41 fb0 0 crw-rw---- 1 root video 29, 1 Jul 4 17:41 fb1 0 lrwxrwxrwx 1 root root 13 Jan 1 1970 fd -> /proc/self/fd 0 crw-rw-rw- 1 root root 1, 7 Jul 4 17:41 full 0 crw-rw-rw- 1 root root 10, 229 Jul 4 17:41 fuse 0 crw------- 1 root root 254, 0 Jul 4 17:41 gpiochip0 0 crw------- 1 root root 254, 1 Jul 4 17:41 gpiochip1 0 drwxr-xr-x 2 root root 0 Feb 14 2019 hugepages 0 crw------- 1 root root 10, 183 Jul 4 17:41 hwrng 0 crw------- 1 root root 89, 0 Jul 4 17:41 i2c-0 0 crw------- 1 root root 89, 1 Jul 4 17:41 i2c-1 0 crw------- 1 root root 248, 0 Jul 4 17:41 iio:device0 0 lrwxrwxrwx 1 root root 12 Jul 4 17:41 initctl -> /run/initctl 0 drwxr-xr-x 3 root root 140 Jul 4 17:41 input 0 crw-r--r-- 1 root root 1, 11 Jul 4 17:41 kmsg 0 crw-rw---- 1 root video 238, 0 Jul 4 17:41 lirc0 0 lrwxrwxrwx 1 root root 28 Feb 14 2019 log -> /run/systemd/journal/dev-log 0 crw-rw---- 1 root disk 10, 237 Jul 4 17:41 loop-control 0 brw-rw---- 1 root disk 7, 0 Jul 4 17:41 loop0 0 brw-rw---- 1 root disk 7, 1 Jul 4 17:41 loop1 0 brw-rw---- 1 root disk 7, 2 Jul 4 17:41 loop2 0 brw-rw---- 1 root disk 7, 3 Jul 4 17:41 loop3 0 brw-rw---- 1 root disk 7, 4 Jul 4 17:41 loop4 0 brw-rw---- 1 root disk 7, 5 Jul 4 17:41 loop5 0 brw-rw---- 1 root disk 7, 6 Jul 4 17:41 loop6 0 brw-rw---- 1 root disk 7, 7 Jul 4 17:41 loop7 0 drwxr-xr-x 2 root root 60 Jul 4 17:41 mapper 0 crw-r----- 1 root kmem 1, 1 Jul 4 17:41 mem 0 brw-rw---- 1 root disk 179, 0 Jul 4 17:41 mmcblk0 0 brw-rw---- 1 root disk 179, 32 Jul 4 17:41 mmcblk0boot0 0 brw-rw---- 1 root disk 179, 64 Jul 4 17:41 mmcblk0boot1 0 brw-rw---- 1 root disk 179, 1 Jul 4 17:41 mmcblk0p1 0 brw-rw---- 1 root disk 179, 2 Jul 4 17:41 mmcblk0p2 0 crw------- 1 root root 241, 0 Jul 4 17:41 mmcblk0rpmb 0 drwxrwxrwt 2 root root 40 Jan 1 1970 mqueue 0 drwxr-xr-x 2 root root 60 Jul 4 17:41 net 0 crw-rw-rw- 1 root root 1, 3 Jul 4 17:41 null 0 crw------- 1 root root 10, 62 Jul 4 17:41 nvme-fabrics 0 crw-r----- 1 root kmem 1, 4 Jul 4 17:41 port 0 crw------- 1 root root 108, 0 Jul 4 17:41 ppp 0 crw-rw-rw- 1 root tty 5, 2 Jul 4 17:54 ptmx 0 drwxr-xr-x 2 root root 0 Jan 1 1970 pts 0 crw------- 1 root root 2, 0 Jul 4 17:41 ptyp0 0 crw------- 1 root root 2, 1 Jul 4 17:41 ptyp1 0 crw------- 1 root root 2, 2 Jul 4 17:41 ptyp2 0 crw------- 1 root root 2, 3 Jul 4 17:41 ptyp3 0 crw------- 1 root root 2, 4 Jul 4 17:41 ptyp4 0 crw------- 1 root root 2, 5 Jul 4 17:41 ptyp5 0 crw------- 1 root root 2, 6 Jul 4 17:41 ptyp6 0 crw------- 1 root root 2, 7 Jul 4 17:41 ptyp7 0 crw------- 1 root root 2, 8 Jul 4 17:41 ptyp8 0 crw------- 1 root root 2, 9 Jul 4 17:41 ptyp9 0 crw------- 1 root root 2, 10 Jul 4 17:41 ptypa 0 crw------- 1 root root 2, 11 Jul 4 17:41 ptypb 0 crw------- 1 root root 2, 12 Jul 4 17:41 ptypc 0 crw------- 1 root root 2, 13 Jul 4 17:41 ptypd 0 crw------- 1 root root 2, 14 Jul 4 17:41 ptype 0 crw------- 1 root root 2, 15 Jul 4 17:41 ptypf 0 brw-rw---- 1 root disk 1, 0 Jul 4 17:41 ram0 0 brw-rw---- 1 root disk 1, 1 Jul 4 17:41 ram1 0 brw-rw---- 1 root disk 1, 10 Jul 4 17:41 ram10 0 brw-rw---- 1 root disk 1, 11 Jul 4 17:41 ram11 0 brw-rw---- 1 root disk 1, 12 Jul 4 17:41 ram12 0 brw-rw---- 1 root disk 1, 13 Jul 4 17:41 ram13 0 brw-rw---- 1 root disk 1, 14 Jul 4 17:41 ram14 0 brw-rw---- 1 root disk 1, 15 Jul 4 17:41 ram15 0 brw-rw---- 1 root disk 1, 2 Jul 4 17:41 ram2 0 brw-rw---- 1 root disk 1, 3 Jul 4 17:41 ram3 0 brw-rw---- 1 root disk 1, 4 Jul 4 17:41 ram4 0 brw-rw---- 1 root disk 1, 5 Jul 4 17:41 ram5 0 brw-rw---- 1 root disk 1, 6 Jul 4 17:41 ram6 0 brw-rw---- 1 root disk 1, 7 Jul 4 17:41 ram7 0 brw-rw---- 1 root disk 1, 8 Jul 4 17:41 ram8 0 brw-rw---- 1 root disk 1, 9 Jul 4 17:41 ram9 0 crw-rw-rw- 1 root root 1, 8 Jul 4 17:41 random 0 drwxr-xr-x 2 root root 60 Jan 1 1970 raw 0 crw-rw-r-- 1 root netdev 10, 242 Jul 4 17:42 rfkill 0 brw-rw---- 1 root disk 8, 0 Jul 4 17:41 sda 0 brw-rw---- 1 root disk 8, 1 Jul 4 17:41 sda1 0 brw-rw---- 1 root disk 8, 2 Jul 4 17:41 sda2 0 crw-rw---- 1 root disk 21, 0 Jul 4 17:41 sg0 0 drwxrwxrwt 2 root root 40 Feb 14 2019 shm 0 crw------- 1 root root 10, 231 Jul 4 17:41 snapshot 0 drwxr-xr-x 3 root root 140 Jul 4 17:41 snd 0 lrwxrwxrwx 1 root root 15 Jan 1 1970 stderr -> /proc/self/fd/2 0 lrwxrwxrwx 1 root root 15 Jan 1 1970 stdin -> /proc/self/fd/0 0 lrwxrwxrwx 1 root root 15 Jan 1 1970 stdout -> /proc/self/fd/1 0 crw-rw-rw- 1 root tty 5, 0 Jul 4 17:41 tty 0 crw--w---- 1 root tty 4, 0 Jul 4 17:41 tty0 0 crw--w---- 1 root tty 4, 1 Jul 4 17:52 tty1 0 crw--w---- 1 root tty 4, 10 Jul 4 17:41 tty10 0 crw--w---- 1 root tty 4, 11 Jul 4 17:41 tty11 0 crw--w---- 1 root tty 4, 12 Jul 4 17:41 tty12 0 crw--w---- 1 root tty 4, 13 Jul 4 17:41 tty13 0 crw--w---- 1 root tty 4, 14 Jul 4 17:41 tty14 0 crw--w---- 1 root tty 4, 15 Jul 4 17:41 tty15 0 crw--w---- 1 root tty 4, 16 Jul 4 17:41 tty16 0 crw--w---- 1 root tty 4, 17 Jul 4 17:41 tty17 0 crw--w---- 1 root tty 4, 18 Jul 4 17:41 tty18 0 crw--w---- 1 root tty 4, 19 Jul 4 17:41 tty19 0 crw--w---- 1 root tty 4, 2 Jul 4 17:41 tty2 0 crw--w---- 1 root tty 4, 20 Jul 4 17:41 tty20 0 crw--w---- 1 root tty 4, 21 Jul 4 17:41 tty21 0 crw--w---- 1 root tty 4, 22 Jul 4 17:41 tty22 0 crw--w---- 1 root tty 4, 23 Jul 4 17:41 tty23 0 crw--w---- 1 root tty 4, 24 Jul 4 17:41 tty24 0 crw--w---- 1 root tty 4, 25 Jul 4 17:41 tty25 0 crw--w---- 1 root tty 4, 26 Jul 4 17:41 tty26 0 crw--w---- 1 root tty 4, 27 Jul 4 17:41 tty27 0 crw--w---- 1 root tty 4, 28 Jul 4 17:41 tty28 0 crw--w---- 1 root tty 4, 29 Jul 4 17:41 tty29 0 crw--w---- 1 root tty 4, 3 Jul 4 17:41 tty3 0 crw--w---- 1 root tty 4, 30 Jul 4 17:41 tty30 0 crw--w---- 1 root tty 4, 31 Jul 4 17:41 tty31 0 crw--w---- 1 root tty 4, 32 Jul 4 17:41 tty32 0 crw--w---- 1 root tty 4, 33 Jul 4 17:41 tty33 0 crw--w---- 1 root tty 4, 34 Jul 4 17:41 tty34 0 crw--w---- 1 root tty 4, 35 Jul 4 17:41 tty35 0 crw--w---- 1 root tty 4, 36 Jul 4 17:41 tty36 0 crw--w---- 1 root tty 4, 37 Jul 4 17:41 tty37 0 crw--w---- 1 root tty 4, 38 Jul 4 17:41 tty38 0 crw--w---- 1 root tty 4, 39 Jul 4 17:41 tty39 0 crw--w---- 1 root tty 4, 4 Jul 4 17:41 tty4 0 crw--w---- 1 root tty 4, 40 Jul 4 17:41 tty40 0 crw--w---- 1 root tty 4, 41 Jul 4 17:41 tty41 0 crw--w---- 1 root tty 4, 42 Jul 4 17:41 tty42 0 crw--w---- 1 root tty 4, 43 Jul 4 17:41 tty43 0 crw--w---- 1 root tty 4, 44 Jul 4 17:41 tty44 0 crw--w---- 1 root tty 4, 45 Jul 4 17:41 tty45 0 crw--w---- 1 root tty 4, 46 Jul 4 17:41 tty46 0 crw--w---- 1 root tty 4, 47 Jul 4 17:41 tty47 0 crw--w---- 1 root tty 4, 48 Jul 4 17:41 tty48 0 crw--w---- 1 root tty 4, 49 Jul 4 17:41 tty49 0 crw--w---- 1 root tty 4, 5 Jul 4 17:41 tty5 0 crw--w---- 1 root tty 4, 50 Jul 4 17:41 tty50 0 crw--w---- 1 root tty 4, 51 Jul 4 17:41 tty51 0 crw--w---- 1 root tty 4, 52 Jul 4 17:41 tty52 0 crw--w---- 1 root tty 4, 53 Jul 4 17:41 tty53 0 crw--w---- 1 root tty 4, 54 Jul 4 17:41 tty54 0 crw--w---- 1 root tty 4, 55 Jul 4 17:41 tty55 0 crw--w---- 1 root tty 4, 56 Jul 4 17:41 tty56 0 crw--w---- 1 root tty 4, 57 Jul 4 17:41 tty57 0 crw--w---- 1 root tty 4, 58 Jul 4 17:41 tty58 0 crw--w---- 1 root tty 4, 59 Jul 4 17:41 tty59 0 crw--w---- 1 root tty 4, 6 Jul 4 17:41 tty6 0 crw--w---- 1 root tty 4, 60 Jul 4 17:41 tty60 0 crw--w---- 1 root tty 4, 61 Jul 4 17:41 tty61 0 crw--w---- 1 root tty 4, 62 Jul 4 17:41 tty62 0 crw--w---- 1 root tty 4, 63 Jul 4 17:41 tty63 0 crw--w---- 1 root tty 4, 7 Jul 4 17:41 tty7 0 crw--w---- 1 root tty 4, 8 Jul 4 17:41 tty8 0 crw--w---- 1 root tty 4, 9 Jul 4 17:41 tty9 0 crw--w---- 1 root tty 244, 0 Jul 4 17:52 ttyAML0 0 crw-rw---- 1 root dialout 4, 64 Jul 4 17:41 ttyS0 0 crw-rw---- 1 root dialout 4, 65 Jul 4 17:41 ttyS1 0 crw--w---- 1 root tty 4, 66 Jul 4 17:41 ttyS2 0 crw-rw---- 1 root dialout 4, 67 Jul 4 17:41 ttyS3 0 crw-rw---- 1 root dialout 4, 68 Jul 4 17:41 ttyS4 0 crw------- 1 root root 3, 0 Jul 4 17:41 ttyp0 0 crw------- 1 root root 3, 1 Jul 4 17:41 ttyp1 0 crw------- 1 root root 3, 2 Jul 4 17:41 ttyp2 0 crw------- 1 root root 3, 3 Jul 4 17:41 ttyp3 0 crw------- 1 root root 3, 4 Jul 4 17:41 ttyp4 0 crw------- 1 root root 3, 5 Jul 4 17:41 ttyp5 0 crw------- 1 root root 3, 6 Jul 4 17:41 ttyp6 0 crw------- 1 root root 3, 7 Jul 4 17:41 ttyp7 0 crw------- 1 root root 3, 8 Jul 4 17:41 ttyp8 0 crw------- 1 root root 3, 9 Jul 4 17:41 ttyp9 0 crw------- 1 root root 3, 10 Jul 4 17:41 ttypa 0 crw------- 1 root root 3, 11 Jul 4 17:41 ttypb 0 crw------- 1 root root 3, 12 Jul 4 17:41 ttypc 0 crw------- 1 root root 3, 13 Jul 4 17:41 ttypd 0 crw------- 1 root root 3, 14 Jul 4 17:41 ttype 0 crw------- 1 root root 3, 15 Jul 4 17:41 ttypf 0 crw------- 1 root root 10, 239 Jul 4 17:41 uhid 0 crw------- 1 root root 10, 223 Jul 4 17:41 uinput 0 crw------- 1 root root 10, 61 Jul 4 17:41 uleds 0 crw-rw-rw- 1 root root 1, 9 Jul 4 17:41 urandom 0 drwxr-xr-x 3 root root 60 Jul 4 17:41 v4l 0 crw-rw---- 1 root tty 7, 0 Jul 4 17:41 vcs 0 crw-rw---- 1 root tty 7, 1 Jul 4 17:41 vcs1 0 crw-rw---- 1 root tty 7, 2 Jul 4 17:41 vcs2 0 crw-rw---- 1 root tty 7, 3 Jul 4 17:41 vcs3 0 crw-rw---- 1 root tty 7, 4 Jul 4 17:41 vcs4 0 crw-rw---- 1 root tty 7, 5 Jul 4 17:41 vcs5 0 crw-rw---- 1 root tty 7, 6 Jul 4 17:41 vcs6 0 crw-rw---- 1 root tty 7, 128 Jul 4 17:41 vcsa 0 crw-rw---- 1 root tty 7, 129 Jul 4 17:41 vcsa1 0 crw-rw---- 1 root tty 7, 130 Jul 4 17:41 vcsa2 0 crw-rw---- 1 root tty 7, 131 Jul 4 17:41 vcsa3 0 crw-rw---- 1 root tty 7, 132 Jul 4 17:41 vcsa4 0 crw-rw---- 1 root tty 7, 133 Jul 4 17:41 vcsa5 0 crw-rw---- 1 root tty 7, 134 Jul 4 17:41 vcsa6 0 crw-rw---- 1 root tty 7, 64 Jul 4 17:41 vcsu 0 crw-rw---- 1 root tty 7, 65 Jul 4 17:41 vcsu1 0 crw-rw---- 1 root tty 7, 66 Jul 4 17:41 vcsu2 0 crw-rw---- 1 root tty 7, 67 Jul 4 17:41 vcsu3 0 crw-rw---- 1 root tty 7, 68 Jul 4 17:41 vcsu4 0 crw-rw---- 1 root tty 7, 69 Jul 4 17:41 vcsu5 0 crw-rw---- 1 root tty 7, 70 Jul 4 17:41 vcsu6 0 drwxr-xr-x 2 root root 60 Jan 1 1970 vfio 0 crw------- 1 root root 10, 63 Jul 4 17:41 vga_arbiter 0 crw------- 1 root root 10, 137 Jul 4 17:41 vhci 0 crw-rw---- 1 root video 81, 0 Jul 4 17:41 video0 0 crw------- 1 root root 10, 130 Jul 4 17:41 watchdog 0 crw------- 1 root root 246, 0 Jul 4 17:41 watchdog0 0 crw-rw-rw- 1 root root 1, 5 Jul 4 17:41 zero 0 brw-rw---- 1 root disk 254, 0 Jul 4 17:41 zram0 0 brw-rw---- 1 root disk 254, 1 Jul 4 17:41 zram1 0 brw-rw---- 1 root disk 254, 2 Jul 4 17:41 zram2 Any help is really appreciated. Lorenzo (Italy)
  5. Hello, everyone! I have an S905M device (Sumavision Q5, RAM:1G, ROM:8G), I made a bootable USB with an Armbian image( ARMBIAN 5.44 user-built Ubuntu 18.04.5 LTS 3.14.29, use gxbb_p201.dtb file ) . I want to use "ddbr" then “b” to make a backup of the EMMC. However, root@SumavisionQ5:~# ddbr DO YOU WANT TO BACKUP OR RESTORE ? BACKUP=(b) RESTORE=(r) b UNABLE TO FIND ANY EMMC OR SD DRIVES ON THIS SYSTEM!!! then I use command "lsblk", I found all partitions(cache, params, ... , data) of the internal storage (8G ROM) for andriod system are treated as seperated disks as shown below: root@SumavisionQ5:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 1 14.9G 0 disk |-sda1 8:1 1 128M 0 part /boot `-sda2 8:2 1 14.6G 0 part / cache 250:0 0 512M 0 disk params 250:1 0 64M 0 disk logo 250:2 0 32M 0 disk recovery 250:3 0 32M 0 disk rsv 250:4 0 8M 0 disk tee 250:5 0 8M 0 disk crypt 250:6 0 32M 0 disk misc 250:7 0 32M 0 disk instaboot 250:8 0 512M 0 disk boot 250:9 0 32M 0 disk system 250:10 0 1G 0 disk data 250:11 0 4.9G 0 disk zram0 253:0 0 100.9M 0 disk [SWAP] zram1 253:1 0 100.9M 0 disk [SWAP] zram2 253:2 0 100.9M 0 disk [SWAP] zram3 253:3 0 100.9M 0 disk [SWAP] use armbianmonitor -u, a detail info is uploaded in http://ix.io/2vPI From that, I find something the 8G ROM is in NAND instead of in EMMC : [ 6.263857] nandphy: Nand PHY Ver:XXX.XXX.001.0006 (c) 2013 Amlogic Inc. [ 6.270503] nandphy: ######STS IRQ mode for nand driver [ 6.275794] nandphy: NAND device id: 2c 64 44 4b a9 0 0 0 [ 6.281261] nandphy: detect NAND device: B revision NAND 8GiB MT29F64G08CBABA [ 6.340701] nandphy: clk_reg = 81000244 [ 6.343380] nandphy: bus_c=6,bus_t=7,sys=4.0ns,T_REA=16,T_RHOH=15 [ 6.347931] nandphy: new oob mode [ 6.352301] nandphy: NAND CKECK:arg nbbt:arg_valid=1,blk_addr=5,page_addr=0 [ 6.361720] nandphy: NAND CKECK:arg ncnf:arg_valid=1,blk_addr=4,page_addr=0 [ 6.382065] nandphy: NAND CKECK:arg phyp:arg_valid=1,blk_addr=8,page_addr=1 [ 6.402285] nandphy: NAND CKECK:arg nkey:arg_valid=1,blk_addr=9,page_addr=0 [ 6.432194] nandphy: NAND CKECK:arg ndtb:arg_valid=1,blk_addr=7,page_addr=33 [ 6.462225] nandphy: NAND CKECK:arg nenv:arg_valid=1,blk_addr=10,page_addr=9 [ 6.469413] nandphy: nfboot : [ 6.472338] nandphy: off:0x000000000000-0x000000800000 :partn=0:single_chip single_plane [ 6.478386] nandphy: nfcache : [ 6.481817] nandphy: off:0x000006800000-0x000029000000 :partn=2:single_chip multi_plane [ 6.489940] nandphy: nfcode : [ 6.493390] nandphy: off:0x00002f800000-0x000077000000 :partn=9:single_chip multi_plane [ 6.501481] nandphy: nfdata : [ 6.504948] nandphy: off:0x0000a6800000-0x000159800000 :partn=1:single_chip multi_plane How I can do it? Could command “ddbr” make a backup of NAND flash? OK! As far as I know,command “ddbr” can not make a backup of a andriod system in NAND flash. ________________________________________ Background................................................... I also have a device (Tianyi, TY1208-Z, RAM:1G, ROM:8G) with S905L, and I have successfully made a backup file of EMMC. The EMMC is normally recognised as shown below: root@aml:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0 179:0 0 1.9G 0 disk |-mmcblk0p1 179:1 0 128M 0 part `-mmcblk0p2 179:2 0 1.7G 0 part mmcblk1 179:32 0 7.3G 0 disk |-mmcblk1p1 179:33 0 122M 0 part /boot `-mmcblk1p2 179:34 0 6.5G 0 part / mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 253:0 0 50M 0 disk /var/log zram1 253:1 0 417M 0 disk [SWAP]