Page: Previous  1, 2, 3, 4  Next

damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 521
Back to top
Posted: Feb 9, 12, 15:22    
You don't appear to have liquorix installed. Can you install the newest packages and show us the output of both /etc/fstab and /boot/grub/grub.cfg?

Also, h2 mentions that inxi -plu will show us some useful information.
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 204
Location: South Florida
Back to top
Posted: Feb 9, 12, 18:23    
:: Code ::
root@littledeb:/home/ckosloff# inxi -plu
Partition: ID: / size: 146G used: 3.7G (3%) fs: rootfs dev: /dev/sda2
           label: N/A uuid: 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
           ID: / size: 146G used: 3.7G (3%) fs: ext4 dev: /dev/sda2
           label: N/A uuid: 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
           ID: swap-1 size: 1.50GB used: 0.00GB (0%) fs: swap dev: /dev/sda1
           label: N/A uuid: 6baa93cc-2bd5-4f0e-9ffb-5d104447a148
root@littledeb:/home/ckosloff#
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 204
Location: South Florida
Back to top
Posted: Feb 9, 12, 18:31    
:: damentz wrote ::
You don't appear to have liquorix installed. Can you install the newest packages and show us the output of both /etc/fstab and /boot/grub/grub.cfg?
Also, h2 mentions that inxi -plu will show us some useful information.


Well, I already mentioned that I purged Liquorix via smxi and set Debian as the default kernel.
I re-installed Liquorix as soon as a newer version became available, and that one failed too, the same way.
All that is in previous posts.
I don't understand in what way it would be helpful to repeat those steps, but will be glad to do so if it could help.
Also, how can I show you "the output of both /etc/fstab and /boot/grub/grub.cfg" if the computer will not boot?
Don't get me wrong, I just feel I already did what you need.
If there is something else, please don't hesitate to ask.
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 521
Back to top
Posted: Feb 9, 12, 19:24    
Just because you install a kernel, doesn't mean you need to boot to it. Anyway, I cannot help you without information from the two files I mentioned while the kernel packages are installed.

What I want to see is if there is a discrepancy between the type of device configured in /etc/fstab, and the device being referenced by Liquorix through the kernel parameters in the grub configuration file. When a kernel drops to initramfs, that is almost always a problem with accessing the root filesystem.

Also, I'm surprised there's absolutely nothing else. Usually there's an important message right before dropping into a recovery shell. A linux kernel does not delightfully drop to a recovery shell from initramfs, it's going to make some noise and complain about something.
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3456
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Feb 9, 12, 20:22    
damentz, that's what I'm wondering too, usually the kernel pukes, then tosses you into some zombie zone of busybox or whatever, but this is stopping right at the very start of the boot process, which to me suggests this is not root failing to be detected, but rather something totally different.

We've all seen those grub complaints about file systems not found, this is different, I know the point he's talking about, it's right when the kernel starts to boot, which I believe, correct me if I'm wrong, is AFTER the root file system is loaded and started. In other words, this might be the actual kernel puking at some super early stage we don't usually see.

no, I'll correct myself, I think that's wrong, is this initramfs puking, not the root kernel code itself? I believe so, if I remember my dmesg viewing, I seem to recall it's quite a bit later on that the root fs gets loaded, but I'm not very up on how this stuff works internally. But an early kernel puke would certainly kill the boot with a correct root path, and that's what this looks like sort of to me. Can you get feedback from other atom users?

I'm wondering if something is up with the mobo or hardware, but given the other kernel boots, it would have to ba configuration thing, unless the bare chance that the liquorix calls something very early that the debian does not, that causes the fail. But definitely odd.

There won't be any kernel logs on this error I bleieve, nor any dmesg, because it's too early in the process.

I almost think this might be worth a look re lkml or something, not that I'm volunteering anyone to spend that frustrating time.

Any known cases of atom of that generation working?
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 204
Location: South Florida
Back to top
Posted: Feb 10, 12, 6:22    
Re-installed latest liquorix from smxi, selected it as default, will have to switch back to Debian after this.
I wrote down exactly what was on the screen, here is after the second line (modprobe: module unix not found in modules.dep) and a delay:

----------------------------------------------------
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay = (did the system wait long enough?)
- Check root = (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)

ALERT! /dev/disk/by-uuid/9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9 does not exist.
Dropping to a shell!
modprobe: module i8042 not found in modules.dep
modprobe: module atkbd not found in modules.dep

BusyBox v1.19.3 (Debian 1:1.19.3-5) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)

------------------------------------------------------------------------

< Edited by ckosloff :: Feb 10, 12, 7:13 >
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 204
Location: South Florida
Back to top
Posted: Feb 10, 12, 6:39    
Latest liquorix 3.2.0-4.dmz.1-liquorix-686 is installed, failing as reported.
I booted into the Debian kerrnel.
Here are requested grub.cfg:
:: Code ::

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  insmod vbe
  insmod vga
  insmod video_bochs
  insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  load_video
  insmod gfxterm
  insmod part_msdos
  insmod ext2
  set root='(hd0,msdos2)'
  search --no-floppy --fs-uuid --set=root 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
  set locale_dir=($root)/boot/grub/locale
  set lang=
  insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4.dmz.1-liquorix-686' --class debian --class gnu-linux --class gnu --class os {
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='(hd0,msdos2)'
   search --no-floppy --fs-uuid --set=root 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
   echo   'Loading Linux 3.2.0-4.dmz.1-liquorix-686 ...'
   linux   /boot/vmlinuz-3.2.0-4.dmz.1-liquorix-686 root=UUID=9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9 ro  quiet
   echo   'Loading initial ramdisk ...'
   initrd   /boot/initrd.img-3.2.0-4.dmz.1-liquorix-686
}
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4.dmz.1-liquorix-686 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='(hd0,msdos2)'
   search --no-floppy --fs-uuid --set=root 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
   echo   'Loading Linux 3.2.0-4.dmz.1-liquorix-686 ...'
   linux   /boot/vmlinuz-3.2.0-4.dmz.1-liquorix-686 root=UUID=9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9 ro single
   echo   'Loading initial ramdisk ...'
   initrd   /boot/initrd.img-3.2.0-4.dmz.1-liquorix-686
}
menuentry 'Debian GNU/Linux, with Linux 3.1.0-1-686-pae' --class debian --class gnu-linux --class gnu --class os {
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='(hd0,msdos2)'
   search --no-floppy --fs-uuid --set=root 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
   echo   'Loading Linux 3.1.0-1-686-pae ...'
   linux   /boot/vmlinuz-3.1.0-1-686-pae root=UUID=9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9 ro  quiet
   echo   'Loading initial ramdisk ...'
   initrd   /boot/initrd.img-3.1.0-1-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.1.0-1-686-pae (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='(hd0,msdos2)'
   search --no-floppy --fs-uuid --set=root 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
   echo   'Loading Linux 3.1.0-1-686-pae ...'
   linux   /boot/vmlinuz-3.1.0-1-686-pae root=UUID=9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9 ro single
   echo   'Loading initial ramdisk ...'
   initrd   /boot/initrd.img-3.1.0-1-686-pae
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 204
Location: South Florida
Back to top
Posted: Feb 10, 12, 6:41    
and fstab:
:: Code ::

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda2 during installation
UUID=9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda1 during installation
UUID=6baa93cc-2bd5-4f0e-9ffb-5d104447a148 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3456
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Feb 10, 12, 9:42    
looks like damentz called this one right with your further screen output (note, always provide all literal data for bug reports, otherwise it takes too long and involves too much speculation. Can't find root device.
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 204
Location: South Florida
Back to top
Posted: Feb 10, 12, 10:20    
@techadmin
I had to reproduce it and write it down by hand since there was no way to save it.
I usually do send verbose info.
Display posts from previous:   
Page: Previous  1, 2, 3, 4  Next
All times are GMT - 8 Hours