Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Boot volume won't mount

Original Message
Name: Pseudonyme
Date: November 2, 2002 at 16:09:35 Pacific
Subject: Boot volume won't mount
OS: BeOS/Windows XP Home
CPU/Ram: pentium 4 1.8ghz/1024mb
Comment:
I have a 60gig hard drive with Windows XP on hda1, Redhat on hda2 (swap on hda3), mandrake on hda4 (swap on hda5), and now I have a fat32 partition on hda6. I had BeOS installed on the fat32 partition, and it always hung up and rebooted before the lightning bolt (This icon appears just before the system enables non-boot CPUs) lights up. I formatted the fat partition in XP (I set it up using partition magic 7) and then installed BeOS again. Now it boots but get stuck on the magnifying glass (the boot volume has been mounted). and displays the following message:

PANIC: The boot loader was unable to find a BeOS volume to boot from. If you are trying to boot from the CD-ROM and find that you are unable to do so, press space during the boot sequence to enter the boot menu and select 'Boot from CD-ROM' as the boot volume.

Kernel debugger: Welcome to Kernel Debugging Land...
eax 0000010d ebp fc00b850 cs 0008 | area 053cff68
ebx 000000fe esp fc00b72c ss 0010 | addr 00100000 size 00087000
ecx 00000200 edi 00000002 ds 0010 |
edx 0000000a esi fc00b750 es 0010 | Thread: sysi ni t2
ei p 00120461 flag 00000246 fs 0000 | Team: kernel_team
trap ffffffff err 00000000 gs 0000 | Stak Trace follows:

00000000 00120461
fc00b850 0011fec1
fc00bf08 0011ef07
kdebug>

Boot failure: The boot loader was unable to find a BeOS volume to boot from. If you are trying to boot from the CD-ROM and find that you are unable to do so, press space during the boot sequence to enter the boot menu and select 'Boot from CD-ROM' as the boot volume.

I downloaded BeOS 5 Personal from bebits.com earlier today. My windows xp uses ntfs partition where i created the fat32 partition. I have a new p4 1.8ghz w/1024mb ram and a 60g ibm hard drive.

Any suggestions/ideas?

Thanks a whole lot,
pseudonyme


Report Offensive Message For Removal


Response Number 1
Name: jefro
Date: November 3, 2002 at 14:10:11 Pacific
Subject: Boot volume won't mount
Reply: (edit)
might need to fix the too much ram thing.
might also need to either get a P4 bootable floppy or try in safe mode "don't call bios"

Report Offensive Follow Up For Removal

Response Number 2
Name: Pseudonyme
Date: November 4, 2002 at 12:54:41 Pacific
Subject: Boot volume won't mount
Reply: (edit)
Too much ram??? Shouldn't BeOS be able to support lots of ram?

The floppy that I am currently booting off of boots fine with a P4. Is there something additional to the Create Floppy program that I need to do? Could the problem be that it will boot the floppy but not realize that the hard drive is there?

How would "don't call bios" help?


Report Offensive Follow Up For Removal

Response Number 3
Name: Pseudonyme
Date: November 4, 2002 at 13:54:20 Pacific
Subject: Boot volume won't mount
Reply: (edit)
Sorry, my reply was premature. I found a Pentium 4 boot disk from www.bedrivers.com, replaced my current Floppy.img with the one i downloaded and created a Pentium 4 boot disk. I still have the same problem. I am searching all over the place for the safe-mode bios thing but I can't find any english URLs. So now I'm down to two questions:
1) Is 1 gig of ram really too much?
and 2) how do I change the safe-mode/bios settings?

Report Offensive Follow Up For Removal

Response Number 4
Name: Andy
Date: November 4, 2002 at 14:36:00 Pacific
Subject: Boot volume won't mount
Reply: (edit)
If you wait until November 23rd, Vasper's BeOS Max Edition V2.1 should be out. I think that will work with your system. Think that'll work jefro?

--andy


Report Offensive Follow Up For Removal

Response Number 5
Name: jefro
Date: November 5, 2002 at 21:31:50 Pacific
Subject: Boot volume won't mount
Reply: (edit)
Dunno. I have yet to hear if yellowtab will fix the 1gig limit on ram. Yes, BeOS only gets worse if you go over 512meg ram. On the safe mode you can choose it by pressing the space bar when you see "Loading....." That will give you a way to choose "Don't call Bios".
Also if you have RDRAM there is a chance that the controller is buggy in beos. Sorry. BeOS was written for Mac's then x86's when all they had was 500mhz machines.

Report Offensive Follow Up For Removal


Response Number 6
Name: Pseudonyme
Date: November 6, 2002 at 13:38:41 Pacific
Subject: Boot volume won't mount
Reply: (edit)

I just installed BeOS on my old celeron 566mhz with 256mb ram! it works
great! It is so easy to use and it detected all of my hardware right off the
bat!
I can't wait until I can get it installed on my P4 w/1gig of ram!

Its fast!

thanks for all the help

-pseudonyme


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Boot volume won't mount

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




ZoneAlarm Question. Blocked Connect

Windows Live Messenger Problem

Delete $Uninstall after SP3 updates

help for hp compaq laptop

Seagate HD works only as slave...


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC