Debian Installation :: 2.6.32-5-amd64 Boot Fails - How To Make It Boot
May 27, 2011
My old computer started randomly rebooting so I went out yesterday and bought a new one. It's a standard Intel 64 architecture with 2gb ram etc.The old computer was running Lenny however I'm happy to upgrade, so I just went to the main Debian download site and downloaded:debian-6.0.1a-ia64.netinst.iso (this didn't work, apparently ia64 is for itanium and my machine is definitely not that), so I downloaded: debian-6.0.1a-amd64-netinst.iso, burnt the CD and ran the install. First time through I had a power failure.
Second time through (a complete fresh start - new partition and everything) it went all the way through to completion and reboot.Clicked 'Continue' to reboot and the machine reset as it would normally and the Grub loader started okay, prompted for the "Debian amd64" standard boot image, selected that and the first 6 lines appeared normal, then the messages wizzed by so fast that only superman could read them. Then they stop - here is some of the content...
[3.816673] Kernel panic - not syncing: Attempted to killl init!
Call trace:
get_empty_filp
panic
[code].....
Running it again I get similar stack stuff but it's a different place: [3.541816], [3.427502] And sometimes if I wait for a minute or two it will continue on further but appear to crash again. Hardware details (everything is onboard - no added cards):
Having trouble installing 'Squeeze' 6.0.1a-amd64-netinst on a new AMD64 system.The installer boots and runs fine until it gets to hard disk detection. Then it hangs for about 20 minutes showing a blue screen, during which time the HDD-activity light flickers every 5 seconds. Eventually it says it can't detect a hard disk, and displays a (longish) list of possible drivers; no idea which, if any, would suit.Anyone else installed (successfully or otherwise) on this combo?
I have not been using my lenny 2.6.26-2-amd64 for about a month or more.I booted it today, and there were over 30 updates available, inculding some kernel header updates I installed all these updates and rebooted.Well, there are 2 new entries to grub menu:Linux 2.6.32-bpo-3-amd64Linux 2.6.32-bpo-2-amd64 (single user or recovery)in addition to my old kernels.So, I chose the bpo-3 entry, but it just sits there.I have to chose the kernel before the update. Is there something wrong with the update? dit: I just found out that synaptic manager does not show 2.6.32-bpo-3-amd64 at all as being installed.In fact, it is not in the header list nor the image list.
System was working reliably. Moved components into a new case. Now system will not boot. Either gives error that the disk is not bootable or displays the motherboard configuration screen.
I am able to boot Debian with a USB drive and have attempted fixes in "rescue mode".
I confirmed that the system is booting to EFI mode.
I have tried re-installing the grub-efi package and re-creating the Grub config file with update-grub.
When re-installing Grub I receive "Discarding improperly nested partition ..." warnings but the installation succeeds. I have searched this warning message and the forums seem to say that it can be ignored.
I have tried re-setting the motherboard NVRAM using the jumper block.
The computer shows "debian" as a boot choice in addition to the usual raw drive model listing. However, neither of the choices will boot successfully.
Recently upgraded to 8GB RAM. BIOS shows 8GB, lshw shows 8GB (2 x4GB), Applications > System Tools > System Monitor > System shows 3.7GB. After 2 days of forum hunting I cannot find a way to check whether the machine is using all 8GB and, if not, how to make it do so. I have found a few postings about using the "bigmem" build but these seem to be for the 32-bit builds as well as a few postings saying that the amd64 build uses bigmem/highmem by default. I can't find any reference to CONFIG_HIGHMEM in /boot/config-2.6.32-5-amd64 and I don't have a menu.lst in /boot/grub to change to a "bigmem" type build.
I have a dual boot computer. I seem to be having a bit of a problem with Grub lately. Every time I do any kind of update in Debian Lenny AMD 64 it borks my Grub. The first time I had to change a few lines in menu.lst (hd1,1 to hd0,1), no problem. The second time, things went downhill fast and G-Parted was giving me errors on my NTFS partitions. I had to do an XP repair, fixboot, and I had to reinstall Grub completely to the MBR.
Now, I having a "Grub Loading stage1.5. Grub loading, please wait.... Error 22". All I did was update Debian Linux and shut down. From my initial searches this is an error relating to not finding the correct partition. I have booted with a G-Part CD and it shows all my partitions. I do have a Windows XP Home boot cd if I need it. Here is my partition outline if you need it:
/dev/sda1 NTFS (Windows) flags--boot /dev/sda2 Ext3 (Linux) /dev/sda3 FAT32 (shared space between Windows and Linux) /dev/sda4 extended /dev/sda5 linux-swap
I've installed squeeze and wheezy on an old Toshiba Satellite 210 CS laptop with 48MB RAM and a 20GB IDE harddrive.Grub2 won't boot at all and stops with a "error: cannot allocate real mode pages". The solution to that is to use the grub-legacy package.The boot then fails with "waiting for root device" and drops to an initramfs shell.
I have a Redhat Enterprise Linux system and I want to re-make it as Debian. I downloaded the Debian netinst iso but can't seem to make a bootable CD out of it, and I haven't found any adequate explanations anywhere.
I tried burning the iso directly to a disk. i set up the boot order in my BIOS but when I restart the machine it spins the CD drive a few times and then moves on to the hard drive.
I tried expanding the iso into a directory, and then copying all those files into into the "Blank CD-R Disc" on my Gnome Desktop, burnt the CD, and still no boot.
I found some instructions using X3b, but X3b was giving me errors.
I've spent a frustrating afternoon trying to install Xubuntu 10.04 x64. I had already installed Win7 Pro 64, and have been attempting to install on a separate hard drive. It wouldn't even boot into Xubuntu install. Figured a bad burn on the Cd so I reburned the image I had down loaded using Ktorrent. It wouldn't boot either. I swapped out the DVD burner. Still no go. Redownloaded using Ktorrent including the torrent. Wouldn't boot into the installer.
I did a fresh burn. Still it wouldn't boot to the installer. I then downloaded Xubuntu again but from a mirror and not using Ktorrent. Good MD5SUM. Burned it again on another computer. Still wouldn't boot into the installer. I burned a copy of Kubuntu 10.04 x64 and it installed with no difficulty. I've installed Xubuntu 10.04 x86 several times on other computers win no difficulty. But I have 8 Gb of RAM on this machine and want to use Xubuntu 64.
This morning I switched my machine and the Update Manager prompted me to upgrade.So, as usual I did it. After upgrade it asked me to restart. Since then id didn't boot anymore. Now I have blank screen with a blinking cursor ... immediately after the BIOS screen, so it looks that no OS is loaded.
I'm trying to install F11 on a machine that was running well under F10 just a few hours ago. I made some changes to the disk configuration, involving the addition of a dmraid-controllable fakeRAID card (SiL 3124 I think) and creating a RAID 0 array out of the two drives connected to the motherboard itself (Intel ICH7R). Otherwise the machine's configuration is identical to the way it was when running F10. My problem is thus: when I boot from the installation DVD (64-bit), the boot process doesn't make it even to anaconda. Here is the error I get, right after md devices are autoconfigured:
I have a Dell PowerEdge SC1425 with two SCSI-disks, that I have tried installing Debian Squeeze on. This machine has previously been running Lenny (with grub 1), and the upgrade was done by booting a live-cd, mounting the root partition and moving everything in / to /oldroot/, then booting the netinstall (from USB), selecting expert install and setting up everything (not formatting the partition).
Both disks have identical partition tables: /dev/sda1 7 56196 de Dell Utility /dev/sda2 8 250 1951897+ fd Linux raid autodetect /dev/sda3 * 251 9726 76115970 fd Linux raid autodetect /dev/sda1 and /dev/sdb1 contain a Dell Utility, that I have left in place. /dev/sda2 and /dev/sdb2 are members of a Raid-1 for swap. /dev/sda3 and /dev/sdb3 are members of a Raid-1 for / formatted with reiserfs.
After installation, grub loads, but fails with the following message: GRUB loading. Welcome to GRUB! error: no such disk. Entering rescue mode... grub rescue>
I can do the following to get grub to boot: set root=(hd0,3) set prefix=(hd0,3)/boot/grub insmod normal normal This will bring me to the grub menu, and the system boots.
It appears that grub has only found md0, which I believe is the swap partition, because ls (md0)/ returns error: unknown filesystem. I have installed grub to both sda, sdb and md1, and tried dpkg-reconfigure grub-pc and dpkg-reconfigure mdadm, as well as update-grub.
I manually added (md1) /dev/md1 to /boot/grub/device.map, but still no result.
I have run the boot_info_script.sh, but unfortunately I cannot attach the RESULTS.txt, because the forum aparently does not allow the txt-extension. Instead I have placed it here: [URL]. I am tempted to go back to grub-legacy, but it seems I am quite close to getting the system working with grub2.
I installed the alternate disc on my ibook G4, it finished the install ejectedtrf the didc then restarted , The writing came up I to boot to C for cd rom so ihit retirn as per nut then it just stayed at an empty black screen
I want to set the login to the old default of having to enter a username,password. I've tried to use the configuration editor to achieve this and have ticked the "disable-user-list" option under /apps/gdm/simple-greeter but it makes no difference, the greeter still starts with a user list. It appears that the default valuef TRUE for this function is overriding my choice, but I'm notre why. My next step appears to be to edit /etc/gdm3/greeter.gconf-defaults to change the default value. I haven't actually tried that yet so not sure if it would work but, even if it does, it doesn't seem a very elegant way of setting this up. Is there some simple way of changing the behaviour back to asking for username first?
I seem to remember the whole login process as being more configurable than it is now, with options to choose backgrounds, allow root accest finystem->administration->login_screen only gives a choice between selecting a user or automatic login of a particular user, with no further options available.On a general note, would the old method not be a more secure default than presenting an unauthorised user with a list of login id's to be tried?
The following is a subset of error messages I'm getting when trying to do "apt-get upgrade" or "apt-get dist-upgrade" on a machine running ubuntu server 9.10 amd64:
Code: Preparing to replace linux-image-2.6.31-22-server 2.6.31-22.60 (using .../linux-image-2.6.31-22-server_2.6.31-22.65_amd64.deb) ...
I am having a strange issue with my xserver. I do have nvidia graphics. My system is Debian Squeeze with limited packages from Sid to fix issues when needed. Currently I don't think that there are any installed from Sid that have not since been updated through testing. It also contains one package from Lenny that does not exist in Testing for some reason, ogle the dvd player.
After an update the other week my gui failed to come up. That is not that unusual with nvidida. So I reinstalled the driver and all seemed to be fine until the next reboot some days later which failed. I reinstalled the driver again and all seemed fine.
The machine did not come out of hibernate cleanly some days later and upon reboot no gui
I have tried the whole group of driver packages out of sid, testing, stable. All are afflicted with the same problem. When the box drops back to the login if I login and issue from root '/etc/init.d/kdm stop' then '/etc/init.d/kdm start' the gui comes up just fine. It also seams to launch much faster than it has for some time.
A friend has questioned if kdm is starting to early in the launch process. I think he may be on to something. But looking at the files in /etc/rc*.d does not seem to indicate to me that is the case. kdm has the launch number 5.
The machine has been converted to the, what is it, multi-process launch thingy, quite some time ago now, like a year maybe? These are what is in the sequence from kdm on
Code:
The install is amd-64 using the standard debian kernel.
I'm running Debian Wheezy x-86 32 bit Kernel 2.6.38-2-686 and I have encountered a problem I'm hoping to get some help with. All help would be greatly appreciated as researching this issue has not led to any concrete information. After a reboot or similar, the process will go through the boot sequence including giving me the option of what kernel to run either 2.6.32 or 2.6.38 and starting module's as well as performing POST and then when the logon screen should appear I'm presented with a flashing cursor. I can boot into saftey mode and the CLI, but not being very efficent with Bash and the CLI I'm not sure where to go or what to do.
I am building a 10.04.1LTS server. I am putting the /root filesystem into a Software RAID1 partition. I want to keeo my /boot partition outside of RAID.Is there a way to have a boot partition on both sda and sdb so if one drive fails the second boot partition will work away - or should this be kept in with RAID also.
I was upgrading our lab's dhcp server to Lucid and it totally died. I have it running on a Debian recovery cd right now. I ran into a bug in gtk which I seem to have fixed, but now I have more serious errors. If I boot without a CD, I get dumped into a busybox shell after the machine fails to boot. From the live CD, I tried dist-upgrading again and it dies trying to build and install rsyslog with a broken pipe error. I am at a loss as to what to do from here short of reinstalling (which is the last option as this server has a lot of custom configs on it)
I'm trying to make dual boot system with Lenny (64bit) along with WinXP. I'm using one HDD with 2 partitions and installed first XP then Lenny. Everything seems fine till the first boot after fresh install. Lenny starts to boot and after same point the screen goes blank and then is turned off and that's it...nothing happens. Happens so fast that I'm unable to see the exact messages on the screen. Maybe somewhere around staring anarcon?
PC is: Athlon64 X2 5400+ Asus M2V-MX motherboard 3GB DDR2 800 500GB WD SATA2 HDD Radeon x800 GTO video
I reinstalled 2 times and it's the same. WinXP is working fine though but I really don't want it to be my OS... Another "hint" from today: The same happens when I use "Try without installing" of Ubuntu 10.04(i386) Live CD. It starts loading and at some point turns off the monitor. Tried also with 8.04(64bit): Boots till it reach something like "Settings sensor limits" and then it's stuck. I have consoles though (Ctrl+Alt+F1/2/3...).
I have a ~ 2008 notebook (Compaq CQ60-137EL) on which I had Windows 7 only (it was sold with Windows Vista installed).
Later I installed Debian Jessie 8.2.0 Stable ("Graphical expert install" from DVD), along with GRUB as a boot manager (I chose not to install it on the EFI removable media path).
Since then, if I select Windows 7 on the GRUB boot screen, I see "Starting Windows...", and after few seconds the screen flashes for a moment, and then the PC reboots: I see the bios screen, followed by the GRUB screen again. What's even more weird about this is the fact it just happens only in like ~50% of the cases. In the other 50%, Win7 starts flawlessy.
I even tried to install Debian first, then Windows 7, then re-install GRUB, but I got the same issue, even with both system freshly installed.
On 6 attempts, 3 times it worked and 3 times it didn't.
On my desktop PC I'm in the same setting, but I don't have this issue. I think it may be related with the fact I have Win7 on a SSD and I installed Debian on a separate HDD, while on my notebook, as you can imagine, there's just one single HDD.
I was planning on installing Stretch on my iBook G4. So I got my netinst cd and went through the install process. Everything was fine till I got to the section where I selected my mirrors. I chose the US/ftp.debian.org mirror and it failed so I tried the ftp.kernel.org and that failed as well. Then I tried the third on the list and I was able to connect and get my packages. The install completed, however when I rebooted the bootup froze. So I thought that it could my cd so I went and grabbed the latest stretch iso from the site.
Yet again I ran into issues. The biggest was that I kept getting sent back to install menu to manually select what steps I wanted to do. I found this odd since normally the install will just walk you through. Then I ran into the same issues with mirrors. finally the install completed and I was rebooted. However the boot failed again, but this I got dropped into the initramfs shell. Should I file this as bug with the debain-installer package?
I've just installed debian to a thumb drive on a system with no hard drives. I did not install any hard drive to avoid confusion. The installation went well, I rebooted the system several times with no issues until I decided to install the hard drive (SATA drive). After I installed the hard drive the system failed to boot showing something like:
Code: Decompressing Linux... Parsing ELF... done. Booting the kernel. Loading, please wait... mount: mounting /dev/sda1 on /root failed: No such device (continues for other partitions and mount points) Target filesystem doesn't have /sbin/init No init found. Try passing init=bootarg
BusyBox v1.10.2 (Debian 1:1.10.2-2) built-in shell (ash) /bin/sh: can't access tty; job control turned off (initramfs) [9.670347] sd 0:0:0:0: [sdb] Assuming drive cache: write through [9.673805] sd 0:0:0:0: [sdb] Assuming drive cache: write through (some insignificant text was not copied :P)
I am guessing that the new disk is somehow confusing debian regarding where to look for system files or the address where the devices are located because if I remove the data cable from the hard drive the system reboots correctly (no hard drive though). Hotpluging the drive works but once I reboot it happens again.
I have just recently installed firestarter to get an idea of iptables editing with a GUI. Firestarter works great and I love it, however when I turn my system on, and my system is booting up the terminal displays a "Failed" message when attempting to start up firestarter. Now I have been doing my homework (reserch) and have read that a user will get this error because firestarter trys to load prior to the network manager starting up. I have also read some other variables that can cause this is if you use network manager and have a password on your user account (which I do have) can cause this issue.
However in most cases from what I have read is even though it gives the user a "Failed" startup message, once the user logs in, and is connected to the internet firestarter will actually load the iptables. I did some tests and from what I understand I can see that this is true because I have allowed access to certain torrent trackers, and denied access to others, and I can see some come online. Does firestarter load iptables once the user logs in? Or once it fails to load, does it not load at all unless you manually open/load the application. If firestarter just modifies iptables, then once I save my listings in firestarter then I really don't need it to start up correct?
Because I am using one of the new WD disks I am trying to aling my root partition with the real sectors, as described here: [url]
So I copied all files to a temp location, deleted my partition (/dev/sda3), recreated it a few cylinders later (same name) and copied the files to the newly created partition. I updated UUIDs in grub's configuration as suggested in this thread:[url]
But now it fails to boot with the following error:
Code:
I checked the filesystem on this partition and its fine. I tried to recreate the initramfs from Knoppix:
Code:
But it didn't change anything.
How can I either fix it or install a different kernel on this drive so I could boot into it and re-install my default kernels?
I recently purchased a new Lenovo Thinkpad T420i and am having problems installing the latest version of Squeeze from CD. After receiving the laptop, I started it up, configured Windows 7, and confirmed everything is working correctly. Next I went through the Debian installer, which completed successfully. I'll be dual-booting Windows 7 and Debian, so at the partitioning stage I resized my NTFS partition, added a shared VFAT partition, then used the "Guided" install to create my root and swap partitions. My partition layout is code...
I assumed something was wrong with grub, so I booted the CD into rescue mode and chose to reinstall grub onto the Master Boot Record. But nothing changed. Just to experiment, I went into fdisk, deleted all my new partitions (leaving just the Windows ones), and tried rebooting, but the same error happened. I then went through the Debian installer again, being careful to set everything up correctly, but still, the device won't boot.
I'm not even getting to the grub boot screen, so something is wrong even before the point. Reinstalling grub to the Master Boot Record (grub-install /dev/sda) isn't changing anything. How can I troubleshoot this?
