Skip to content

ROCKPro64 - Der Bootvorgang

Verschoben Hardware
3 1 1.6k
  • Basis für diesen Beitrag

    rock64@rockpro64:/boot$ uname -a
    Linux rockpro64 4.4.132-1075-rockchip-ayufan-ga83beded8524 #1 SMP Thu Jul 26 08:22:22 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
    

    So sieht die Partitionstabelle des Images aus (SD-Karte)

     rock64@rockpro64:/boot$ sudo fdisk /dev/mmcblk0
     [sudo] password for rock64: 
     
     Welcome to fdisk (util-linux 2.31.1).
     Changes will remain in memory only, until you decide to write them.
     Be careful before using the write command.
     
     
     Command (m for help): p
     Disk /dev/mmcblk0: 29.7 GiB, 31914983424 bytes, 62333952 sectors
     Units: sectors of 1 * 512 = 512 bytes
     Sector size (logical/physical): 512 bytes / 512 bytes
     I/O size (minimum/optimal): 512 bytes / 512 bytes
     Disklabel type: gpt
     Disk identifier: 2C9A4A22-7AA8-4A1B-815E-0C3E2E7065E6
     
     Device          Start      End  Sectors  Size Type
     /dev/mmcblk0p1     64     8063     8000  3.9M Linux filesystem
     /dev/mmcblk0p2   8064     8191      128   64K Linux filesystem
     /dev/mmcblk0p3   8192    16383     8192    4M Linux filesystem
     /dev/mmcblk0p4  16384    24575     8192    4M Linux filesystem
     /dev/mmcblk0p5  24576    32767     8192    4M Linux filesystem
     /dev/mmcblk0p6  32768   262143   229376  112M Microsoft basic data
     /dev/mmcblk0p7 262144 62333918 62071775 29.6G Linux filesystem
     
     Command (m for help): 
    
    Partition Start Sector Number of Sectors Partition Size PartNum in GPT Requirements
    MBR 0 1 512
    Primary GPT 1 63 32256
    loader1 64 7104 4096000 1 preloader (miniloader or U-Boot SPL)
    Vendor Storage 7168 512 262144 SN, MAC and etc.
    Reserved Space 7680 384 196608 Not used
    reserved1 8064 128 65536 legacy DRM key
    U-Boot ENV 8128 64 32768
    reserved2 8192 8192 4194304 legacy parameter
    loader2 16384 8192 4194304 2 U-Boot or UEFI
    trust 24576 8192 4194304 3 trusted-os like ATF, OP-TEE
    boot(bootable must be set) 32768 229376 117440512 4 kernel, dtb, extlinux.conf, ramdisk
    rootfs 262144 - - 5 Linux system
    Secondary GPT 16777183 33 16896

    Quelle der Info's (bearbeitet) Rockchip.

    Hier sieht man das zwei Partitionen gemountet werden.

    rock64@rockpro64:~$ df -h
    Filesystem      Size  Used Avail Use% Mounted on
    udev            992M     0  992M   0% /dev
    tmpfs           200M  484K  199M   1% /run
    /dev/mmcblk0p7   30G  1.3G   27G   5% /
    tmpfs           996M     0  996M   0% /dev/shm
    tmpfs           5.0M  4.0K  5.0M   1% /run/lock
    tmpfs           996M     0  996M   0% /sys/fs/cgroup
    /dev/mmcblk0p6  112M  4.0K  112M   1% /boot/efi
    /dev/sda1       1.9T   43G  1.8T   3% /mnt
    tmpfs           200M     0  200M   0% /run/user/1000
    
    • /dev/mmcblk0p6 = /boot/efi
    • /dev/mmcblk0p7 = Linux System /

    Inhalt /boot/efi (/dev/mmcblk0p6)

    rock64@rockpro64:/boot/efi$ ls -la
    total 22
    drwxr-xr-x 3 root root 16384 Jan  1  1970 .
    drwxr-xr-x 5 root root  4096 Aug 27 17:23 ..
    drwxr-xr-x 2 root root  2048 Jul 26 09:15 extlinux
    

    Inhalt extlinux

    rock64@rockpro64:/boot/efi$ ls -la extlinux/
    total 20
    drwxr-xr-x 2 root root  2048 Jul 26 09:15 .
    drwxr-xr-x 3 root root 16384 Jan  1  1970 ..
    -rwxr-xr-x 1 root root   688 Jul 21 22:50 extlinux.conf
    

    Datei extlinux.conf

     timeout 10
     default kernel-latest
     menu title select kernel
     
     label kernel-latest
         kernel /Image
         initrd /initrd.img
         fdt /dtb
         append rw root=LABEL=linux-root rootwait rootfstype=ext4 panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
     
     label kernel-previous
         kernel /Image.bak
         initrd /initrd.img.bak
         fdt /dtb.bak
         append rw root=LABEL=linux-root rootwait rootfstype=ext4 panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
    

    Inhalt /boot (/dev/mmcblk0p7)

    rock64@rockpro64:/boot$ ls
    System.map-4.4.132-1075-rockchip-ayufan-ga83beded8524  filesystem.packages
    config-4.4.132-1075-rockchip-ayufan-ga83beded8524      filesystem.packages-remove
    dtbs                                                   initrd.img-4.4.132-1075-rockchip-ayufan-ga83beded8524
    efi                                                    vmlinuz-4.4.132-1075-rockchip-ayufan-ga83beded8524
    extlinux
    

    In extlinux liegt auch hier eine extlinux.conf mit folgendem Inhalt.

    timeout 10
    menu title select kernel
    
    label kernel-4.4.132-1075-rockchip-ayufan-ga83beded8524
        kernel /boot/vmlinuz-4.4.132-1075-rockchip-ayufan-ga83beded8524
        initrd /boot/initrd.img-4.4.132-1075-rockchip-ayufan-ga83beded8524
        devicetreedir /boot/dtbs/4.4.132-1075-rockchip-ayufan-ga83beded8524
        append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4
    
    label kernel-4.4.132-1075-rockchip-ayufan-ga83beded8524-memtest
        kernel /boot/vmlinuz-4.4.132-1075-rockchip-ayufan-ga83beded8524
        initrd /boot/initrd.img-4.4.132-1075-rockchip-ayufan-ga83beded8524
        devicetreedir /boot/dtbs/4.4.132-1075-rockchip-ayufan-ga83beded8524
        append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 memtest
    

    Ok, das kenne ich. Hier stellt man ein von wo er bootet usw. Was ich nicht verstehe, wofür braucht es dann /boot/efi (/dev/mmcblk0p6) ?? Es gibt immer einen Eintrag für die aktuelle Kernelversion und die alte Kernelversion. Wenn was schief geht, kann man die alte Version booten. Die aktuelle Version steht immer oben. Im Beispiel handelt es sich um das Original Image, kein anderer Kernel ist installiert.

    • Ordner /boot/efi ???
    • Ordner /boot/dtbs - hier liegt das .dts File!!
    • Ordner /boot/efi ???
    • Ordner /boot/extlinux ???????

    System.map-4.4.132-1075-rockchip-ayufan-ga83beded8524

    A symbol table is a look-up between symbol names and their addresses in memory. A symbol name may be the name of a variable or the name of a function.

    Quelle: https://en.wikipedia.org/wiki/System.map

    Beispiel (gekürzt)

    0000000000000000 A __rela_size
    0000000000000000 A _kernel_flags_le_hi32
    0000000000000000 A _kernel_offset_le_hi32
    0000000000000000 A _kernel_size_le_hi32
    000000000000000a A _kernel_flags_le_lo32
    0000000000000200 A PECOFF_FILE_ALIGNMENT
    0000000000080000 A _kernel_offset_le_lo32
    000000000119f908 A __rela_offset
    0000000001392000 A _kernel_size_le_lo32
    ffffff8008080000 t _head
    ffffff8008080000 T _text
    ffffff8008080800 T __exception_text_start
    ffffff8008080800 T _stext
    ffffff8008080800 T do_undefinstr
    ffffff8008080a1c T do_sysinstr
    ffffff8008080ab4 T do_mem_abort
    ffffff8008080b60 T do_sp_pc_abort
    ffffff8008080c34 T do_debug_exception
    ffffff8008080ce8 T __exception_text_end
    ffffff8008080ce8 T __irqentry_text_start
    ffffff8008080ce8 t gic_handle_irq
    ffffff8008080da8 t gic_handle_irq
    ffffff8008080f28 T __do_softirq
    ffffff8008080f28 T __irqentry_text_end
    ffffff8008080f28 T __softirqentry_text_start
    ffffff8008081228 T __entry_text_start
    ffffff8008081228 T __softirqentry_text_end
    ffffff8008081800 T vectors
    

    config-4.4.132-1075-rockchip-ayufan-ga83beded8524

    Linux Kernel Konfiguration

    Beispiel (gekürzt)

    #
    # Automatically generated file; DO NOT EDIT.
    # Linux/arm64 4.4.132 Kernel Configuration
    #
    CONFIG_ARM64=y
    CONFIG_64BIT=y
    CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
    CONFIG_MMU=y
    CONFIG_ARCH_MMAP_RND_BITS_MIN=18
    CONFIG_ARCH_MMAP_RND_BITS_MAX=24
    CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=11
    CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16
    CONFIG_ARM64_PAGE_SHIFT=12
    CONFIG_ARM64_CONT_SHIFT=4
    CONFIG_STACKTRACE_SUPPORT=y
    CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
    CONFIG_LOCKDEP_SUPPORT=y
    CONFIG_TRACE_IRQFLAGS_SUPPORT=y
    CONFIG_RWSEM_XCHGADD_ALGORITHM=y
    CONFIG_GENERIC_BUG=y
    CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
    CONFIG_GENERIC_HWEIGHT=y
    CONFIG_GENERIC_CSUM=y
    CONFIG_GENERIC_CALIBRATE_DELAY=y
    CONFIG_ZONE_DMA=y
    CONFIG_HAVE_GENERIC_RCU_GUP=y
    CONFIG_ARCH_DMA_ADDR_T_64BIT=y
    CONFIG_NEED_DMA_MAP_STATE=y
    CONFIG_NEED_SG_DMA_LENGTH=y
    CONFIG_SMP=y
    CONFIG_SWIOTLB=y
    CONFIG_IOMMU_HELPER=y
    CONFIG_KERNEL_MODE_NEON=y
    CONFIG_FIX_EARLYCON_MEM=y
    CONFIG_PGTABLE_LEVELS=3
    

    filesystem.packages

    Beispiel (gekürzt)

    adduser 3.116ubuntu1
    alsa-utils      1.1.3-1ubuntu1
    apt     1.6.1
    apt-utils       1.6.1
    base-files      10.1ubuntu2
    base-passwd     3.5.44
    bash    4.4.18-2ubuntu1
    binutils        2.30-15ubuntu1
    binutils-aarch64-linux-gnu      2.30-15ubuntu1
    binutils-common:arm64   2.30-15ubuntu1
    bsdutils        1:2.31.1-0.4ubuntu3
    build-essential 12.4ubuntu1
    busybox-initramfs       1:1.27.2-2ubuntu3
    bzip2   1.0.6-8.1
    ca-certificates 20180409
    console-setup   1.178ubuntu2
    console-setup-linux     1.178ubuntu2
    coreutils       8.28-1ubuntu1
    

    filesystem.packages-remove

    Datei ist leer

    initrd.img-4.4.132-1075-rockchip-ayufan-ga83beded8524

    initrd ist ein temporäres Dateisystem, das vom Linux-Kernel während des Bootvorgangs verwendet wird.

    Quelle: https://de.wikipedia.org/wiki/Initrd

    Jedes mal, wenn man einen Kernel installiert, wird dieses File angelegt. Ein Beispiel von meinem ROCKPro64 mit NVMe SSD.

    rock64@rockpro64v2_0:/boot$ ls
    config-4.18.0-rc8-1060-ayufan-g45828c4db727
    config-4.4.132-1075-rockchip-ayufan-ga83beded8524
    dtbs
    efi
    extlinux
    filesystem.packages
    filesystem.packages-remove
    initrd.img-4.18.0-rc8-1056-ayufan-gad339353011e
    initrd.img-4.18.0-rc8-1060-ayufan-g45828c4db727
    initrd.img-4.18.0-rc8-1060-ayufan-g45828c4db727.bak
    initrd.img-4.4.132-1075-rockchip-ayufan-ga83beded8524
    System.map-4.18.0-rc8-1060-ayufan-g45828c4db727
    System.map-4.4.132-1075-rockchip-ayufan-ga83beded8524
    vmlinuz-4.18.0-rc8-1060-ayufan-g45828c4db727
    vmlinuz-4.4.132-1075-rockchip-ayufan-ga83beded8524
    

    Hier kann man auch ganz gut erkennen, das es immer ein initrd.img gibt, eine entsprechende System.map und eine vmlinux.

    vmlinuz-4.4.132-1075-rockchip-ayufan-ga83beded8524

    On Linux systems, vmlinux is a statically linked executable file that contains the Linux kernel in one of the object file formats supported by Linux, which includes ELF, COFF and a.out. The vmlinux file might be required for kernel debugging, symbol table generation or other operations, but must be made bootable before being used as an operating system kernel by adding a multiboot header, bootsector and setup routines.

    Ich denke, das man das normalerweise nicht braucht. Aber ich mach hier zur Sicherheit mal ein paar ???? dran!

    wird fortgesetzt..

  • Ich versuche hier mal den Bootvorgang des ROCKPro64 zu verstehen 🙂

  • Um einen neuen Kernel booten zu können, brauche ich diese 4 Dateien unter /boot

    • config-4.19.0-rc4-1065-ayufan-g72e04c7b3e06
    • initrd.img-4.19.0-rc4-1065-ayufan-g72e04c7b3e06
    • System.map-4.19.0-rc4-1065-ayufan-g72e04c7b3e06
    • vmlinuz-4.19.0-rc4-1065-ayufan-g72e04c7b3e06

    Und den Ordner /boot/dtbs/4.19.0-rc4-1065-ayufan-g72e04c7b3e06 mit folgendem Inhalt

    rock64@rockpro64v2_0:/boot/dtbs/4.19.0-rc4-1065-ayufan-g72e04c7b3e06$ ls -la
    total 104
    drwxr-xr-x 26 root root 4096 Sep 30 09:54 .
    drwxr-xr-x  6 root root 4096 Sep 30 09:55 ..
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 al
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 allwinner
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 altera
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 amd
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 amlogic
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 apm
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 arm
    drwxr-xr-x  4 root root 4096 Sep 30 09:54 broadcom
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 cavium
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 exynos
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 freescale
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 hisilicon
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 lg
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 marvell
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 mediatek
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 nvidia
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 qcom
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 renesas
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 rockchip
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 socionext
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 sprd
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 synaptics
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 xilinx
    drwxr-xr-x  2 root root 4096 Sep 30 09:54 zte
    

    Unter /boot/extlinux liegt dann die Datei extlinux.conf

    Die sieht bei mir dann so aus

    timeout 10
    menu title select kernel
    
    label kernel-4.19.0-rc4-1065-ayufan-g72e04c7b3e06
        kernel /boot/vmlinuz-4.19.0-rc4-1065-ayufan-g72e04c7b3e06
        initrd /boot/initrd.img-4.19.0-rc4-1065-ayufan-g72e04c7b3e06
        devicetreedir /boot/dtbs/4.19.0-rc4-1065-ayufan-g72e04c7b3e06
        append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=TEST rootwait rootfstype=ext4
    
    label kernel-4.19.0-rc4-1065-ayufan-g72e04c7b3e06-memtest
        kernel /boot/vmlinuz-4.19.0-rc4-1065-ayufan-g72e04c7b3e06
        initrd /boot/initrd.img-4.19.0-rc4-1065-ayufan-g72e04c7b3e06
        devicetreedir /boot/dtbs/4.19.0-rc4-1065-ayufan-g72e04c7b3e06
        append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=TEST rootwait rootfstype=ext4 memtest
    

    Darunter kommen dann evt. die alten Kernel die installiert waren, das habe ich hier im Beispiel weg gelassen.

  • Mainline 6.0.x

    Images rockpro64
    6
    0 Stimmen
    6 Beiträge
    456 Aufrufe
    FrankMF
    Und RC7 released https://github.com/ayufan-rock64/linux-mainline-kernel/releases/tag/6.7.0-rc7-1185-ayufan
  • Images 0.10.x

    Angeheftet Images rockpro64
    10
    0 Stimmen
    10 Beiträge
    610 Aufrufe
    FrankMF
    0.10.12: gitlab-ci-linux-build-184 released 0.10.12: Be strict on any qemu failures 0.10.12: Build by default mate/lxde/gnome/xfce4 0.10.12: Add pcie scan delay from @nuumio 0.10.12: Add ubuntu-mate-lightdm-theme where possible Ich komme gar nicht mehr mit dem Testen hinterher
  • ROCKPro64 - Zwei LAN Schnittstellen / VLAN einrichten

    ROCKPro64 linux vlan rockpro64
    4
    0 Stimmen
    4 Beiträge
    690 Aufrufe
    FrankMF
    Das Setup heute mal getestet um zu sehen, ob das auch so funktioniert. LAN an meine Fritzbox (DHCP) an eth1.100 mein Notebook an eth1.200 meine PS4 Und dann mal gemütlich eine Runde MW gezockt. Läuft alles einwandfrei
  • ROCKPro64 - i2c Bus

    Hardware rockpro64
    1
    2
    0 Stimmen
    1 Beiträge
    591 Aufrufe
    Niemand hat geantwortet
  • Ayufan Release 0.7.12

    ROCKPro64 rockpro64
    3
    0 Stimmen
    3 Beiträge
    476 Aufrufe
    FrankMF
    Dafür andere Probleme https://pastebin.com/VGGKm1vR Aktuell nicht zu empfehlen!
  • ROCKPro64 - Das erste Mal

    Angeheftet Verschoben Hardware rockpro64
    5
    2
    1 Stimmen
    5 Beiträge
    989 Aufrufe
    FrankMF
    Ich kann heute die Fragen aller Fragen beantworten Damit ist leider die Frage immer noch unbeantwortet ob WLan und PCIe zusammen nutzbar ist!! Es geht!! Ich habe von MrFixit ein Testimage der RecalBox, benutzt das selbe Debian wie oben. Die Tage konnte man im IRC verfolgen, wie man dem Grundproblem näher kam und wohl einen Fix gebastelt hat, damit beides zusammen funktioniert. Mr.Fixit hat das in RecalBox eingebaut und ich durfte testen. # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP8000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 62:03:b0:d6:dc:b3 brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP8000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether ac:83:f3:e6:1f:b2 brd ff:ff:ff:ff:ff:ff inet 192.168.178.27/24 brd 192.168.178.255 scope global wlan0 valid_lft forever preferred_lft forever inet6 2a02:908:1262:4680:ae83:f3ff:fee6:1fb2/64 scope global dynamic valid_lft 7145sec preferred_lft 3545sec inet6 fe80::ae83:f3ff:fee6:1fb2/64 scope link valid_lft forever preferred_lft forever # ls /mnt bin etc media recalbox sd.img test2.img boot home mnt root selinux tmp crypthome lib opt run srv usr dev lost+found proc sbin sys var # fdisk BusyBox v1.27.2 (2019-02-01 22:43:19 EST) multi-call binary. Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK Change partition table -u Start and End are in sectors (instead of cylinders) -l Show partition table for each DISK, then exit -b 2048 (for certain MO disks) use 2048-byte sectors -C CYLINDERS Set number of cylinders/heads/sectors -H HEADS Typically 255 -S SECTORS Typically 63 # fdisk -l Disk /dev/mmcblk0: 15 GB, 15931539456 bytes, 31116288 sectors 486192 cylinders, 4 heads, 16 sectors/track Units: cylinders of 64 * 512 = 32768 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/mmcblk0p1 * 2,10,9 10,50,40 32768 163839 131072 64.0M c Win95 FAT32 (LBA) Partition 1 does not end on cylinder boundary /dev/mmcblk0p2 * 16,81,2 277,102,17 262144 4456447 4194304 2048M 83 Linux Partition 2 does not end on cylinder boundary /dev/mmcblk0p3 277,102,18 1023,254,63 4456448 31115263 26658816 12.7G 83 Linux Partition 3 does not end on cylinder boundary Disk /dev/nvme0n1: 233 GB, 250059350016 bytes, 488397168 sectors 2543735 cylinders, 12 heads, 16 sectors/track Units: cylinders of 192 * 512 = 98304 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/nvme0n1p1 1,0,1 907,11,16 2048 488397167 488395120 232G 83 Linux # Oben sieht man eine funktionierende WLan-Verbindung, das LAN-Kabel war entfernt. Unten sieht man die PCIe NVMe SSD, gemountet nach /mnt und Inhaltsausgabe. Das sollte beweisen, das der Ansatz der Lösung funktioniert. Leider kann ich nicht sagen, das es zum jetzigen Zeitpunkt stabil läuft. Ich habe einfach so Reboots, kann den Fehler aktuell aber nicht fangen. Mal sehen ob ich noch was finde. Aber, es ist ein Anfang!
  • ROCKPro64 - PCIe SATA-Karte macht immer mal Probleme

    ROCKPro64 rockpro64
    2
    0 Stimmen
    2 Beiträge
    568 Aufrufe
    FrankMF
    Das ist das Ergebnis des Stresstests [ 2461.489468] ata2.00: exception Emask 0x10 SAct 0xffffffff SErr 0x400000 action 0x6 frozen [ 2461.490206] ata2.00: irq_stat 0x08000000, interface fatal error [ 2461.490732] ata2: SError: { Handshk } [ 2461.491062] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.491532] ata2.00: cmd 61/40:00:f8:a6:64/05:00:84:00:00/40 tag 0 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.492993] ata2.00: status: { DRDY } [ 2461.493327] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.493796] ata2.00: cmd 61/c0:08:38:ac:64/03:00:84:00:00/40 tag 1 ncq dma 491520 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.495181] ata2.00: status: { DRDY } [ 2461.495507] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.496276] ata2.00: cmd 61/c0:10:a0:f5:64/02:00:84:00:00/40 tag 2 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.497697] ata2.00: status: { DRDY } [ 2461.498029] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.498497] ata2.00: cmd 61/40:18:60:f8:64/05:00:84:00:00/40 tag 3 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.499886] ata2.00: status: { DRDY } [ 2461.500213] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.500681] ata2.00: cmd 61/c0:20:a0:fd:64/02:00:84:00:00/40 tag 4 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.502087] ata2.00: status: { DRDY } [ 2461.502416] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.502884] ata2.00: cmd 61/40:28:60:00:65/05:00:84:00:00/40 tag 5 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.505026] ata2.00: status: { DRDY } [ 2461.505378] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.505852] ata2.00: cmd 61/c0:30:a0:05:65/02:00:84:00:00/40 tag 6 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.507244] ata2.00: status: { DRDY } [ 2461.507572] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.508040] ata2.00: cmd 61/40:38:60:08:65/05:00:84:00:00/40 tag 7 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.509472] ata2.00: status: { DRDY } [ 2461.509808] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.510277] ata2.00: cmd 61/a0:40:a0:0d:65/02:00:84:00:00/40 tag 8 ncq dma 344064 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.511667] ata2.00: status: { DRDY } [ 2461.511994] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.512461] ata2.00: cmd 61/40:48:00:20:66/05:00:84:00:00/40 tag 9 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.514503] ata2.00: status: { DRDY } [ 2461.514850] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.515322] ata2.00: cmd 61/40:50:00:28:66/05:00:84:00:00/40 tag 10 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.516721] ata2.00: status: { DRDY } [ 2461.517084] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.517562] ata2.00: cmd 61/c0:58:40:2d:66/02:00:84:00:00/40 tag 11 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.519253] ata2.00: status: { DRDY } [ 2461.519595] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.520066] ata2.00: cmd 61/40:60:f8:9e:64/05:00:84:00:00/40 tag 12 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.521504] ata2.00: status: { DRDY } [ 2461.521840] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.522309] ata2.00: cmd 61/c0:68:38:a4:64/02:00:84:00:00/40 tag 13 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.523706] ata2.00: status: { DRDY } [ 2461.524033] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.524501] ata2.00: cmd 61/40:70:f8:af:64/05:00:84:00:00/40 tag 14 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.525925] ata2.00: status: { DRDY } [ 2461.526256] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.526725] ata2.00: cmd 61/c0:78:38:b5:64/02:00:84:00:00/40 tag 15 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.528122] ata2.00: status: { DRDY } [ 2461.528449] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.528939] ata2.00: cmd 61/40:80:f8:b7:64/05:00:84:00:00/40 tag 16 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.530339] ata2.00: status: { DRDY } [ 2461.530667] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.531136] ata2.00: cmd 61/c0:88:38:bd:64/02:00:84:00:00/40 tag 17 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.532532] ata2.00: status: { DRDY } [ 2461.532880] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.533357] ata2.00: cmd 61/40:90:f8:bf:64/05:00:84:00:00/40 tag 18 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.534754] ata2.00: status: { DRDY } [ 2461.535081] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.535549] ata2.00: cmd 61/c0:98:38:c5:64/02:00:84:00:00/40 tag 19 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.536970] ata2.00: status: { DRDY } [ 2461.537301] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.537769] ata2.00: cmd 61/40:a0:f8:c7:64/05:00:84:00:00/40 tag 20 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.539165] ata2.00: status: { DRDY } [ 2461.539491] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.539960] ata2.00: cmd 61/c0:a8:38:cd:64/02:00:84:00:00/40 tag 21 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.541381] ata2.00: status: { DRDY } [ 2461.541713] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.542182] ata2.00: cmd 61/40:b0:f8:cf:64/05:00:84:00:00/40 tag 22 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.543577] ata2.00: status: { DRDY } [ 2461.543905] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.544374] ata2.00: cmd 61/40:b8:f8:d7:64/05:00:84:00:00/40 tag 23 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.545790] ata2.00: status: { DRDY } [ 2461.546120] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.546589] ata2.00: cmd 61/c0:c0:38:dd:64/02:00:84:00:00/40 tag 24 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.547987] ata2.00: status: { DRDY } [ 2461.548314] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.548782] ata2.00: cmd 61/a8:c8:f8:df:64/05:00:84:00:00/40 tag 25 ncq dma 741376 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.550198] ata2.00: status: { DRDY } [ 2461.550530] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.550999] ata2.00: cmd 61/c0:d0:a0:e5:64/02:00:84:00:00/40 tag 26 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.552396] ata2.00: status: { DRDY } [ 2461.552723] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.553208] ata2.00: cmd 61/40:d8:60:e8:64/05:00:84:00:00/40 tag 27 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.554607] ata2.00: status: { DRDY } [ 2461.554935] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.555404] ata2.00: cmd 61/c0:e0:a0:ed:64/02:00:84:00:00/40 tag 28 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.556800] ata2.00: status: { DRDY } [ 2461.557145] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.557617] ata2.00: cmd 61/40:e8:60:f0:64/05:00:84:00:00/40 tag 29 ncq dma 688128 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.559012] ata2.00: status: { DRDY } [ 2461.559340] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.559807] ata2.00: cmd 61/c0:f0:38:d5:64/02:00:84:00:00/40 tag 30 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.561221] ata2.00: status: { DRDY } [ 2461.561552] ata2.00: failed command: WRITE FPDMA QUEUED [ 2461.562021] ata2.00: cmd 61/c0:f8:40:25:66/02:00:84:00:00/40 tag 31 ncq dma 360448 out res 40/00:50:00:28:66/00:00:84:00:00/40 Emask 0x10 (ATA bus error) [ 2461.563416] ata2.00: status: { DRDY } [ 2461.563752] ata2: hard resetting link [ 2471.561504] ata2: softreset failed (1st FIS failed) [ 2471.561959] ata2: hard resetting link [ 2481.560785] ata2: softreset failed (1st FIS failed) [ 2481.561238] ata2: hard resetting link [ 2516.561654] ata2: softreset failed (1st FIS failed) [ 2516.562109] ata2: limiting SATA link speed to 3.0 Gbps [ 2516.562113] ata2: hard resetting link [ 2521.561261] ata2: softreset failed (1st FIS failed) [ 2521.561715] ata2: reset failed, giving up [ 2521.562074] ata2.00: disabled [ 2521.562575] ata2: EH complete [ 2521.562677] sd 1:0:0:0: [sdb] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2521.562686] sd 1:0:0:0: [sdb] tag#18 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 [ 2521.562701] print_req_error: I/O error, dev sdb, sector 0 [ 2521.562791] sd 1:0:0:0: [sdb] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2521.562802] sd 1:0:0:0: [sdb] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2521.562873] sd 1:0:0:0: [sdb] tag#19 CDB: opcode=0x2a 2a 00 84 66 25 40 00 02 c0 00 [ 2521.562888] print_req_error: I/O error, dev sdb, sector 2221286720 [ 2521.563107] sd 1:0:0:0: [sdb] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2521.563126] sd 1:0:0:0: [sdb] tag#21 CDB: opcode=0x2a 2a 00 84 64 f0 60 00 05 40 00 [ 2521.563138] print_req_error: I/O error, dev sdb, sector 2221207648 [ 2521.563422] sd 1:0:0:0: [sdb] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2521.563772] sd 1:0:0:0: [sdb] tag#20 CDB: opcode=0x2a 2a 00 84 64 d5 38 00 02 c0 00 [ 2521.564326] print_req_error: I/O error, dev sdb, sector 2221200696 [ 2521.564337] sd 1:0:0:0: [sdb] tag#22 CDB: opcode=0x2a 2a 00 84 64 ed a0 00 02 c0 00 [ 2521.564896] print_req_error: I/O error, dev sdb, sector 2221206944 [ 2521.565088] sd 1:0:0:0: [sdb] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2521.565469] sd 1:0:0:0: [sdb] tag#26 CDB: opcode=0x2a 2a 00 84 64 dd 38 00 02 c0 00 [ 2521.565483] print_req_error: I/O error, dev sdb, sector 2221202744 [ 2521.565610] sd 1:0:0:0: [sdb] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2521.566056] sd 1:0:0:0: [sdb] tag#23 CDB: opcode=0x2a 2a 00 84 64 e8 60 00 05 40 00 [ 2521.566069] print_req_error: I/O error, dev sdb, sector 2221205600 [ 2521.566183] sd 1:0:0:0: [sdb] tag#29 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2521.566641] sd 1:0:0:0: [sdb] tag#29 CDB: opcode=0x2a 2a 00 84 64 cd 38 00 02 c0 00 [ 2521.566654] print_req_error: I/O error, dev sdb, sector 2221198648 [ 2521.566954] sd 1:0:0:0: [sdb] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2521.567224] sd 1:0:0:0: [sdb] tag#24 CDB: opcode=0x2a 2a 00 84 64 e5 a0 00 02 c0 00 [ 2521.567237] print_req_error: I/O error, dev sdb, sector 2221204896 [ 2521.567459] sd 1:0:0:0: [sdb] tag#30 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2521.567809] sd 1:0:0:0: [sdb] tag#30 CDB: opcode=0x2a 2a 00 84 64 c7 f8 00 05 40 00 [ 2521.567821] print_req_error: I/O error, dev sdb, sector 2221197304 [ 2521.584903] md: super_written gets error=10 [ 2521.585306] md/raid1:md0: Disk failure on dm-1, disabling device. md/raid1:md0: Operation continuing on 1 devices. [ 2526.581450] scsi_io_completion_action: 41779 callbacks suppressed [ 2526.581461] sd 1:0:0:0: [sdb] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2526.581467] sd 1:0:0:0: [sdb] tag#27 CDB: opcode=0x2a 2a 00 84 66 7d 50 00 00 01 00 [ 2526.581469] print_req_error: 41780 callbacks suppressed [ 2526.581471] print_req_error: I/O error, dev sdb, sector 2221309264 [ 2526.582524] sd 1:0:0:0: [sdb] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2526.582530] sd 1:0:0:0: [sdb] tag#28 CDB: opcode=0x2a 2a 00 84 66 7d 51 00 00 01 00 [ 2526.582534] print_req_error: I/O error, dev sdb, sector 2221309265 [ 2526.583366] sd 1:0:0:0: [sdb] tag#29 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2526.583370] sd 1:0:0:0: [sdb] tag#29 CDB: opcode=0x2a 2a 00 84 66 7d 52 00 00 01 00 [ 2526.583373] print_req_error: I/O error, dev sdb, sector 2221309266 [ 2526.584113] sd 1:0:0:0: [sdb] tag#30 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2526.584117] sd 1:0:0:0: [sdb] tag#30 CDB: opcode=0x2a 2a 00 84 66 7d 53 00 00 01 00 [ 2526.584119] print_req_error: I/O error, dev sdb, sector 2221309267 [ 2526.584960] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2526.584968] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 84 66 7d 54 00 00 01 00 [ 2526.584971] print_req_error: I/O error, dev sdb, sector 2221309268 [ 2526.585765] sd 1:0:0:0: [sdb] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2526.585769] sd 1:0:0:0: [sdb] tag#1 CDB: opcode=0x2a 2a 00 84 66 7d 55 00 00 01 00 [ 2526.585772] print_req_error: I/O error, dev sdb, sector 2221309269 [ 2526.586461] sd 1:0:0:0: [sdb] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2526.586465] sd 1:0:0:0: [sdb] tag#2 CDB: opcode=0x2a 2a 00 84 66 7d 56 00 00 01 00 [ 2526.586468] print_req_error: I/O error, dev sdb, sector 2221309270 [ 2526.587144] sd 1:0:0:0: [sdb] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2526.587148] sd 1:0:0:0: [sdb] tag#3 CDB: opcode=0x2a 2a 00 84 66 7d 57 00 00 01 00 [ 2526.587150] print_req_error: I/O error, dev sdb, sector 2221309271 [ 2526.587734] sd 1:0:0:0: [sdb] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2526.587737] sd 1:0:0:0: [sdb] tag#4 CDB: opcode=0x2a 2a 00 84 66 7d 58 00 00 01 00 [ 2526.587739] print_req_error: I/O error, dev sdb, sector 2221309272 [ 2526.588320] sd 1:0:0:0: [sdb] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 [ 2526.588323] sd 1:0:0:0: [sdb] tag#5 CDB: opcode=0x2a 2a 00 84 66 7d 59 00 00 01 00 [ 2526.588325] print_req_error: I/O error, dev sdb, sector 2221309273 Und, wieder eine Platte im Raid1 verloren rock64@rockpro64v_2_1:~$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 dm-1[2](F) dm-0[1] 1953379392 blocks super 1.2 [2/1] [_U] bitmap: 5/15 pages [20KB], 65536KB chunk unused devices: <none> Leider habe ich nicht die Kenntnisse um zu erkennen, woran das liegt.
  • IPFire auf dem ROCKPro64

    ROCKPro64 rockpro64
    2
    1
    0 Stimmen
    2 Beiträge
    678 Aufrufe
    FrankMF
    Falls es jemanden da draußen interessiert, hier eine Liste der Dinge die funktionieren GREEN Die LAN-Schnittstelle wird einwandfrei erkannt Webserver läuft, Weboberfläche erreichbar Das war's dann mit den positiven Daten jede Menge Kernelfehler iptables Fehler Modul fehlt?? kein LAN-Adapter, WLan-Adapter wird erkannt Lizenzverbindungen lassen sich nicht bestätigen nach der Installation ist die Konsole weg usw. usf