Page: Previous  1, 2, 3, 4  Next

techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3458
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Feb 10, 12, 11:00    
This issue rings a bell very faintly, but I do not remember how to fix it, or what causes it.

The uuid match, unless I read them too fast.

The disk is a sata, not ssd, so that's not the issue.

:: Code ::
UUID=9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9 /               ext4    errors=remount-ro 0       1


errors=remount-ro is not how my / root is in my fstab

/ ext3 defaults 0 2

was your fstab auto generated or did you change it? I don't believe this would be the issue.

Is there something else on this system that is non standard? is this the only operating system installed?
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 521
Back to top
Posted: Feb 10, 12, 15:06    
Interesting... can you try the liquorix kernel again and then list the contents of /dev from Busybox? It's possible that your netbook requires a special module to be loaded into initramfs to get access to your drives.
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 204
Location: South Florida
Back to top
Posted: Feb 10, 12, 17:38    
@ techadmin
This is a business card install of wheezy + smxi, nothing else.
fstab auto-generated, no Windoze pollution.
The only thing that could remotely be non-standard is the swap partition in the beginning.
Again, the Debian kernel works fine on that netbook.

@damentz
I don't understand what you need me to do.
I can try the liquorix kernel again but have no idea how to "list the contents of /dev from Busybox".
All that computer will do is written down already, it won't go past
(initramfs)
After that, I have to press Crtl+Alt+Del to restart and boot into the other kernel.
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3458
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Feb 10, 12, 20:29    
:: Code ::
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)


damentz is on the right track here i think.

When you see this point, simply type: ls /dev

if you see a /dev/disk, then also do
ls /dev/disk

and if you then see a: /dev/disk/by-uuid
do: ls /dev/disk/by-uuid

this will show what the initramfs actually thinks is going on vs what is actually going on, I think anyway.

busybox is a stripped down minimal shell that lets you do basic things when everything else has failed.

I have never tried seeing what's in /dev at that stage of things, so can't say more.

Actually, I just tried, didn't know you can run busybox commands in shell, like so:

busybox ls /dev

but when you are actually in busybox, like on a failied boot, you don't need the extra busybox command, just the ls command.

see: busybox --help

in your console now to see the options, basically it's just a basic shell with basic simple commands.
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 204
Location: South Florida
Back to top
Posted: Feb 11, 12, 6:51    
I didn't know that you could run busybox commands in shell either.
:: Code ::
(initramfs) ls /dev
console                           tty1         tty33         tty57
core                                tty10       tty34         tty58
cpu_dma_latency            tty11       tty35         tty59
fd                                     tty12       tty36         tty6
full                                  tty13       tty37         tty60
fuse                                tty14       tty38         tty61
hpet                               tty15        tty39        tty62
input                              tty16        tty4          tty63
kmsg                              tty17        tty40         tty7
mapper                          tty18        tty41         tty8
mcelog                           tty19        tty42         tty9
mem                              tty2         tty43         ttyS0
networrk_latency          tty20       tty44         ttyS1
network_thorughput     tty21        tty45        ttyS2
null                                tty22        tty46        ttyS3
port                               tty23       tty47         urandom
psaux                            tty24       tty48         vcs
ptmx                              tty25       tty49          vcs1
pts                                 tty26       tty5            vcsa
random                          tty27       tty50          vcsa1
snapshot                       tty28       tty51          vga_arbiter
stderr                            tty29       tty52          zero
stdin                             tty3         tty53
stdout                           tty30        tty54
(initramfs)
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 204
Location: South Florida
Back to top
Posted: Feb 11, 12, 7:00    
This busy box output is organized in 4 columns, unable to reproduce in this forum's format, where you see a space there is a tab in the column.
BTW, today I installed latest Debian kernel in this netbook, works fine.
3.2.0.1-686-pae
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3458
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Feb 11, 12, 10:19    
well, that answers that, no sda found at all with the liquorix kernel.

I can't remember if there's a way to make the system enter this busybox manually during boot to confirm / deny what the booting kernel sees.

But in this case, the kernel is certainly not seeing anything in terms of disks.

The problem is I don't know if this is normal at that boot stage in initramfs or not.

But given the system is stating it cannot see a drive partition, and that the drive partition data is consistent, this is a certainly something real.

Just to confirm, at what point is the above output appearing, at boot failure with liquorix? or running: busybox ls /dev in console after booting in the debian kernel?

Ou
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 521
Back to top
Posted: Feb 11, 12, 13:27    
ckosloff, can you try the 3.2-5.dmz.1 liquorix kernel? I made some sata modules static that might help with your netbook.
anticapitalista
Status: Contributor
Joined: 13 Jun 2008
Posts: 193
Location: Greece
Back to top
Posted: Feb 11, 12, 14:03    
This might help, or be totally irrelevent.

IIRC I got this and update-initramfs -k all -u -t got me back to booting ok.

I also remember there being a hidden .udev file in /dev/ that existed when I couldn't boot the liquorix kernel, but it 'disappeared' after doing the update-initramfs above (or I deleted it, can't remember exactly).
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 204
Location: South Florida
Back to top
Posted: Feb 12, 12, 5:45    
:: techAdmin wrote ::

Just to confirm, at what point is the above output appearing, at boot failure with liquorix? or running: busybox ls /dev in console after booting in the debian kernel?

None of those, sorry.
I typed ls /dev in the busybox of the liquorix kernel, after it failed.
Display posts from previous:   
Page: Previous  1, 2, 3, 4  Next
All times are GMT - 8 Hours