LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 11-16-2008, 06:08 AM   #1
unfuniak
LQ Newbie
 
Registered: Nov 2005
Posts: 7

Rep: Reputation: 0
Can't install Linux- How to fix a "stop:0x0000007b"


I'm not sure this belongs to this section, but I give it a go.

My computer is a Dell Optiplex 755.

Yesterday I tried to reformat my computer with a xp CD because I felt it was infected with crap. I did the usual stuff, got through the blue window when the Pc froze. Pressing the alt+ctrl didnt help so I had the pc shut down by holding down the start button for a few mins, I then start it up again but this time windows couldn't complete running, it would only load halfway and the stop:
Quote:
0x0000007b (0xf78DA524, 0XC0000034, 0X00000000, 0X00000000)
. I have tried using other xp cds but the same blue screen comes up b4 windows could completely load and start installing.

I tried pressing "Press F6 if you have to install a third-party SCSI or RAID driver". But with no result.

So I figured what the heck, lets install linux. I have two different Linuxes, Debian and ubuntu. When I tried to install ubuntu I received this message:

Quote:
BusyBox v1.1.3 (Debian 1:1.1.3-2ubuntu3) Built-in shell (ash)
/bin/sh: can't access tty; job control turned off
..and when i tried with Debian it stops with
Quote:
"Your installation CD-ROM couldn't be mounted. This probably means that the CD-Rom was not in the drive. If so you can insert it and try again"
The odd thing is that it is inserted.

Now I used google to search for the first problem and came here
http://support.microsoft.com/kb/324103

Now I don't really know what to do, can it be a Boot-Sector Virus ..and how do I remove it?

Now to the very Important thing, I don't want xp in my computer, I want Linux Ubuntu. So how do I continue from the ubuntu message I received?
 
Old 11-16-2008, 06:15 AM   #2
Dailan
LQ Newbie
 
Registered: Jun 2008
Posts: 5

Rep: Reputation: 0
Yairs.

Irrespective of the Windows Knowledge Base thing, I suspect it's SATA controller issue.

Do you have some odd hardware stuff going on? Sparkly new SATA drive or the like?

Dailan
 
Old 11-16-2008, 06:18 AM   #3
unfuniak
LQ Newbie
 
Registered: Nov 2005
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Dailan View Post
Yairs.

Irrespective of the Windows Knowledge Base thing, I suspect it's SATA controller issue.

Do you have some odd hardware stuff going on? Sparkly new SATA drive or the like?

Dailan
I have no new things going on. I've also heard of the SATA issue but I don't know how to proceed.
 
Old 11-16-2008, 06:32 AM   #4
pinniped
Senior Member
 
Registered: May 2008
Location: planet earth
Distribution: Debian
Posts: 1,732

Rep: Reputation: 50
Quote:
Originally Posted by unfuniak View Post
Now to the very Important thing, I don't want xp in my computer, I want Linux Ubuntu. So how do I continue from the ubuntu message I received?
Since you were dumped into BusyBox (I presume after a long wait?), that means that the boot process ran fine - the kernel loaded, initalized the system, and loaded the initramfs image. Now something went wrong when switching from the initramfs image to the final running filesystem - usually this means the wrong "root=" parameter was supplied to the kernel (a common problem when bootloading with 'grub') or in more extreme cases that the HDs somehow could not be detected (some driver - for example SATA - was not included in the initramfs image or else was included but not loaded into the kernel).

SO - see if you can spot anything in the 'messages' file:

dmesg | less

Press 'G' to jump to the end and work your way backwards through the messages; see if you can spot any about 'sda' or 'hda' or similar - well, anything about disk drives anyway.

Once you're convinced that the drivers are loaded and your system is in fact aware of the HDs, that suggests that "root=" is incorrect. When you reboot, press a key to get into grub's interactive mode. Use the upa nd down arrows to select the system you want to boot, then I think it's 'e' to edit. You will have to change the "root=" argument to something appropriate - if, for example, grub called it something like 'sdb1', then try 'sda1'. If grub called it 'sda1' you could try 'hda1' (or even 'sdb1', although this is not likely the case). Once you get the system booted through, edit /boot/grub/menu.lst and fix that "root="
 
Old 11-16-2008, 06:46 AM   #5
unfuniak
LQ Newbie
 
Registered: Nov 2005
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by pinniped View Post
Since you were dumped into BusyBox (I presume after a long wait?), that means that the boot process ran fine - the kernel loaded, initalized the system, and loaded the initramfs image. Now something went wrong when switching from the initramfs image to the final running filesystem - usually this means the wrong "root=" parameter was supplied to the kernel (a common problem when bootloading with 'grub') or in more extreme cases that the HDs somehow could not be detected (some driver - for example SATA - was not included in the initramfs image or else was included but not loaded into the kernel).

SO - see if you can spot anything in the 'messages' file:

dmesg | less

Press 'G' to jump to the end and work your way backwards through the messages; see if you can spot any about 'sda' or 'hda' or similar - well, anything about disk drives anyway.

Once you're convinced that the drivers are loaded and your system is in fact aware of the HDs, that suggests that "root=" is incorrect. When you reboot, press a key to get into grub's interactive mode. Use the upa nd down arrows to select the system you want to boot, then I think it's 'e' to edit. You will have to change the "root=" argument to something appropriate - if, for example, grub called it something like 'sdb1', then try 'sda1'. If grub called it 'sda1' you could try 'hda1' (or even 'sdb1', although this is not likely the case). Once you get the system booted through, edit /boot/grub/menu.lst and fix that "root="
I suspect that SATA was not included. I stumbled upen a message saying you harddrive could not be found when using Acronis Disk Director. What should I do now?
 
  


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
How to stop bash from replacing "~/" with "/home/username"? daihard Linux - Software 8 08-22-2010 03:32 PM
?Possible to choose "Update" during Install (Reinstall)? to fix sound file forgeonx Linspire/Freespire 4 01-21-2008 06:05 AM
Install Fedora Core 4 issue (Stop at process of "CD Found") Sun Fedora - Installation 0 01-24-2007 12:44 PM
LXer: Petition to all us Linux users to stop telling newbies "RTMF". LXer Syndicated Linux News 2 03-29-2006 08:22 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 04:08 AM.

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