Jump to content

Failed to setup dm-crypt key mapping for device


saljut7

Recommended Posts

Hello together

 

sorry for this long description but I want to provide all information I could save.

 

I'm running armbian since 2(?) years and had never a serious problem with it. Today the system was not reachable anymore (services, ssh, ping) so I rebooted the server. Rebooting worked but all my data is on an external encrypted harddisk which I couldn't open anymore:

 

root@MyCubietruck:~# cryptsetup luksOpen /dev/sda1 MyEncryptedHarddisk
Enter passphrase for /dev/sda1:
device-mapper: reload ioctl on  failed: No such file or directory
Failed to setup dm-crypt key mapping for device /dev/sda1.
Check that kernel supports aes-xts-plain64 cipher (check syslog for more info).

 

journalctl said:

 

root@MyCubietruck:~# journalctl -r
May 07 13:37:11 MyCubietruck kernel: device-mapper: ioctl: error adding target to table
May 07 13:37:11 MyCubietruck kernel: device-mapper: table: 254:0: crypt: Error allocating crypto tfm

 

System and kernel info when the armbian was still working was:

 

root@MyCubietruck:~# uname -a
Linux MyCubietruck 4.10.12-sunxi #7 SMP Wed Apr 26 02:44:12 CEST 2017 armv7l GNU/Linux
root@MyCubietruck:~# cat /etc/debian_version
8.8

 

So I tried to find similar problems amd found:

The point is: I didn't upgrade the kernel and according to my logwatch mail from this morning there was no kernel upgrade.

 

Now I made a huge mistake: I assumed a kernel problem anyway and tried to solve it with a kernel downgrade (even though I didn't try something like this before) - and I thought should use the script provided by @Igor :

...and noticed this information too late:

Well, the script (choosing "Cubietruck" and "vanilla" ended up with):

                                               ┌─Armbian universal installer 2015.11───┐                                                  
                                               │                                       │                                                  
                                               │ Removing conflicting packages ...     │                                                  
                                               │                                       │                                                  
                                               └───────────────────────────────────────┘                       
                                          
E: Unable to locate package nstall_new                                                                                                    
E: Unable to locate package ""
E: Unable to locate package "Installing
E: Unable to locate package packages..."

 

The upgrade.log says:

 

The following packages will be REMOVED:
  linux-dtb-next-sunxi
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 4,163 kB will be freed.
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 105718 files and directories currently installed.)^M
Removing linux-dtb-next-sunxi (5.27.170427) ...^M
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Note: selecting "linux-image-dev-rockchip" instead of the
      virtual package "linux-image-4.10.0-rockchip"
Note: selecting "linux-image-sun8i" instead of the
      virtual package "linux-image-3.4.113-sun8i"
"linux-image-3.4.112-sun8i" exists in the package database, but it is not a
real package and no package provides it.
"linux-image-4.8.3-sun8i" exists in the package database, but it is not a
real package and no package provides it.
"linux-image-4.7.3-sun8i" exists in the package database, but it is not a
real package and no package provides it.
Note: selecting "linux-image-dev-sun8i" instead of the
      virtual package "linux-image-4.10.0-sun8i"
"linux-image-4.9.4-sun8i" exists in the package database, but it is not a
real package and no package provides it.
The following packages will be REMOVED:
  linux-image-next-sunxi
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 48.8 MB will be freed.
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 105562 files and directories currently installed.)^M
Removing linux-image-next-sunxi (5.27.170427) ...^M
update-initramfs: Deleting /boot/initrd.img-4.10.12-sunxi^M
"linux-headers-2.6" is a virtual package provided by:
  linux-headers-sun7i linux-headers-sun5i linux-headers-sun4i
You must choose one to install.
Note: selecting "linux-headers-sun8i" instead of the
      virtual package "linux-headers-3.4.113-sun8i"
"linux-headers-3.4.112-sun8i" exists in the package database, but it is not a
real package and no package provides it.
The following packages will be REMOVED:
  linux-headers-next-sunxi
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 73.0 MB will be freed

Yes, I know it is stupid but I rebooted again and ended up with:

 

*** ERROR: 'serverip' not set
missing encironment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
Speed: 1000, full duplex
*** ERROR: 'serverip' not set
missing encironment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
Speed: 1000, full duplex
*** ERROR: 'serverip' not set
Config file not found
Speed: 1000, full duplex
BOOTP boradcast 1
BOOTP boradcast 2
DHCP client bound to address 192.168.1.3 (2189 ms)
Zsubg tgerber q01c50000 decie
TFTP from server 0.0.0.0; our IP address is 192.168.1.3; sending through gateway 192.168.1.1
Filename 'boot.scr.uing'.
Load address: 0x43100000
Loading: T T T T T T T T T T
Retry cound exceeded; starting again
sunxi#


For the case it is already to late to fix this with "two or three commands" I would at least try to understand what was causing the problem: why "Failed to setup dm-crypt key mapping" today?

Thx a lot for all helping comments and sorry again for the long description.

sj7

Link to comment
Share on other sites

41 minutes ago, saljut7 said:

For the case it is already to late to fix this with "two or three commands" I would at least try to understand what was causing the problem: why "Failed to setup dm-crypt key mapping" today?

As it was stated in one of the threads you linked, an untested kernel was pushed to the stable repository by mistake, and since your initial kernel version was 4.10.12, this updated kernel was installed on your device before you tried to downgrade it.

 

For the reference "upgrade.armbian.com" is obsolete and I am surprised that it is still not disabled.

Link to comment
Share on other sites

7 minutes ago, zador.blood.stained said:

 

For the reference "upgrade.armbian.com" is obsolete and I am surprised that it is still not disabled.

 

Done.

Link to comment
Share on other sites

Thx @Igor. Here is my complete "how I fixed it log" because the "How to unbrick the system" didn't work for me completely because in my case uInitrd-4.9.7-sunxi and initrd.img-4.9.7-sunxi were not provided by the download links.

 

Here is how I fixed my armbian kernel step by step (originally in markdown, sorry for some format issues). Hope it will help other users fixing a similar problem:

 

### Backup sd-card

 

Create a backup with `dd`, example:

 

# pv /dev/sdb | dd of=/home/YourUser/backups/YourServerHostname2017-05-08.img && sync

 

### Extract kernel DEBs to sd-card

 

> Mount SD card and extract all those deb files to it’s mount point:

 

dpkg -x linux-???.deb /media/...???.../mnt

 

Example:

 

root@YourRescueSystems:/path/to/your/downloaded/armbian_kernel_DEBs# ls -la
total 25912
drwxr-xr-x 2 YourUser YourUser     4096 May  8 19:36 .
drwxr-xr-x 5 YourUser YourUser    12288 May  8 18:16 ..
-rw-r--r-- 1 YourUser YourUser   141466 May  8 19:35 linux-dtb-next-sunxi_5.25_armhf.deb
-rw-r--r-- 1 YourUser YourUser    58860 May  8 19:35 linux-firmware-image-next-sunxi_5.25_armhf.deb
-rw-r--r-- 1 YourUser YourUser 10267140 May  8 19:36 linux-headers-next-sunxi_5.25_armhf.deb
-rw-r--r-- 1 YourUser YourUser 15415128 May  8 19:36 linux-image-next-sunxi_5.25_armhf.deb
-rw-r--r-- 1 YourUser YourUser   362732 May  8 18:02 linux-jessie-root-next-cubietruck_5.25_armhf.deb
-rw-r--r-- 1 YourUser YourUser   211868 May  8 17:56 linux-u-boot-next-cubietruck_5.25_armhf.deb
root@YourRescueSystems:/path/to/your/downloaded/armbian_kernel_DEBs# dpkg -x linux-dtb-next-sunxi_5.25_armhf.deb /media/YourUser/SD-cardIDofYourBrokenArmbian/
root@YourRescueSystems:/path/to/your/downloaded/armbian_kernel_DEBs# dpkg -x linux-firmware-image-next-sunxi_5.25_armhf.deb /media/YourUser/SD-cardIDofYourBrokenArmbian/
root@YourRescueSystems:/path/to/your/downloaded/armbian_kernel_DEBs# dpkg -x linux-headers-next-sunxi_5.25_armhf.deb /media/YourUser/SD-cardIDofYourBrokenArmbian/
root@YourRescueSystems:/path/to/your/downloaded/armbian_kernel_DEBs# dpkg -x linux-image-next-sunxi_5.25_armhf.deb /media/YourUser/SD-cardIDofYourBrokenArmbian/
root@YourRescueSystems:/path/to/your/downloaded/armbian_kernel_DEBs# dpkg -x linux-jessie-root-next-cubietruck_5.25_armhf.deb /media/YourUser/SD-cardIDofYourBrokenArmbian/
root@YourRescueSystems:/path/to/your/downloaded/armbian_kernel_DEBs# dpkg -x linux-u-boot-next-cubietruck_5.25_armhf.deb /media/YourUser/SD-cardIDofYourBrokenArmbian/

 

### Symlink vmlinuz-4.x.x-sunxi

 

> Go to /mnt/boot and link (or copy) `vmlinuz-4.x.x-sunxi` kernel file to `zImage`:

 

Example:

 

root@YourRescueSystems:/path/to/your/downloaded/armbian_kernel_DEBs# cd /media/YourUser/SD-cardIDofYourBrokenArmbian/
root@YourRescueSystems:/media/YourUser/SD-cardIDofYourBrokenArmbian# cd boot/
root@YourRescueSystems:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# ls -la
total 13100
drwxr-xr-x  6 root root    4096 Feb  2 03:20 .
drwxr-xr-x 22 root root    4096 Feb  2 02:21 ..
drwxr-xr-x  2 root root    4096 Feb  2 03:20 bin
drwxr-xr-x  2 root root    4096 Oct 24  2016 bin.old
-rwxr-xr-x  1 root root    6944 Sep 16  2015 boot.bmp
-rwxr-xr-x  1 root root    1698 May  7 14:30 boot.cmd
-rwxr-xr-x  1 root root    1749 May  7 14:30 boot.cmd.backup
-rw-r--r--  1 root root    1770 May  7 14:30 boot.scr
-rw-r--r--  1 root root  144620 Feb  2 01:53 config-4.9.7-sunxi
lrwxrwxrwx  1 root root      17 Apr 30 14:30 dtb -> dtb-4.10.12-sunxi
drwxr-xr-x  2 root root    4096 Sep 24  2016 dtb-4.6.3-sunxi
drwxr-xr-x  2 root root    4096 Feb  2 01:53 dtb-4.9.7-sunxi
lrwxrwxrwx  1 root root      16 Feb 25 01:06 dtb.old -> dtb-4.9.12-sunxi
-rw-r--r--  1 root root       0 Apr 30 14:31 .next
lrwxrwxrwx  1 root root      24 Sep 16  2015 script.bin -> /boot/bin/cubietruck.bin
-rw-r--r--  1 root root 2695178 Feb  2 01:53 System.map-4.9.7-sunxi
lrwxrwxrwx  1 root root      21 May  7 12:49 uInitrd -> uInitrd-4.10.12-sunxi
-rw-r--r--  1 root root 4484597 May  7 12:49 uInitrd-4.10.12-sunxi
-rw-r--r--  1 root root       0 Jan  1  1970 .verbose
-rwxr-xr-x  1 root root 6037368 Feb  2 01:53 vmlinuz-4.9.7-sunxi
lrwxrwxrwx  1 root root      21 Apr 30 14:31 zImage -> vmlinuz-4.10.12-sunxi
root@YourRescueSystems:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# rm zImage
root@YourRescueSystems:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# ln -s vmlinuz-4.9.7-sunxi zImage
root@YourRescueSystems:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# ls -la
total 13100
drwxr-xr-x  6 root root    4096 May  8 20:41 .
drwxr-xr-x 22 root root    4096 Feb  2 02:21 ..
drwxr-xr-x  2 root root    4096 Feb  2 03:20 bin
drwxr-xr-x  2 root root    4096 Oct 24  2016 bin.old
-rwxr-xr-x  1 root root    6944 Sep 16  2015 boot.bmp
-rwxr-xr-x  1 root root    1698 May  7 14:30 boot.cmd
-rwxr-xr-x  1 root root    1749 May  7 14:30 boot.cmd.backup
-rw-r--r--  1 root root    1770 May  7 14:30 boot.scr
-rw-r--r--  1 root root  144620 Feb  2 01:53 config-4.9.7-sunxi
lrwxrwxrwx  1 root root      17 Apr 30 14:30 dtb -> dtb-4.10.12-sunxi
drwxr-xr-x  2 root root    4096 Sep 24  2016 dtb-4.6.3-sunxi
drwxr-xr-x  2 root root    4096 Feb  2 01:53 dtb-4.9.7-sunxi
lrwxrwxrwx  1 root root      16 Feb 25 01:06 dtb.old -> dtb-4.9.12-sunxi
-rw-r--r--  1 root root       0 Apr 30 14:31 .next
lrwxrwxrwx  1 root root      24 Sep 16  2015 script.bin -> /boot/bin/cubietruck.bin
-rw-r--r--  1 root root 2695178 Feb  2 01:53 System.map-4.9.7-sunxi
lrwxrwxrwx  1 root root      21 May  7 12:49 uInitrd -> uInitrd-4.10.12-sunxi
-rw-r--r--  1 root root 4484597 May  7 12:49 uInitrd-4.10.12-sunxi
-rw-r--r--  1 root root       0 Jan  1  1970 .verbose
-rwxr-xr-x  1 root root 6037368 Feb  2 01:53 vmlinuz-4.9.7-sunxi
lrwxrwxrwx  1 root root      19 May  8 20:41 zImage -> vmlinuz-4.9.7-sunxi
root@YourRescueSystems:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot#


### Test your (maybe) unbricked system

 

cd /
umount /media/YourUser/SD-cardIDofYourBrokenArmbian


Problem: armbian still doesn't boot. :/

 

#### Comparison FreshInstalledArmbian <-> BrokenArmbian

 

root@YourRescueSystem:/media/YourUser/SD-cardIDofYourFreshInstalledArmbian/boot# ls -la
total 16656
drwxr-xr-x  4 root root    4096 May  8 21:51 .
drwxr-xr-x 22 root root    4096 Feb  5 22:54 ..
-rw-r--r--  1 root root     114 May  8 21:51 armbianEnv.txt
drwxr-xr-x  2 root root    4096 Feb  5 22:58 bin
-rw-r--r--  1 root root    6944 Feb  5 22:59 boot.bmp
-rw-r--r--  1 root root    2580 Feb  5 22:53 boot.cmd
-rw-r--r--  1 root root    2652 Feb  5 23:00 boot.scr
-rw-r--r--  1 root root  144620 Feb  2 01:53 config-4.9.7-sunxi
lrwxrwxrwx  1 root root      15 Feb  5 22:58 dtb -> dtb-4.9.7-sunxi
drwxr-xr-x  2 root root    4096 Feb  5 22:58 dtb-4.9.7-sunxi
-rw-r--r--  1 root root 4065438 Feb  5 22:59 initrd.img-4.9.7-sunxi
-rw-r--r--  1 root root       0 Feb  5 22:54 .next
lrwxrwxrwx  1 root root      18 Feb  5 22:58 script.bin -> bin/cubietruck.bin
-rw-r--r--  1 root root 2695178 Feb  2 01:53 System.map-4.9.7-sunxi
lrwxrwxrwx  1 root root      19 Feb  5 22:59 uInitrd -> uInitrd-4.9.7-sunxi
-rw-r--r--  1 root root 4065502 Feb  5 22:59 uInitrd-4.9.7-sunxi
-rwxr-xr-x  1 root root 6037368 Feb  2 01:53 vmlinuz-4.9.7-sunxi
lrwxrwxrwx  1 root root      19 Feb  5 22:54 zImage -> vmlinuz-4.9.7-sunxi

 

root@YourRescueSystems:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# ls -la
total 13100
drwxr-xr-x  6 root root    4096 May  8 20:41 .
drwxr-xr-x 22 root root    4096 Feb  2 02:21 ..
drwxr-xr-x  2 root root    4096 Feb  2 03:20 bin
drwxr-xr-x  2 root root    4096 Oct 24  2016 bin.old
-rwxr-xr-x  1 root root    6944 Sep 16  2015 boot.bmp
-rwxr-xr-x  1 root root    1698 May  7 14:30 boot.cmd
-rwxr-xr-x  1 root root    1749 May  7 14:30 boot.cmd.backup
-rw-r--r--  1 root root    1770 May  7 14:30 boot.scr
-rw-r--r--  1 root root  144620 Feb  2 01:53 config-4.9.7-sunxi
lrwxrwxrwx  1 root root      17 Apr 30 14:30 dtb -> dtb-4.10.12-sunxi
drwxr-xr-x  2 root root    4096 Sep 24  2016 dtb-4.6.3-sunxi
drwxr-xr-x  2 root root    4096 Feb  2 01:53 dtb-4.9.7-sunxi
lrwxrwxrwx  1 root root      16 Feb 25 01:06 dtb.old -> dtb-4.9.12-sunxi
-rw-r--r--  1 root root       0 Apr 30 14:31 .next
lrwxrwxrwx  1 root root      24 Sep 16  2015 script.bin -> /boot/bin/cubietruck.bin
-rw-r--r--  1 root root 2695178 Feb  2 01:53 System.map-4.9.7-sunxi
lrwxrwxrwx  1 root root      21 May  7 12:49 uInitrd -> uInitrd-4.10.12-sunxi
-rw-r--r--  1 root root 4484597 May  7 12:49 uInitrd-4.10.12-sunxi
-rw-r--r--  1 root root       0 Jan  1  1970 .verbose
-rwxr-xr-x  1 root root 6037368 Feb  2 01:53 vmlinuz-4.9.7-sunxi
lrwxrwxrwx  1 root root      19 May  8 20:41 zImage -> vmlinuz-4.9.7-sunxi
root@YourRescueSystems:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot#


So in my case some symlinks still point on ^4.10.*^ files:

 

dtb -> dtb-4.10.12-sunxi (should point on ^dtb-4.9.7-sunxi^)
uInitrd -> uInitrd-4.10.12-sunxi (should point on ^uInitrd-4.9.7-sunxi^ which is missing)

 

And `initrd.img-4.9.7-sunxi` is missing.

 

To get `uInitrd-4.9.7-sunxi` and `initrd.img-4.9.7-sunxi` I flashed `Armbian_5.25_Cubietruck_Debian_jessie_next_4.9.7.img` on another sd-card copied the missing files from `/media/YourUser/SD-cardIDofYourFreshInstalledArmbian/boot/uInitrd-4.9.7-sunxi` to `/media/YourUser/SD-cardIDofYourBrokenArmbian/boot/`.

 

Then I fixed `dtb` and `uInitrd` symlinks in `/media/YourUser/SD-cardIDofYourBrokenArmbian/boot` and deleted all `4.10.12` files via:

 

rm dtb
rm uInitrd
ln -s dtb-4.9.7-sunxi dtb
ln -s uInitrd-4.9.7-sunxi uInitrd
rm *4.10.12*


Example:

 

root@YourRescueSystem:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# ls -la
total 17072
drwxr-xr-x  6 root root    4096 May  8 22:01 .
drwxr-xr-x 22 root root    4096 Feb  2 02:21 ..
drwxr-xr-x  2 root root    4096 Feb  2 03:20 bin
drwxr-xr-x  2 root root    4096 Oct 24  2016 bin.old
-rwxr-xr-x  1 root root    6944 Sep 16  2015 boot.bmp
-rwxr-xr-x  1 root root    1698 May  7 14:30 boot.cmd
-rwxr-xr-x  1 root root    1749 May  7 14:30 boot.cmd.backup
-rw-r--r--  1 root root    1770 May  7 14:30 boot.scr
-rw-r--r--  1 root root  144620 Feb  2 01:53 config-4.9.7-sunxi
lrwxrwxrwx  1 root root      17 Apr 30 14:30 dtb -> dtb-4.10.12-sunxi
drwxr-xr-x  2 root root    4096 Sep 24  2016 dtb-4.6.3-sunxi
drwxr-xr-x  2 root root    4096 Feb  2 01:53 dtb-4.9.7-sunxi
lrwxrwxrwx  1 root root      16 Feb 25 01:06 dtb.old -> dtb-4.9.12-sunxi
-rw-r--r--  1 root root 4065438 May  8 22:13 initrd.img-4.9.7-sunxi
-rw-r--r--  1 root root       0 Apr 30 14:31 .next
lrwxrwxrwx  1 root root      24 Sep 16  2015 script.bin -> /boot/bin/cubietruck.bin
-rw-r--r--  1 root root 2695178 Feb  2 01:53 System.map-4.9.7-sunxi
lrwxrwxrwx  1 root root      21 May  7 12:49 uInitrd -> uInitrd-4.10.12-sunxi
-rw-r--r--  1 root root 4484597 May  7 12:49 uInitrd-4.10.12-sunxi
-rw-r--r--  1 root root 4065502 May  8 22:01 uInitrd-4.9.7-sunxi
-rw-r--r--  1 root root       0 Jan  1  1970 .verbose
-rwxr-xr-x  1 root root 6037368 Feb  2 01:53 vmlinuz-4.9.7-sunxi
lrwxrwxrwx  1 root root      19 May  8 20:41 zImage -> vmlinuz-4.9.7-sunxi
root@YourRescueSystem:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# rm dtb
root@YourRescueSystem:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# rm uInitrd
root@YourRescueSystem:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# ln -s dtb-4.9.7-sunxi dtb
root@YourRescueSystem:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# ln -s uInitrd-4.9.7-sunxi uInitrd
root@YourRescueSystem:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# rm *4.10.12*
root@YourRescueSystem:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot# ls -la
total 16664
drwxr-xr-x  6 root root    4096 May  8 22:16 .
drwxr-xr-x 22 root root    4096 Feb  2 02:21 ..
drwxr-xr-x  2 root root    4096 Feb  2 03:20 bin
drwxr-xr-x  2 root root    4096 Oct 24  2016 bin.old
-rwxr-xr-x  1 root root    6944 Sep 16  2015 boot.bmp
-rwxr-xr-x  1 root root    1698 May  7 14:30 boot.cmd
-rwxr-xr-x  1 root root    1749 May  7 14:30 boot.cmd.backup
-rw-r--r--  1 root root    1770 May  7 14:30 boot.scr
-rw-r--r--  1 root root  144620 Feb  2 01:53 config-4.9.7-sunxi
lrwxrwxrwx  1 root root      15 May  8 22:04 dtb -> dtb-4.9.7-sunxi
drwxr-xr-x  2 root root    4096 Sep 24  2016 dtb-4.6.3-sunxi
drwxr-xr-x  2 root root    4096 Feb  2 01:53 dtb-4.9.7-sunxi
lrwxrwxrwx  1 root root      16 Feb 25 01:06 dtb.old -> dtb-4.9.12-sunxi
-rw-r--r--  1 root root 4065438 May  8 22:13 initrd.img-4.9.7-sunxi
-rw-r--r--  1 root root       0 Apr 30 14:31 .next
lrwxrwxrwx  1 root root      24 Sep 16  2015 script.bin -> /boot/bin/cubietruck.bin
-rw-r--r--  1 root root 2695178 Feb  2 01:53 System.map-4.9.7-sunxi
lrwxrwxrwx  1 root root      19 May  8 22:04 uInitrd -> uInitrd-4.9.7-sunxi
-rw-r--r--  1 root root 4065502 May  8 22:01 uInitrd-4.9.7-sunxi
-rw-r--r--  1 root root       0 Jan  1  1970 .verbose
-rwxr-xr-x  1 root root 6037368 Feb  2 01:53 vmlinuz-4.9.7-sunxi
lrwxrwxrwx  1 root root      19 May  8 20:41 zImage -> vmlinuz-4.9.7-sunxi
root@YourRescueSystem:/media/YourUser/SD-cardIDofYourBrokenArmbian/boot#


Comparison with FreshInstalledArmbian:

 

root@YourRescueSystem:/media/YourUser/SD-cardIDofYourFreshInstalledArmbian/boot# ls -la
total 16656
drwxr-xr-x  4 root root    4096 May  8 21:51 .
drwxr-xr-x 22 root root    4096 Feb  5 22:54 ..
-rw-r--r--  1 root root     114 May  8 21:51 armbianEnv.txt
drwxr-xr-x  2 root root    4096 Feb  5 22:58 bin
-rw-r--r--  1 root root    6944 Feb  5 22:59 boot.bmp
-rw-r--r--  1 root root    2580 Feb  5 22:53 boot.cmd
-rw-r--r--  1 root root    2652 Feb  5 23:00 boot.scr
-rw-r--r--  1 root root  144620 Feb  2 01:53 config-4.9.7-sunxi
lrwxrwxrwx  1 root root      15 Feb  5 22:58 dtb -> dtb-4.9.7-sunxi
drwxr-xr-x  2 root root    4096 Feb  5 22:58 dtb-4.9.7-sunxi
-rw-r--r--  1 root root 4065438 Feb  5 22:59 initrd.img-4.9.7-sunxi
-rw-r--r--  1 root root       0 Feb  5 22:54 .next
lrwxrwxrwx  1 root root      18 Feb  5 22:58 script.bin -> bin/cubietruck.bin
-rw-r--r--  1 root root 2695178 Feb  2 01:53 System.map-4.9.7-sunxi
lrwxrwxrwx  1 root root      19 Feb  5 22:59 uInitrd -> uInitrd-4.9.7-sunxi
-rw-r--r--  1 root root 4065502 Feb  5 22:59 uInitrd-4.9.7-sunxi
-rwxr-xr-x  1 root root 6037368 Feb  2 01:53 vmlinuz-4.9.7-sunxi
lrwxrwxrwx  1 root root      19 Feb  5 22:54 zImage -> vmlinuz-4.9.7-sunxi


Magic moment... ...armbian is booting again. :)

Edited by saljut7
markdown -> html
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines