I have tried many times to load Debian on a new HD without any success. I used bittorrent to download it to my windows vista laptop and preceded to burn the image to a cd using Active@isoburner. But it only gets to where it says boot failure.
AMD 64X2 3800 CPU
1.5 G RAM
ASUS A8N5X MOTHERBOARD
ATI RADEON HD 545O GRAPHICS
HITACHI DESKSTAR SATA 500G HD
I cannot boot after installing Squeeze. /home partition is missing.
Here is the related information.
df -h
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 6.5G 4.5G 1.7G 73% /
tmpfs 1.7G 0 1.7G 0% /lib/init/rw
udev 1.7G 196K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /dev/shm
[Code].......
Lately I'm encountering a somewhat annoying malfunction: almost every boot, my desktop is stuck, HD red led is constatnly on, and i get a message from kerneloops that I had a kernel failure. I can move the cursor a little and slowly or not at all. Few violent reboots and I get a clean boot. Running Debian Lenny kernel 2.6.26-2-686 on a Pentium 4 2.0 GHz with 250 MiB ram.
View 4 Replies View RelatedResently I installed OpenSUSE 11.1 including XEN as I planned to use virtual machines. XEN item appeared in GRUB boot menu along with other items (OpenSUSE, windows...).I was instructed to boot XEN in order to use virtual machines.During boot, XEN was examining my disks and partitions, and when it reached CD and DVD drives, seemingly it went into infinite loop between the two drives. Finaly the screen went dark, and I have to make hard reboot. How can I work around this problem?
View 3 Replies View RelatedI tried to intall DEBIAN on a P6 machine(Power 570 processor)'s LPAR. Using debian-504-powerpc-DVD-1.iso from http://cdimage.debian.org/debian-cd/5.0 ... c/iso-dvd/I used "install64" option and it completed normally. All using default/recommended options during the installation. i.e. whole disk, one filesystem, etc.However, after the installation(seemed succesful), I got the following error during reboot."root=/dev/sda2:2,/vmlinux: Unable to open file, Invalid device"
View 1 Replies View RelatedMy laptop died while installing F12, without completing installation. Now I can not boot the computer from HD, CD, or USB. I have flashed the BIOS with the most recent ROM. I can access the BIOS setup and exhausted all my options there, which is mainly boot order. At the moment, the boot process goes to a blinking cursor and does not allow for input. The laptop in question is a lenovo Y510 that was previously running F10 with a single partition.
View 2 Replies View RelatedI downloaded Fedora 15 Live and Fedora 14 Live to try to see where Linux is for music and broadcast audio on a laptop. It turns out I have to use 14. 14 and 15 both sort of work as live out of the box, although why they ship with the common Broadcom wifi driver missing and the touchpad tap disabled beats me. I also never found the magic button to close down 15. There must be one, but blow me I couldn't find it. Then I tried to follow the instructions at [URL] which mostly seemed to work. I need to keep Win 7 as this is the 32-bit test machine. I used EasyBCD v2.1 rather than the older version the guide is written for.
Booting into Win7 at first worked, then a boot into Linux stopped at a line that said something about a kernel thread helper Then Win 7 blue screened on boot, although it would boot to Safe Mode. Removed Veriface from the Lenovo laptop and it would boot Win 7. Tried setting Drive in EasyBCD to "Boot" rather than "C:" for Fedora. Now booting Fedora gave a Windows missing file message and croaked. Repairing startup with the Win 7 boot CD cured Win 7. Repeated the loop with the same failures. Re-partitioned and re-installed Fedora and just the same - a screen of text that stops. I can now boot to Windows and need help to sort out the Linux boot. How do I start to investigate the screen of text saying things like "__bad_area_nosemaphore" ?
When I install either desktop version of Ubuntu 9.10 or Xubantu 9.10 it boots ok when ask to reboot at the end of the install, but will not reboot after that (2nd attempt and all after fail)On 2nd and later attempts the grub menu comes up and I choose default Ubantu and the Ubuntu circle logo displays for about 30 seconds, and most of time I see it try to access my floppy drive (sometimes the floppy drive light stays on, sometimes it does not) a cursor then blinks in the upper left hand corner for about 10 seconds and then the screen goes blank and freezes there until I power down.
My System
Dell Dimension 2350
Celeron 1.80 G Hz
768 Meg RAM
30 Gig hard drive
Note: Xubantu installs OK to HD on another system I have, but not on this Dell. To test the Dell I did install Puppy Linux with default grub loader to HD ant it works OK (boots OK to HD each time).Side note: At first I tried this Dell to set up dual boot with XP and Ubantu and same symptoms Ubantu only booting OK once and then never again so I thought it was dual boot issue so I deleted all partions (XP is now gone) with latest GParted version and attempted installing Ubuntu 9.10 and then Xubanto 9.10 on the whole harddrive but still no boot past the first time I though this might not be a grub issue since it seems to get past grub and the Ubantu circle shows for about 30 seconds before the system freezes. only a guess on my part as I don't know enough about Grub or Ubuntu to troubleshoot without help. I see I can hit "e" to get to the grub editor and I looked at the grub boot code but don't enough about it to edit for a fix. I thought about Lilo but did not see an option on the normal Xbuntu ,or even when I used the alternate install CD,for a Lilo option. Also note I can run the live CDs for Ubuntu and Xubuntu OK on this Dell. Only HD install gives me problems.
on my pc, that was running WinXP, I thought of installing Ubuntu. (I did install linux already a few times in the past years and use it on another couple of pcs) But something went wrong. This machine has 2 x 200MB maxtor drives, in raid 0 configuration, supported by the motherboard Nvidia chipset, and working well in Windows. When ran the live Ubuntu 10.04 cd, gparted was not able to access the drives in raid configuration, until I installed the mdadm and kpartx packages then the existing data became visible. So after that initial moment I thought all was ok and proceeded to install Lucid on the machine, dual booting with Windows. I did partition manually so that in my 400GB raid drive there is an 80GB NTFS partition with WinXP, a 90GB extended partition for Linux Ext4 and Swap and then a last NTFS 200GB partition for data. All went well, but now on restarting the computer nothing happens, nothing loads, Grub is not showing, and it looks like I cannot launch Linux nor Windows. All the data from WinXP and the Ubuntu installation seems to be on the disks but the pc is just not booting. I suppose the problem is with the raid configuration that is not handled properly during the installation, but is there anything that I can do now, apart from reinstalling Windows Xp or installing Ubuntu in a non raid configuration?
View 9 Replies View RelatedI was finally able to install Fedora 11 x64 after choosing to only install packages from the repository on the install DVD. Prior to that when I had chosen tio install from the default online repositories, the install itself failed with a Python exception ( see my other post ). Now, however, once I boot after the install I eventually receive a kernel panic message, and failure. The exact same thing happened with CentOS 5.3 x64 after a flawless install. So unless someone knows what might be going on I will assume that Fedore, Red hat, and offshoots for x64 bit systems are just not for me. I have been able to successfully install the latest Mandriva and SUSE x64 Linux distros so whatever Red Hat/Fedora has done just does not work on my system.
View 3 Replies View RelatedRecently, I had to switch harddrives on one of my servers due to the need for hardware.
However, when I switched back to the original harddrive I got a surprise : Instead of booting normally in OpenSuse 11.3, it booted in the grub shell.
I did a root ( hd0,1) but when I attempted the setup cmd it failed. Thinking that I probably was a configuration error ( nothing was changed - the drive had spent some time in a nice anti static bag ) I booted using a USB key.
To my surprise I got a message stating that parted couldn't read the other partitions ( boot and swap ) and hence I would not be able to edit then. Fortunately, the data partition seemed OK so I can backup the data.
Preferbly, I would like to be able to restore my original system.
After buying a new PC, I decided to "reorganize" my former PC as follows:Initially it has been a dual (SATA) disk dual boot PC- one disk for each OS, while XP was fully installed on a single NTFS partition. Using Gparted I shrunk the XP partition, and created some Linux partitions. I've verified that the XP partition (sda1) is bootable. Afterwards, I removed the other (former Linux) disk from the computer. While doing so, I had to temporarily disconnect cables from both drives. Finally, I fresh installed Mint 9 (Ubuntu 10.04 derivative), on my pre-prepared Linux partitions. Installation completed flawlessly, and during the install, I've noticed that GRUB2 has been installed on sda. Rebooted and got "Disk boot failure" error.
I've checked the BIOS and noticed that the (single) drive was not recognized.
I manually tested from the BIOS and located the drive as IDE3. Saving the new configuration (F10) and rebooting- the HD gain is not identified (the CMOS battery is fine- keeps time).
Booting a live CD I can see and access all above partitions.
How do I install an additional kernel in Linux Ubuntu 10.10, in case of a boot failure? Also how do I make the Grub Menu Visible, so that I am able to select multiple kernels. There is an older solution below, but is there a way to do this in Linux Ubuntu 10.10. I just suffered an update failure, possibly due to a corrupt kernel upgrade, which made my system unbootable. The cursor just flashed continuously.
Solution of 2007[URL].... "The next obvious rescue aid is to always have a working kernel installed. I usually work from a kernel updated via yum. Kernels have occasionally been released with flaws that have caused one or more of my machines to not boot. To this end, I always make sure I have at least one perfectly running kernel on a machine. A great way to handle this is to first add plugins=1 in your /etc/yum.conf file. The next step is to take this script (written by Jeremy Katz from Red Hat) and save it as n-installonly.py in /usr/lib/yum-plugins. You can change the number of kernels to retain on the system by changing the tookeep variable (default = 2).
With a known working kernel on your system, you can upgrade safely. If the new kernel is hosed, simply boot the old kernel to solve the issue with the new kernel be it to remove it, recompile it, or update it."
I've run the install to hard drive program three times over and each time I get "disk boot failure". I believe I've got Grub to install to the mbr but I am not sure.
System:
Barton 3200+ with 1GB of DDR1
Asus A7V333
High Point hard disk controller
other items
All the hard drives are hooked to the High Point controller. It recognizes all of them that have power hooked up and read/writes to them. Two have 98SE installs, the third is where I'm trying to install Fedora 12 to get away from some problems I'm having with 98SE.
The BIOS is set up to boot from the "SCSI device" which means it's booting from the High Point controller. The High Point lets me set a boot mark, which, when set to the Fedora drive, yields the disk boot failure no matter what I do to it.
I'm having a problem installing Ubuntu Studio 9.10-alternate-amd64 onto my machine. This is the third attempt and I keep running into the same problem. Grub Boot Loader will only install to 16% when a screen pops up:
Ubuntu Installer Main Menu
Choose the next step in the install process:
choose language
configure the keyboard
detect and mount CD-rom
etc...
choosing the option "Install Grub boot loader on a hard disk" sends me back to the Grub install and once again at 16% the Ubuntu Installer Main Menu pops up. Choosing the option "Install the Lilo Boot Loader on a hard disk" resolves in an Lilo-install failure and i'm directed back to the Installer Main Menu. The option "Finish the installation" sends me back to the same menu..I'm stumped as to what to do... a disk check ensured me that the instal-dvd is valid though I can't get past this silly install menu.
Ive been at this for two days now, and cant make any progress.
First, the details:
Target Machine:
IBM (e)server, xSeries 306
OS: Fedora 4
Boot Order:
1. CD...
2. Removable Media
3. SATA...
USB Drive:
adata 8GB
Process:
I used the prescribed live usb creator for windows to fill the usb drive. Ive attempted to boot from the USB at least 4 times, once from each USB port on the box. No luck.There isnt an option in the BIOS to select the specific boot device. I bring that up because my desktop does have that option, and using the BIOS BOOT MENU, I was able to boot from the USB and bring up the Fedora 14 Installation Menu, no problem.
So, it works on the pc thats on my desk (eMachine w/XP), but the IBM doesnt even recognize it.
I've just installed 'Testing' on a VMware server and after I completed the install with no problems, the system booted into the kernel and I noticed the following start up process error:
Code:
startpar: service(s) returned failure: udev...failure!!!
I have not seen this before and am not sure if it's related to the fact that this is a virtual machine and not a physical server or something else. Here is a Screenshot.
I have a box running Lenny and boot with lilo. Today there was a power failure and now the system is stuck on Lilo ..It doesnt get passed that. I tried to boot in single mode but the same thing is happens. How can I fix this problem
View 3 Replies View RelatedI just installed the lenny (amd64) on my new core i7 870 computer (with netinst), but the kernel failure message appeared everytime I booted into gnome. I don't know how to solve this problem. Sorry I don't have much experience with installing linux, though I have been its user for a few years.
View 4 Replies View RelatedI've just installed 'Testing' on a VMware server and after I completed the install with no problems, the system booted into the kernel and I noticed the following start up process error:
startpar: service(s) returned failure: udev...failure!
I have not seen this before and am not sure if it's related to the fact that this is a virtual machine and not a physical server or something else.
Here is a Screenshot.
Toshiba notebook is set up to triple boot win7, mepis 8.5 and os 11.3.Recent update of os11.3 left system with boot failure, "file not found".I booted mepis and used utility to reinstall grub, but no joy.
Appeared to install ok but on reboot, sda5 identified as 'mepis' not os11.3 and would not boot. Win7 & mepis boot ok.
Next, booted live Parted Magic and repaired as per another thread here, but again, no joy.NONE of the systems will boot.Rebooted mepis live cd and reinstalled grub again. Sda5 still identified as mepis and will not boot. Win7 & mepis boot ok.
I'm running a dual-boot with linux mint and Windows. I have an E-machines desktop with : 760 GB Hard Drive 6GB RAM NVidia GeForce Graphics card 6150se Integrated AMD Athalon II X2 235e dual-core processor My problem is getting my grub to boot into Linux Mint, and the problem may lie with my graphics card. Whenever I install the linux mint for the first time, I am prompted to activate my proprietary NVidia graphics driver, which I do. Then I am asked to reboot.
Upon reboot, the system gets to the grub menu, accepts my selection to boot linux mint, then the "progress dots" appear on the screen. After about 8 seconds, the screen switches into command prompt mode. I never get to the graphical sign-on screen. All I get is the console sign-on prompts. From there my only option seems to be to reboot. (sudu reboot). After which, of course, I am forced to go into Windows vs. Linux to avoid the problem. Once Windows has loaded up, I do a restart and go back into Linux Mint . Finally, I get to the Linux sign-on graphical screen.
To summarize, i cannot restart linux mint without getting stuck staring at a console screen. I can get back into linux mint if i use the command 'sudo reboot', and, from the grub menu, choosing to go into Windows. From Windows, I then do a restart and end up back at the grub screen again, but this time when I select linux mint, things work and I am given the sign-on gui.
If I choose to not install the graphics driver (and put up with the annoying reminder to activate one), the system dual boots without a problem.
I have a working RHEL in /dev/sda1 and a newly constructed Ubuntu Lucid in /dev/sda2. I'm going to edit the grub config and reboot the server into the new Ubuntu. However, I'm not 100% sure that the new distro can boot. And since my only way to access the server is via SSH, I need the network to be up too.
How can I configure Grub and Ubuntu so that if the server fails to boot, it will automatically reboot into the old RHEL? Currently using GRUB 0.93, but I can upgrade it if needed.
Update: In the end, no boot failure occured. But without the insurance from this, I wouldn't have attempted [URL]..
I have a system with 2 hard drives. One drive (D) is my Ubuntu 10.04 system and the other drive (C) is my Windows XP system.
When I boot, I get BIOS then GRUB. If I choose the XP selection I am taken to a Boot Loader that now longer works. I get an error saying: "Windows could not start because the following file is missing. <windows root> system32hal.dll Please reinstall a copy of the above file.
Can I remove the boot loader and let Grub take me directly to the C:/windows? If so how?
No wonder my network-career is not getting in the mood... always other trouble.
Thing is: reboot and ended with a black screen: "no video available". i hit the reboot button. same result. I just, today, added a new DVD/Read-Write, so i have assumed thats the problem. Unplugged it: same problem. Nothing, not even the BIOS-display.
As i once started a PC without keyboard connected i did remember that that doesn't work (if i recall correct it gave me some beeps, today nothing like a beep). I replaced the keyboard and could boot.
But i don't trust this result. If someone might give an experienced opinion i would be very glad (i got several pc's, but this one is the only one which is really usuable, though its still a 200€ one, but it does all i need).
I have a dell PE1750 server which would not boot up after a power failure. I am thrown to a shell for maintenance after showing an error in file system check. The server was running - Red Hat Enterprise Linux AS release 3 (Taroon). Please let me know if I can try to recover from this error by booting from the 1st CD of a higher version of linux like RHEL5. I ask this because I do not have the old media with which the system was setup. Can the use of latest OS CD cause any problem?
View 2 Replies View RelatedThis error message appears in the varlog
The situation is I removed the ADSL card from my desktop as I have no use for it for the moment. I am guessing that the motherboard is still trying to detect the Sangoma ADSL card. What is the best way to resolve this problem, uninstall the drivers for the ADSL card or change the settings in the system configuration files?
The system is not affected by this removal, just get prompted regularly about this error as configured in the kerneloops client.
Hardware at issue is an nVidia GeForce 9600 GT. Issue occurs regardless whether the driver is downloaded and installed from nVidia, or installed via Synaptic courtesy of the new dkms package in the repositories.
It should also be noted that the issue only arose after an update today, as follows:
I do not believe it is related to the last three items in that list. Because everything worked perfectly before todays update, it would appear that one of those other updates is causing KDM and nVidia to not want to co-operate with each other.I also notice that, new to the boot sequence, the system is booting with "concurrency" - never seen that scroll by before - which may have something to do with it too.
OK, what happens. KDM "fails" to start when booting the computer. Symptoms : At the appropriate spot in the boot sequence, the screen goes black (as usual), but then, instead of the cycling cursor followed by the logon screen, the nVidia logo appears, and after about 7 or 8 seconds, the screen goes black for about a second, then drops me back at the console. From there, I can log in as root.
Now, the thing is, KDM is actually running, but using <control> <alt> <F7> only brings me to a blank black screen. By issuing the command /etc/init.d/kdm restart, I come up to a normal logon and can proceed as usual. As well, if I delete xorg.conf, system boots OK.
Looking at the system log, we find :
And then some way past that we get :
Should mention that was using the latest stable driver from nVidia (195.36.24), but in the hope that maybe something in the latest beta may solve the issue, installed that, but the answer is nope And yes, completely uninstalled the nVidia drivers between each test of the nVidia driver, the same driver in the repositories and the latest beta driver, before anyone mentions.
I tried to install fedora in my pc. First I insert fedora dvd and install as per procedure then finally system says like that your installation is completed please reboot ur system. So, before reboot I tried to eject my fedora dvd but it couldn't come out. So after click reboot I eject that dvd. And I got error msg like "media test failure exiting intel boot agent". How can I overcome this error.
View 3 Replies View RelatedI was trying to install Fedora to dual boot with Vista in the middle it said that the installation failed and now it will not run grub to let me choose between Windows and Mint which I had installed. All that happens is it shows a command line and says "grub rescue>"
View 1 Replies View Related