LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 08-27-2012, 02:31 PM   #1
contentics
LQ Newbie
 
Registered: Aug 2012
Posts: 6

Rep: Reputation: Disabled
Debian squeeze won't start after reboot


After my Dell R210-II server with Debian Squeeze had been running for 4 months without any problems, today I suddenly could not get a shell prompt after a successful login using SSH. Also using the virtual console from iDRAC6 I could not see any prompt.

But all other services like httpd, mysqld and so on were still running OK.

Because I have knowledge to administer the server, but do not have qualifications to debug such a problem any other way, I decided to reboot the server. Also because I did not change any configuration options on the server since weeks

But now the server (single OS install) won’t start anymore… Here is an explanation what happens:

System starts

On PXE menu I select (local) and press enter

Then there is a message:
-----------------------------------------
Booting from local disk...
GRUB loading.
Welcome to GRUB!
-----------------------------------------

After that I can select which OS I want to load and I select
-----------------------------------------
Debian GNU/Linux, with Linux 2.6.32-5-amd64
-----------------------------------------

But then the system reports the following:

-----------------------------------------
[0.527313] pci 0000:02:03.0: BAR 6: address space collision of device [0xffff0000-0xffffffff]
[0.707719] i8042.c: No controller found.
Loading, please wait...
/init: /scripts/init-top/ORDER: line 1: /scripts/init-top/all_generic_ide: Permission denied
/init: /scripts/init-top/ORDER: line 3: /scripts/init-top/blacklist: Permission denied
/init: /scripts/init-top/ORDER: line 5: /scripts/init-top/keymap: Permission denied
/init: /scripts/init-top/ORDER: line 7: /scripts/init-top/udev: Permission denied
/init: /scripts/local-top/ORDER: line 1: /scripts/local-top/mdadm: Permission denied
error sending message: Connection refused
udevadm[79]: error sending message: Connection refused

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/800d8e8b-daae-4b9e-811f-9057565aa7f3 does not excist.
Dropping to shell!

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

It seems like the same problem was as discussed at http://forums.debian.net/viewtopic.php?f=17&t=73085 but I cannot boot any linux. So working from command prompt (shell) is not an option without physically going to the datacenter

Is there anybody who can help?

Thanx in advance,
Alvin

Last edited by contentics; 08-29-2012 at 06:22 AM. Reason: Problem solved
 
Old 08-28-2012, 05:27 AM   #2
Dutch Master
Senior Member
 
Registered: Dec 2005
Posts: 1,686

Rep: Reputation: 124Reputation: 124
For some reason you seem to have access to the system during boot, so there's some connectivity... In the Grub menu, press 'e' to get a rudimentary shell so you can change the boot options of the chosen grub-entry. Your first task is to comment out the UUID line of the root fs (the line that states "root=") by putting a # in front of it. Then create a new line under it (go the the line below it, press enter then move the cursor up one line) and enter
Code:
root=/dev/sda1
Assuming /sda1 is the root partition, that is. If not, change sda1 to the appropriate partition. Check to see you did it right (syntax!) then press b to boot. You may need to do this more then once if you get it wrong... Make notes of what you've changed so you can revert it back if it fails. Once the system boots, run the "update-grub" command. Mind that your problems might come from failing hardware, so they could be more persistent then you'd like...
 
Old 08-28-2012, 09:01 AM   #3
contentics
LQ Newbie
 
Registered: Aug 2012
Posts: 6

Original Poster
Rep: Reputation: Disabled
Thanx for your reply Dutch Master... The initial config looks like:

Code:
insmod raid
insmod mdraid
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(md/0)'
search --no-floppy --fs-uuid --set 800d8e8b-daae-4b9e-811f-9057565aa7f3
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=800d8e8b-daae-4b9e-811f-9057565aa7f3 ro quit
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
I have tried a lot of things, like

Code:
insmod raid
insmod mdraid
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(hd/0)' #where here I have tried sda, sda/0, sda/1, sda/2, hda, hda/0, hda/1, hda/2 etc.
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
and


Code:
insmod raid
insmod mdraid
insmod part_msdos
insmod part_msdos
insmod ext2
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=/dev/hda1 #where here I have tried sda, sda0, sda1, sda2, hda, hda0, hda1, hda2 etc.
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
but also


Code:
root=/dev/hda1 #where here I have tried sda, sda0, sda1, sda2, hda, hda0, hda1, hda2 etc.
linux /boot/vmlinuz-2.6.32-5-amd64
initrd /boot/initrd.img-2.6.32-5-amd64
But none with any success
With last one I kept getting error that the drive was not found and after pressing a key I got back into config...

Last edited by contentics; 08-28-2012 at 09:05 AM.
 
Old 08-28-2012, 09:23 AM   #4
contentics
LQ Newbie
 
Registered: Aug 2012
Posts: 6

Original Poster
Rep: Reputation: Disabled
I am just playing a bit, and now I have tried:

Code:
insmod raid
insmod mdraid
insmod part_msdos
insmod ext2
root (hd0,1)
linux (hd0,1)/boot/vmlinuz-2.6.32-5-amd64
initrd /boot/initrd.img-2.6.32-5-amd64
and now I get a message:

Quote:
(hd0,1): Filesystem is unknown.
error: not a pxe disk.
error: not a pxe disk.
error: you need to load the kernel first

Press any key to continue...
But changing the (hd0,1) to all kinds of possible entries, like sd0,1, sda,1, sda0,1 and so on, sometimes it returns "no such disk" and all other times "Filesystem is unknown"

Last edited by contentics; 08-28-2012 at 09:34 AM.
 
Old 08-28-2012, 02:01 PM   #5
Dutch Master
Senior Member
 
Registered: Dec 2005
Posts: 1,686

Rep: Reputation: 124Reputation: 124
Your root filesystem resides on a RAID, named md0, and it seems it won't load the drivers for it. You need to comment out this line:
Code:
linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=800d8e8b-daae-4b9e-811f-9057565aa7f3 ro quit
and replace it with
Code:
linux /boot/vmlinuz-2.6.32-5-amd64 root=/dev/md0 ro quit
on a new line. Hopefully it works...
 
Old 08-28-2012, 02:09 PM   #6
contentics
LQ Newbie
 
Registered: Aug 2012
Posts: 6

Original Poster
Rep: Reputation: Disabled
Unfortunately the same error as before editing the GRUB config.

Quote:
[0.527313] pci 0000:02:03.0: BAR 6: address space collision of device [0xffff0000-0xffffffff]
[0.707719] i8042.c: No controller found.
Loading, please wait...
/init: /scripts/init-top/ORDER: line 1: /scripts/init-top/all_generic_ide: Permission denied
/init: /scripts/init-top/ORDER: line 3: /scripts/init-top/blacklist: Permission denied
/init: /scripts/init-top/ORDER: line 5: /scripts/init-top/keymap: Permission denied
/init: /scripts/init-top/ORDER: line 7: /scripts/init-top/udev: Permission denied
/init: /scripts/local-top/ORDER: line 1: /scripts/local-top/mdadm: Permission denied
error sending message: Connection refused
udevadm[79]: error sending message: Connection refused

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/800d8e8b-daae-4b9e-811f-9057565aa7f3 does not excist.
Dropping to shell!

BusyBox v1.71.1 (Debian 1:1.17.1-8 built-in shell (ash)
Enter 'help' for a list of built in commands.
/bin/sh: can't access tty; job control is turned off (initramfs)
 
Old 08-28-2012, 07:42 PM   #7
Dutch Master
Senior Member
 
Registered: Dec 2005
Posts: 1,686

Rep: Reputation: 124Reputation: 124
Did you comment out the line starting with "search"? It tells Grub to look for that disk, but as it can't find it it won't proceed further. Try this, if it fails I'm afraid you need to plan a road trip to the data-centre soon...
Code:
insmod raid
insmod mdraid
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(md/0)'
# search --no-floppy --fs-uuid --set 800d8e8b-daae-4b9e-811f-9057565aa7f3
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=/dev/md0 ro
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
 
Old 08-28-2012, 08:20 PM   #8
contentics
LQ Newbie
 
Registered: Aug 2012
Posts: 6

Original Poster
Rep: Reputation: Disabled
Again, no success

But what could possibly be the problem? Is it a driver issue maybe? Seeing the first 2 error lines:

Code:
[0.527313] pci 0000:02:03.0: BAR 6: address space collision of device [0xffff0000-0xffffffff]
[0.707719] i8042.c: No controller found.
I came across somewhere where there was mention of some drivers of the Dell R210-II not being correctly installed with Debian Squeeze. Can this be the problem?
Is a kernel update the remedy for this?

Or is the boot sector corrupt?
 
Old 08-28-2012, 08:43 PM   #9
Dutch Master
Senior Member
 
Registered: Dec 2005
Posts: 1,686

Rep: Reputation: 124Reputation: 124
Good catch, I didn't realise there could be a problem with that... According to this page it works: http://kmuto.jp/debian/hcl/DELL/PowerEdge+R210

I found one particularly interesting answer on a question (http://serverfault.com/questions/358...d-dell-servers) quite insightful: how many kernels do you have, are there any newer kernels then the 2.6 version you now use mentioned in the Grub menu? If there are, try the highest numbered one. If there's no other version, you may want to compile a new kernel from scratch. That sounds more difficult then it is, but still shouldn't be performed too light-heartedly though. But it does require a working system... Mind that the Backports repository holds a 3.2 kernel that could be useful, but again: a working system is mandatory...
 
Old 08-29-2012, 06:29 AM   #10
Dutch Master
Senior Member
 
Registered: Dec 2005
Posts: 1,686

Rep: Reputation: 124Reputation: 124
You marked it as solved, what happened?
 
Old 08-29-2012, 06:30 AM   #11
contentics
LQ Newbie
 
Registered: Aug 2012
Posts: 6

Original Poster
Rep: Reputation: Disabled
Thanx for your reply Dutch Master... We have solved the problem by upgrading the kernel to backport version 3.2.0-0. After the reboot we still got the 'address collision' error, but that did not stop the booting process. Via iDRAC we updated the NIC drivers and now the 'address collision' error is also gone.

Still it is uncertain what suddenly caused this mess...

By the way, the GRUB config is now:

Code:
insmod raid
insmod mdraid
insmod part_msdos
insmod ext2
set root='(md/0)'
search --no-floppy --fs-uuid --set 800d8e8b-daae-4b9e-811f-9057565aa7f3
echo    'Loading Linux 3.2.0-0.bpo.2-amd64 ...'
linux   /boot/vmlinuz-3.2.0-0.bpo.2-amd64 root=UUID=800d8e8b-daae-4b9e-811f-9057565aa7f3 ro  quiet
echo    'Loading initial ramdisk ...'
initrd  /boot/initrd.img-3.2.0-0.bpo.2-amd64
So exactly like before, just the version has been upgraded.

Anyway, thanx for your effort trying to help me.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Moved /etc/ Debian squeeze won't boot up now Oapples Linux - Newbie 7 12-21-2011 06:48 PM
Asus eee pc 1101ha, dual boot, debian-squeeze/xp, won't start xp,"reboot and select p mfan Linux - Laptop and Netbook 2 12-04-2010 03:19 PM
Customs keyboard shortcut on Debian Squeeze disabled after reboot... gagou7 Linux - Newbie 0 09-08-2010 12:24 PM
X Server won't start, /dev/fb0 not found, clean install of Debian Squeeze frumpus Linux - Hardware 12 02-26-2010 03:27 PM
X won't start after reboot kodiakmook Linux - General 3 12-21-2001 03:25 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 09:18 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration