1 1
mokanman

SD Card Boot Recovery

Recommended Posts

We had a power outage the other day and though I have UPS coverage on all my computers, TV's, switches, router and Arm boards I forgot to shut down the ARM boards gracefully before shutting off the UPS that protects them.  Later, all my PI's booted back up just fine but my Le Potato is not responding.  I verified that the SD card still shows a Linux system but am not sure what all to look at to repair boot problems.  I tested the Le Potato with another fresh Armbian install and it booted up just fine so the hardware is not an issue.  I am lamenting not having made a backup of the card before this happened but was still tweaking stuff and didn't think about it (next time I will backup sooner).  Anyway, I originally spent a lot of time overcoming all kinds of initial set-up and configuration issues and actually had a Spigot Minecraft server running that was very responsive so rather than spend hours recreating it I was hoping to find a way to recover boot capability.  One of the things I had a heck of a time getting under control was a static MAC address (and I don't remember exactly how I finally overcame that problem) which I prefer so my router can assign a specific IP.  Since the board is not booting I can't get to any log files, however, I can view the SD card on my Ubuntu desktop computer so I can possibly find something there if it is actually getting far enough to create a log file.  Any helpful suggestions for finding a log and/or recovering boot capability will be appreciated.

Share this post


Link to post
Share on other sites
28 minutes ago, mokanman said:

 Any helpful suggestions for finding a log and/or recovering boot capability will be appreciated.

How about inserting the microsd-card in another linux system and doing a fsck on the filesystem of the micro-sd card?

If you are lucky fsck could fix this for you?

Share this post


Link to post
Share on other sites
4 minutes ago, guidol said:

How about inserting the microsd-card in another linux system and doing a fsck on the filesystem of the micro-sd card?

If you are lucky fsck could fix this for you?

Thanks for the suggestion.  I forgot to mention I tried that already and though it appeared to clean up some stuff it did not help with the boot.

Share this post


Link to post
Share on other sites

Hmm how about a "quick &dirty" way?

Setting up a empty/clean/fresh system with the same kernel/system and copy all the clean old files in the new installation...and see what happens.

Maybe less work as setting up the complete system again? :)

Share this post


Link to post
Share on other sites
1 hour ago, guidol said:

Hmm how about a "quick &dirty" way?

Setting up a empty/clean/fresh system with the same kernel/system and copy all the clean old files in the new installation...and see what happens.

Maybe less work as setting up the complete system again? :)

Great minds think alike!  That's exactly what I've been working on for a couple of hours now.  When I first tried to copy, it told me that there wasn't enough space.  It told me that the 277.6 GB (on my 16 GB card!) was too much to copy to my other 16 GB card.  I drilled down to a find a file in /lib/udev/rules.d called "90-alsa-restore.rules" that was showing a supposed size of 274.9 so I copied all the files but that one (it already existed there with same modified date anyway but only 489 bytes!).  File copy is taking a long time.  If this doesn't work then I'll just start from scratch I guess.

Share this post


Link to post
Share on other sites
2 hours ago, guidol said:

Setting up a empty/clean/fresh system with the same kernel/system and copy all the clean old files in the new installation...and see what happens.

 

Well, I'm sorry to say this did not work.  Since I really have no way of knowing what other files may have been corrupted it is hard to determine what is actually wrong.  Anyway, I appreciate your suggestions as it at least validated my thinking.  I'm going to head outside and work in the yard for a while so I can rest my brain and exercise my body instead.  When I come back in I'll start working on it from scratch again.  Since I created an img file from the damaged SD card I'll at least have somewhat of a roadmap to see what I had originally set up.  Maybe before I work on recreating I'll do some research on Le Potato LED blink codes.  Anyway, thanks again!

Share this post


Link to post
Share on other sites
4 hours ago, TonyMac32 said:

Is it even attempting to boot?  Any chance of a serial terminal?

 

Not seeing anything on the screen but I don't know what it may be doing behind the scene.  What is a serial terminal?  Does my ignorance mean that there probably is not a chance of a serial terminal?

Share this post


Link to post
Share on other sites
10 minutes ago, mokanman said:

Does my ignorance mean that there probably is not a chance of a serial terminal?

:lol: Well, yes and no.  On the Le Potato, the 3 pins beside the HDMI are a serial port, where the bootloader and kernel send boot messages and a console to log into the device directly.  If you don't know what it is, then you probably don't have an "FTDI friend" or other adapter to interface to it.  That's ok, just thought I would ask.  Hard to debug much farther I'm afraid... :-/

Share this post


Link to post
Share on other sites

IMHO

1. Create a full backup image from the SD card before further operations (dd if= of=).

2. Copy u-boot with a working SD card not working on the SD card (using dd two command with saving the partition table). Check the start.

3. Copy replace all files from /boot partition (kernel, initrd, etc.). Check the start.

4. If that doesn't help, boot from a working SD card, plug in a USB adapter to a non-working SD card, use "chroot" in a non-working SD card and watch\check the basic startup files. Or gradually shift from non-working Sd card in a working system all the settings and the files you need.

Share this post


Link to post
Share on other sites
14 hours ago, TonyMac32 said:

:lol: ... "FTDI friend" or other adapter to interface to it.

 

Are these expensive or hard to come by?  If it would come in handy in the future I would get one (some) if it's (they're) not astronomically priced.  Will it work on a Raspberry or Banana Pi as well?

Share this post


Link to post
Share on other sites
13 hours ago, balbes150 said:

IMHO

1. Create a full backup image from the SD card before further operations (dd if= of=).

2. Copy u-boot with a working SD card not working on the SD card (using dd two command with saving the partition table). Check the start.

3. Copy replace all files from /boot partition (kernel, initrd, etc.). Check the start.

4. If that doesn't help, boot from a working SD card, plug in a USB adapter to a non-working SD card, use "chroot" in a non-working SD card and watch\check the basic startup files. Or gradually shift from non-working Sd card in a working system all the settings and the files you need.

 

I already wrote over that card trying the steps outlined in one of the above posts but I created a disk image first using the Disks GUI option for that (I think that is basically a front end to dd).  So I think I have number one on your list done.  I could use a little more guidance on number 2 and 3 on your list.  I have a working SD card (and or can create another one from the Armbian download) but am not familiar with u-boot or what the specific dd command would be.  Same with number 3, do I just copy from the /boot directory or is there more to it than that.  Please excuse my lack of knowledge on this and thanks for your help.

Share this post


Link to post
Share on other sites
21 minutes ago, mokanman said:

Will it work on a Raspberry or Banana Pi as well?

 

Available on Amazon and from most SBC companies, most are 3.3 volt logic, some (Odroid XU4) are 1.8 volt.  It is a USB to serial uart adapter.

Share this post


Link to post
Share on other sites
3 hours ago, TonyMac32 said:

 

Available on Amazon and from most SBC companies, most are 3.3 volt logic, some (Odroid XU4) are 1.8 volt.  It is a USB to serial uart adapter.

 

Appreciate the tip.  Found one on eBay I'm going to order tonight.

Share this post


Link to post
Share on other sites

2. If you do not know how to make a copy of u-boot from a working SD card, you can ask the developers of the image for your TV box for the necessary file. It's not a big file "u-boot.bin.sd.bin". To record a working u-boot in two teams.

 

dd if=u-boot.bin.sd.bin of=/dev/mmcblk0 conv=fsync bs=1 count=442

 

dd if=u-boot.bin.sd.bin of=/dev/mmcblk0 conv=fsync bs=512 skip=1 seek=1

 

Note that the name mmcblk0 needs to be replaced with the name of your SD card in the system.

 

 

3. There are several important files that are involved in the startup process, which are used in your Armbian image, it is better to check with the image developer. You can try to copy all files from /boot.

Share this post


Link to post
Share on other sites
(edited)

Been away for a while due to wife's surgery.  Have had to play nurse maid as well as doing tasks she normally does (not to mention my own).  Anyway, with all that going on have not been able to move forward with this issue until now.  I did buy a USB to serial UART adapter and it was relatively easy to connect.  I am using gkterm from Ubuntu to monitor the boot process and have the following output to share.  I removed power to Le Potato when I assumed it was not going to recover from the last set of recurring errors.  Not being familiar with what it is showing me I'm hoping somebody can point me in the right direction.  There are many occurrences that look like errors prior to those at the end and though some of them may be negligible I have no idea which ones are important:

Spoiler

GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:0;RCY:0;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;0.0;CHK:0;
no sdio debug board detected
TE: 1897132

BL2 Built : 11:58:42, May 27 2017.
gxl gc3c9a84 - xiaobo.gu@droid05

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 6
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - PASS
Rank0: 1024MB(auto)-2T-13
Rank1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from SD, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from SD, src: 0x00020200, des: 0x05100000, size: 0x0002c600
Load bl33 from SD, src: 0x00050200, des: 0x01000000, size: 0x00064200
NOTICE:  BL3-1: v1.0(release):5fba975
NOTICE:  BL3-1: Built : 14:24:33, Jun 15 2017
[BL31]: GXL CPU setup!
NOTICE:  BL31: BL33 decompress pass
mpu_config_enable:ok
[Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07]
OPS=0x82
51 8f f6 f1 e0 62 1 14 d3 65 af 54 [2.233545 Inits done]
secure task start!
high task start!
low task start!
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2015.01-g573eb26-dirty (Sep 19 2017 - 00:44:24)

DRAM:  2 GiB
Relocation Offset is: 76eb8000
register usb cfg[0][1] = 0000000077f5ba80
[CANVAS]canvas init
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
vpu: vpu_clk_gate_init_off
vpp: vpp_init
boot_device_flag : 1
Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc.
init bus_cycle=6, bus_timing=7, system=5.0ns
reset failed
get_chip_type and ret:fffffffe
get_chip_type and ret:fffffffe
chip detect failed and ret:fffffffe
nandphy_init failed and ret=0xfffffff1
MMC:   aml_priv->desc_buf = 0x0000000073eb86b0
aml_priv->desc_buf = 0x0000000073eba9d0
SDIO Port B: 0, SDIO Port C: 1
MMC init failed
Using default environment

In:    serial
Out:   serial
Err:   serial
reboot_mode=cold_boot
hpd_state=0
cvbs performance type = 6, table = 0
[store]To run cmd[emmc dtb_read 0x1000000 0x40000]
_dtb_init()-956: mmc init failed
card in
init_part() 278: PART_TYPE_DOS
[mmc_init] mmc init success
Device: SDIO Port B
Manufacturer ID: 1d
OEM: 4144
Name: SD    
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 15.4 GiB
mmc clock: 40000000
Bus Width: 4-bit
** Unrecognized filesystem type **
Net:   dwmac.c9410000[KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000

[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[CANVAS]addr=0x3d800000 width=5760, height=2160
38518 bytes read in 12 ms (3.1 MiB/s)
[OSD]ERR: error: gdev.bpp 3, but bmp.bpp 4
bmp - manipulate BMP image data

Usage:
bmp info <imageAddr>              - display image info
bmp display <imageAddr> [x y]     - display image at x,y
bmp scale [imageAddr scaleAddr]   - scale image

Hit Enter or space or Ctrl+C key to stop autoboot -- :  0
(Re)start USB...
USB0:   USB3.0 XHCI init start
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
Device: SDIO Port B
Manufacturer ID: 1d
OEM: 4144
Name: SD    
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 15.4 GiB
mmc clock: 40000000
Bus Width: 4-bit
564 bytes read in 14 ms (39.1 KiB/s)
## Executing script at 01020000
5631520 bytes read in 340 ms (15.8 MiB/s)
25111 bytes read in 32 ms (765.6 KiB/s)
14965312 bytes read in 861 ms (16.6 MiB/s)
ee_gate_off ...
## Booting kernel from Legacy Image at 01080000 ...
   Image Name:   Linux kernel
   Image Type:   AArch64 Linux Kernel Image (uncompressed)
   Data Size:    14965248 Bytes = 14.3 MiB
   Load Address: 01080000
   Entry Point:  01080000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 39000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    5631456 Bytes = 5.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
load dtb from 0x1000000 ......
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x1000000
   Loading Kernel Image(COMP_NONE) ... OK
   kernel loaded at 0x01080000, end = 0x01ec5a00
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
[rsvmem] fdt get prop fail.
   Loading Ramdisk to 3faa1000, end 3ffffde0 ... OK
   Loading Device Tree to 000000001fff6000, end 000000001ffff216 ... OK
fdt_instaboot: no instaboot image

Starting kernel ...

uboot time: 11339340 us
[    1.408840] dmi: Firmware registration failed.
[    1.683010] meson_gx_pwrc_vpu c8100000.sys-ctrl:power-controller-vpu: failed to get reset lines
[    1.706502] mdio-mux-mmioreg c883455c.eth-phy-mux: failed to register mdio-mux bus /soc/periphs@c8834000/eth-phy-mux
[    1.767012] meson-gx-mmc d0074000.mmc: no support for card's volts
[    1.767549] mmc0: error -22 whilst initialising SDIO card
[    1.776868] meson-gx-mmc d0074000.mmc: no support for card's volts
[    1.779064] mmc0: error -22 whilst initialising MMC card
[    1.808514] mdio-mux-mmioreg c883455c.eth-phy-mux: failed to register mdio-mux bus /soc/periphs@c8834000/eth-phy-mux
domain-0 init dvfs: 4
[    1.863286] mdio-mux-mmioreg c883455c.eth-phy-mux: failed to register mdio-mux bus /soc/periphs@c8834000/eth-phy-mux
Loading, please wait...
[    1.911696] mdio-mux-mmioreg c883455c.eth-phy-mux: failed to register mdio-mux bus /soc/periphs@c8834000/eth-phy-mux
starting version 229
[    2.116855] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[    2.122455] meson-drm d0100000.vpu: Failed to create debugfs directory
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk1p1] fsck.ext4 -y -C0 /dev/mmcblk1p1
e2fsck 1.42.13 (17-May-2015)
/dev/mmcblk1p1: recovering journal
/dev/mmcblk1p1: clean, 124391/1011840 files, 825141/4045568 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Ubuntu 16.04.4 LTS!

[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Started Trigger resolvconf update for networkd DNS.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Reached target Swap.
[  OK  ] Listening on Journal Socket.
[  OK  ] Reached target User and Group Name Lookups.
[  OK  ] Listening on Syslog Socket.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Created slice System Slice.
         Starting Set console keymap...
         Starting Load Kernel Modules...
         Mounting POSIX Message Queue File System...
         Mounting Debug File System...
         Starting Remount Root and Kernel File Systems...
         Starting Nameserver information manager...
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Set up automount Arbitrary Executab...ats File System Automount Point.
         Mounting Huge Pages File System...
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
         Starting Create list of required st... nodes for the current kernel...
[  OK  ] Listening on udev Control Socket.
         Starting Restore / save the current clock...
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Mounted Debug File System.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Set console keymap.
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Create list of required sta...ce nodes for the current kernel.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Nameserver information manager.
[  OK  ] Reached target Network (Pre).
         Starting Create Static Device Nodes in /dev...
         Starting udev Coldplug all Devices...
         Starting Load/Save Random Seed...
         Mounting Configuration File System...
         Starting Apply Kernel Variables...
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted /tmp.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Reached target Local File Systems.
         Starting Raise network interfaces...
         Starting Armbian enhanced Log2Ram...
         Starting Odroid C2 HDMI init...
         Starting Set console font and keymap...
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
[  OK  ] Started Odroid C2 HDMI init.
[  OK  ] Started Set console font and keymap.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Started Armbian enhanced Log2Ram.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Raise network interfaces.
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[ TIME ] Timed out waiting for device dev-ttyAML0.device.
[DEPEND] Dependency failed for Serial Getty on ttyAML0.
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[  OK  ] Stopped udev Kernel Device Manager.
         Starting udev Kernel Device Manager...
[ ***  ] A start job is running for udev Kernel Device Manager (35s / 1min 30s)

 

 

 

 

Edited by Igor
spoilers

Share this post


Link to post
Share on other sites
10 hours ago, mokanman said:

There are many occurrences that look like errors prior to those at the end and though some of them may be negligible I have no idea which ones are important:


We made new images a few days ago. Try these: https://www.armbian.com/lepotato/ (v5.49 Debian Stretch Default with 4.14.52)

Share this post


Link to post
Share on other sites
7 hours ago, Igor said:


We made new images a few days ago. Try these: https://www.armbian.com/lepotato/ (v5.49 Debian Stretch Default with 4.14.52)

 

Thanks for your reply Igor.  As I stated in my first post, I was able to successfully boot with a fresh install.  The problem is that I had originally spent a lot of time tweaking the configuration and I am trying to avoid having to go through all those steps again because I did not document everything I did.  It would be somewhat of a learning curve though I'm sure I can figure it out if I must.  By the way,  how was it you hid the output I pasted in my posting?  I see the word "spoilers" so maybe that eyeball icon is how it is done?  I was looking for a way to do that before I posted but the word "spoilers" didn't seem like an accurate description.

Share this post


Link to post
Share on other sites
2 minutes ago, mokanman said:

As I stated in my first post, I was able to successfully boot with a fresh install. 


Got it. Well, then we are more talking about a backup / restore situation here. 

I tend to only backup the data and not the operating system. That is easy to install from scratch and when you do this, you can jump to the latest version ... A way to do this is to make install scripts. A direct consequence of having an easy to reinstall everything is this: https://github.com/armbian/config/blob/master/debian-software I made it initially to set up a (fairly complicated) LAMP setup for my personal needs. I also made a simple script to dump and import SQL data and tar/untar data directories and save configs that were custom and that's about it. I know it is a little more work for a start, but a backup is populated with as less junk as possible and I could easily migrate it to different systems and hardware platforms. And I acttually did it several times, jumping between ARM and X86, Wheezy to Stretch.

 

8 minutes ago, mokanman said:

I see the word "spoilers"

Spoiler

image.png

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
1 1