Interesting boot failure when starting Centaurus 3.5 r4 TDE

bin · 2019-03-28 18:06

I decided to try out the latest TDE Centaurus r4 on an Acer laptop which has run other linux quite happily.

Ran fine on live and did standard install as normal.

Reboot:-

Loading Q4OS operating system...
Loading initial ramdisk...

Normally at this point it runs fsck on (my) sda1

BUT - Flashing flat cursor and that's your lot mate......no boot.

Hmmmm.....went back and installed r3 which restarted OK.

Ran upgrade - rebooted - back to stuck prompt - not looking at hard disk, just sitting there.

Rebooted to grub>recovery mode.

Booted fine. Rebooted, all OK - Power down and start - all OK.

I have no idea which part of the upgrade was responsible but there was a grub update and that sort of seems a likely candidate. That would not explain why the r4 install failed to boot after installation. I don't really want to try again with r4 as I'm there via update.

Just flagging this in case anyone else has similar issues.

System:    Host: flopsy Kernel: 4.19.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Trinity R14.0.6 
           Distro: Q4OS 3.5.3-n1 base: Debian GNU/Linux buster/sid 
Machine:   Type: Other-vm? System: Acer product: Aspire 6930G v: N/A serial: <filter> 
           Mobo: Acer model: Makalu serial: <filter> BIOS: Acer v: 0.3204 date: 09/25/2008 
Battery:   ID-1: BAT1 charge: 29.3 Wh condition: 31.3/48.8 Wh (64%) model: SANYO AS07B31 status: Discharging 
CPU:       Topology: Dual Core model: Intel Core2 Duo T6400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 bogomips: 7980 
           Speed: 1432 MHz min/max: 1200/2000 MHz Core speeds (MHz): 1: 1432 2: 1244 
Graphics:  Device-1: NVIDIA G96M [GeForce 9600M GT] vendor: Acer Incorporated ALI G96CM driver: nouveau v: kernel 
           bus ID: 01:00.0 
           Display: server: X.Org 1.20.3 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz 
           Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:     Device-1: Intel 82801I HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.19.0-2-amd64 
Network:   Device-1: Intel WiFi Link 5100 driver: iwlwifi v: kernel port: 2000 bus ID: 07:00.0 
           IF: wlp7s0 state: up mac: <filter> 
           Device-2: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet vendor: Acer Incorporated ALI 
           driver: ATL1E v: N/A port: 5000 bus ID: 09:00.0 
           IF: enp9s0 state: down mac: <filter> 
Drives:    Local Storage: total: 149.05 GiB used: 115.34 GiB (77.4%) 
           ID-1: /dev/sda vendor: Hitachi model: HTS723216L9A360 size: 149.05 GiB 
Partition: ID-1: / size: 11.47 GiB used: 2.26 GiB (19.7%) fs: ext4 dev: /dev/sda1 
           ID-2: /home size: 134.09 GiB used: 113.07 GiB (84.3%) fs: ext4 dev: /dev/sda6 
           ID-3: swap-1 size: 1000.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:   Missing: Required tool sensors not installed. Check --recommends 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/10_q4os.list 
           1: deb http://q4os.org/q4repo q4os-3-0-cn main
           Active apt repos in: /etc/apt/sources.list.d/12_qtde.list 
           1: deb http://q4os.org/qtderepo buster main
           Active apt repos in: /etc/apt/sources.list.d/20_debian.list 
           1: deb http://ftp.debian.org/debian/ buster main contrib non-free
           2: deb http://security.debian.org/debian-security/ buster/updates main contrib non-free
           3: deb http://ftp.debian.org/debian/ buster-updates main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/30_debian_backports.list 
Info:      Processes: 137 Uptime: 4m Memory: 3.85 GiB used: 288.2 MiB (7.3%) Init: systemd runlevel: 15 Compilers: gcc: N/A 
           Shell: bash v: 5.0.2 inxi: 3.0.32

bin · 2019-04-01 06:40

Following on from the above, next day it had the same start up problem.

Looking at it, it seems that fsck is either not always recognising the drive or that there is an issue getting the ID from fstab and returning that as an sd value.

Recovery mode and restart and it works.

Anyway, r5 had come along, fresh install and no further issues - r5 seems very well behaved.

Q4OS Forum

#1 2019-03-28 18:06

Interesting boot failure when starting Centaurus 3.5 r4 TDE

#2 2019-04-01 06:40

Re: Interesting boot failure when starting Centaurus 3.5 r4 TDE

Board footer