(non-)boot messages

AmigaOne X1000 platform specific issues related to Linux only.

(non-)boot messages

Postby kilaueabart » Sat Nov 14, 2015 4:10 am

I had what seemed like a successful install of Ubuntu 15.10 MATE. Or so I thought until I tried to actually boot it.

It doesn't quite boot, in spite of a lot of encouraging messages. I photgraphed them and typed them out for easier readability, and pasted them below.

I don't know how to interpret them, and hope to get some tutoring. There are a lot of "[ OK ]"s that end abruptly, forcing me to hit the reset button after waiting a long time. The only clearly negative lines are on fresh screen with two penguings at the top with a couple "couldn't"s and a "quitting," followed by a couple "Failed," the second in red capital letters. Perhaps these few lines are the key to my problem, but then why does it seem to continue booting, and with so much success, before it quits for good?


CFE> setenv bootargs "root=/dev/sdb2 quiet ro splash"
*** command status = 0
CFE> boot -elf -noints -fatfs cf0:vmlinus-4.1
Loader:elf Filesys:fat Dev:cf0 File:vmlinus-4.1 Options:(null)
Loading: 0x0000000000000000/20706688 0x000000000013BF580/1579572
Starting program at 0x0000000000000000
OF stdout device is: /bootconsole
Preparing to boot Linux version 4.1.10_A-EON_AMIGA_one_X1000_Nem[edge of photo]
sion 4.9.2 (Debian 4.9.2-21) ) #1 SMP Mon Oct 5 20:19:17 CEST 20[edge of photo]
Detected machine type: 0000000000000500
command line: root=/dev/sdb2 quiet ro splash
memory layout at init:
memory_limit : 0000000000000000 (16 MB aligned)
alloc_bottom : 0000000001545000
alloc_top : 0000000030000000
alloc_top_hi : 0000000080000000
[bottom edge of first photo]

[some black screens]

[two penguins at top of screen]
[guessing at fuzzy text:] NOMO SB600 IOB base c0000000
no UART detected at 0x1
EXT3-fs (sdb2): error: couldn't mount because of unsupported optional features (Z[or 2?]40)
EXT2-fs (sdb2): error: couldn't mount because of unsupported optional features (Z[or 2?]40)
hld-generic 000C:046D:C52B.0003: device has no listeners, quitting
system1111: Failed to start Load Kernel Modules.
[(in red)FAILED] Failed to start Load Kernel Modules.
See 'system status syst??d modules-load.service' for details.
Starting apply Kernel Variables...
Mounting FUSE Control File System...
Starting ?dcv Kernel Device Manager...
[ OK ]Listening on Syslog Socket. [All "OK"s from here on are green]
Starting Journal Service...
[ OK ] Mounted Confirmation File System.
[ OK ] Mounted FUSE Control File System.
[ OK ] Started Apply Normal Variables.
[ OK ] Started udev Coldplug all Devices.
Starting File System Check on Boot Device...
Starting Show Plymouth Boot Screen
[ OK ] Started File System Check Daemon to report status.

[some black screens, followed by one with "Ubuntu 15.10," and four white dots under those words,
in the middle, then more black screens]

[ OK ] Started Nameserver information manager.
Starting LSB: Raise network interfaces....
Starting Update UTMP about System Boot/Shutdown...
Starting Network Time Synchronization...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Started Set console keymap.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Time Synchronized.
[ OK ] Started LSB raise network interfaces..
[ OK ] Reached target System Initialization.
[ OK ] Listening on CUPS Scheduler.
[ OK ] Reached target Paths.
[ OK ] Reached target Basic System.
[ OK ] Started run anacron jobs.
Starting Network Manager...
Starting LSB: daemon to balance interrupts for SMP system...
Starting Restore /etc/resolve.conf if the system crashed before the ppp link[edge of photo]
Starting Permit User Sessions...
Starting LSB: Set the CPU frequency Scaling governor to "ondemand"...
Starting Initialize hardware monitoring sensors...
Starting LSB: handle special hotkeys of Apple computers...
[ OK ] Started crash report submission daemon.
[ OK ] Started regular background program processing daemon.
[ OK ] Started D-Bus System Message Bus.
Starting System Logging Service...
[ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
Starting LSB: automatic crash report generation...
Starting Avahi mDNS/DNS-SD Stack...
Starting Login Service...
Starting Accounts Service...
Starting Modem Manager...
[ OK ] Started CUPS Scheduler.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Timers.
[ OK ] Started LSB: daemon to balance interrupts for SMP systems.
[ OK ] Started Restore /etc/resolv.conf if the system crashed before the ppp link was [edge of photo]
[ OK ] Started Permit User Sessions.
[ OK ] Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
[ OK ] Started LSB: handle special hotkeys of Apple computers.
[ OK ] Started System Logging Service.
[ OK ] Started Initialize hardware monitoring sensors.
[ OK ] Started LSB: automatic crash report generation.
[ OK ] Started Network Manager.
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Started Login Service.
Starting Authenticate and Authorize Users to Run Privileged Tasks...
[ OK ] Started Make remote CUPS printers available.
[ OK ] Reached target Network.
[ OK ] Reached target Network is Online.
Starting LSB: disk temperature monitoring daemon...
Starting LSB: Tool to automatically collect and submit kernel crash signatur[edge of photo]
Starting /etc/rc.local Compatibility...
Starting Light Display Manager...
[ OK ] Started /etc/rc.local Compatibility.
Starting Wait for Plymouth Boot Screen to Quit...
[ OK ] LSB: disk temperature monitoring daemon.
[ OK ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[ OK ] Started Accounts Service.
[ OK ] Started Modem Manager.
[ OK ] Started LSB: Tool to automatically collect kernel crash signatur[edge of photo]
User avatar
kilaueabart
 
Posts: 471
Joined: Mon Mar 05, 2012 3:36 am

Re: (non-)boot messages

Postby salass00 » Sat Nov 14, 2015 2:23 pm

kilaueabart wrote:[(in red)FAILED] Failed to start Load Kernel Modules.


I get this message every time I start Debian Jessie on a G4 PowerBook and it boots up just fine anyway so it can't be that serious (for me at least).
User avatar
salass00
AmigaOS Core Developer
AmigaOS Core Developer
 
Posts: 502
Joined: Sat Jun 18, 2011 4:12 pm
Location: Finland

Re: (non-)boot messages

Postby mechanic » Sat Nov 14, 2015 4:35 pm

EXT3-fs (sdb2): error: couldn't mount because of unsupported optional features (Z[or 2?]40)
EXT2-fs (sdb2): error: couldn't mount because of unsupported optional features (Z[or 2?]40)

That is a killer right there. If it can't mount root it can't read modules or any thing else.

It looks like you are using a separate HD for Linux. I don't use Ubuntu so have no idea of it's installer or HD setup proceedure.

If your kernel is on a CF card, why is root on sdb2? and not on sdb1.
A-Eon A1X1000
User avatar
mechanic
 
Posts: 486
Joined: Sat Jun 25, 2011 10:22 pm

Re: (non-)boot messages

Postby kilaueabart » Sun Nov 15, 2015 3:58 am

I have Ubuntu 12.04 LST on /dev/sdb1. It always boots just fine. But I think I'll try photo'ing the startup messages I get with it, and compare them with the 15.10 messages. (They go by way too fast to read with my bare eyes.)

As a matter of fact, it seems to me I usually get those "couldn't mount because of" notices when I boot 12.04 too.
User avatar
kilaueabart
 
Posts: 471
Joined: Mon Mar 05, 2012 3:36 am

Re: (non-)boot messages

Postby kilaueabart » Sun Nov 29, 2015 4:54 am

mechanic wrote:EXT3-fs (sdb2): error: couldn't mount because of unsupported optional features (Z[or 2?]40)
EXT2-fs (sdb2): error: couldn't mount because of unsupported optional features (Z[or 2?]40)

That is a killer right there. If it can't mount root it can't read modules or any thing else.

As I thought when I first replied to this, I do get those EXT3-fs and EXT2-fs error messages when I boot Ubuntu 12.04 LST, and it still (usually) boots just fine, so that presumably has nothing to do with my inability to launch Ubuntu 15:10 (Wily).

I photoed a recent 12.04 launch and copied out the messages, as quoted below. What shows above the line of "***.." inserted by me is what I always get when I start Ubuntu 12.04. What comes after that line was a special treat, just that one time.

After all that, Ubuntu 12.04 came up, but not fully usable. It was mounted "read only"! So I tried to restart it and it failed to come up at all!

For those two attempts I was using kernel 4.1. After the complete failure I tried 4.3 and was fully successful. And ever since then I have been able to boot with with 4.1. Brings to mind the old saying, "Computers is weird."

NEMO SB600 108 base a0000000
no UART detected at 0x1
EXT3-fs (sdb1): error: couldn't mount because of unsupported optional features (240)
EXT3-fs (sdb1): error: couldn't mount because of unsupported optional features (244)
hid-generic 0003:046D:C528.0003: device has no listeners, quitting
**********************************************
Filesystem check or mount failed.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and continue booting after re-trying
filesystems. Any further errors will be ignored
root@bart-desktop:~# Inode 4980753 was part of the orphaned inode list. FIXED.
Inode 6815757 was part of the orphaned inode list. FIXED.
Inode 6815930 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
ata2.00: exception Emask: 0x50 SAct 0x3 SErr 0x680900 action 0x6 frozen
ata2.00: irq_stat 0x08000000, interface fatal error
ata2: SError: [ UnrecovData HostInt 10888 BadCRC Handshk ]
ata2.00: failed command: READ FPDHA QUEUED
ata2.00: cmd 60/f8:00:e8:14:81/00:00:04:00:00/40 tag 0 ncq 126976 in
res 40/f8:00:e8:14:81/00:00:04:00:00/40 Emask 0x50 (ATA bus error)
ata2.00: status: [ DRDY ]
ata2.00: failed command: READ FPDMA QUEUED
ata2.00: cmd 60/08:08:e0:15:8a/00:00:04:00:00/40 tag 1 ncq 4096 in
res 40/f8:00:e8:14:81/00:00:04:00:00/40 Emask 0x50 (ATA bus error)
ata2.00: status: [ DRDY ]
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(27956270--27356272) -27356753 -(27356790--27356798) -27356808
Fix? yes

Free blocks count wrong for group #834 (24751, counted=24765).
Fix? yes

Free blocks count wrong (34507526, counted=34507540).
Fix? yes

Inode bitmap differences: -1575142 -1575166 -4980753 -6815797 -6815930
Fix? yes

Free inodes count wrong for group #192 (2491, counted=2493).
Fix? yes

Free inodes count wrong for group #608 (8167, counted=8168).
Fix? yes

Free inodes count wrong for group #832 (438, counted=440).
Fix? yes

Free inodes count wrong (9185675, counted=9185680).
Fix? yes

/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: ***** REBOOT LINUX ******
/dev/sdb1: 415344/9601024 files (0.2% non-contiguous), 3892460/38400000 blocks
_
User avatar
kilaueabart
 
Posts: 471
Joined: Mon Mar 05, 2012 3:36 am


Return to Platform: AmigaOne X1000 - Linux Only

Who is online

Users browsing this forum: No registered users and 2 guests

cron