Jump to content

Cubietruck not booting anymore after apt update/upgrade


Don Pedro

Recommended Posts

Hello,

 

after the usual apt update/apt upgrade the OS requested a reboot. However it then fails to boot. Here's the output of the console:

 

Quote

U-Boot 2017.11-armbian (Jan 24 2018 - 22:33:23 +0100) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Cubietech Cubietruck
I2C:   ready
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Card did not respond to voltage select!
mmc_init: -95, time 22
*** Warning - MMC init failed, using default environment

Setting up a 1024x768 vga console (overscan 0x0)
In:    serial
Out:   vga
Err:   vga
Allwinner mUSB OTG (Peripheral)
SCSI:  Target spinup took 0 ms.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c50000
Warning: usb_ether using MAC address from ROM
, eth1: usb_ether
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3708 bytes read in 202 ms (17.6 KiB/s)
## Executing script at 43100000
Wrong image format for "source" command

SCRIPT FAILED: continuing...
Card did not respond to voltage select!
mmc_init: -95, time 25
scanning bus for devices...
  Device 0: (0:0) Vendor: ATA Prod.: ST4000VN000-1H41 Rev: SC46
            Type: Hard Disk
            Capacity: 3815447.8 MB = 3726.0 GB (7814037168 x 512)
Found 1 device(s).

Device 0: (0:0) Vendor: ATA Prod.: ST4000VN000-1H41 Rev: SC46
            Type: Hard Disk
            Capacity: 3815447.8 MB = 3726.0 GB (7814037168 x 512)
... is now current device
Scanning scsi 0:1...

Device 0: device type unknown
... is now current device
** Bad device usb 0 **
** Bad device usb 0 **
ethernet@01c50000 Waiting for PHY auto negotiation to complete...... done
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.178.34 (11 ms)
*** Warning: no boot file name; using 'C0A8B222.img'
Using ethernet@01c50000 device
TFTP from server 192.168.178.1; our IP address is 192.168.178.34
Filename 'C0A8B222.img'.
Load address: 0x42000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-02-44-06-c3-35-61
Speed: 1000, full duplex
Using ethernet@01c50000 device
TFTP from server 192.168.178.1; our IP address is 192.168.178.34
Filename 'pxelinux.cfg/01-02-44-06-c3-35-61'.
Load address: 0x43200000
Loading: T T T

I guess the critical stuff is what I marked in bold? So what happened here and what to do to recover? Not keen to reinstall the whole OS...

 

Edit:

I pulled th SD-Card and read it from a Linux PC. When I take a look at /boot/boot.scr it is clearly corrupted! If I'm correct there's binary data inside, however in the hexdata I can see some segments with ASCII text fragments inside that releates to my private data (e.g. names of mp3 files!!) and that shoud definitely not be in boot.scr. So whatever happened, something during apt update/upgrade killed the boot.scr - and hopefully nothing else. Can I somehow repair boot.scr without reinstalling the whole OS? My Cubietruck is on Stretch.

 

Edit:

Further analysis showed that several more files than just boot.scr from /boot have been corrupted, where originally was a script there's binary junk now. So probably I need to reinstall the OS, as I cannot know which files were destroyed. The question here of course is what did corrupt all those file in /boot? I'm aware that I might never find out. The SD Card used is not a no-name product, it's an emtec (http://www.emtec-international.com/de/home), so this should not be due to a crappy card. So what remains is a stale feeling about the system suddenly dying... :-//

 

THX

 

Don

 

Link to comment
Share on other sites

On 19. 3. 2018 at 10:47 PM, Don Pedro said:

When I take a look at /boot/boot.scr it is clearly corrupted!


boot.scr is binary made from boot.cmd ... how it is made is written in the last line.

 

On 19. 3. 2018 at 10:47 PM, Don Pedro said:

The SD Card used is not a no-name product,


This tells nothing. All SD cards die. Sooner or later. Since I am dealing with Armbian I already threw away 10-15 cards and at least half of them were claimed to be the best in their (consumer) class. 

 

An upgrade is very stressful for SD card. 

Link to comment
Share on other sites

4 hours ago, Igor said:

boot.scr is binary made from boot.cmd ... how it is made is written in the last line.

I know. My boot.cmd also contains crap :-/

Recreating boot.scr was my first attempt. But as we engineers say: Junk in, junk out. Is that already a FIFO? ;-)

I extracted boot.scr from the original armbian image. I also was able to create one on a Linux machine alternatively. However when I realized even more files got corrupted I decide to dump the installation on the SD-card, you never know what other files were corrupted and I'm not keen on a semi-broken system  showing mysterious errors.

 

Quote

This tells nothing. All SD cards die. Sooner or later. Since I am dealing with Armbian I already threw away 10-15 cards and at least half of them were claimed to be the best in their (consumer) class. 

 

An upgrade is very stressful for SD card.

 

Of course a quality card doesn't mean it ain't gonna die one day. Plus SD card has the disadvantage that it can't be trimmed like an SSD. However this card is not old, I just setup the whole system (not upgraded) a couple of weeks ago, the card was newly bought for that purpose. I will check it with a test program before reinstalling the OS.

 

Edit:

I tested the card with Heise's H2testw and it found broken areas on the card. So it seems my card is broken. I will pick a new one and reinstall the OS.

 

THX

 

Don

 

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