Sponsored Content
Operating Systems Linux No Hard Drives Have Been Found Post 302215785 by tamcomng on Thursday 17th of July 2008 07:19:40 AM
Old 07-17-2008
No Hard Drives Have Been Found

I am using an Acer Aspire 4720Z with two partitions C and D. Windows is installed on C and I decided to install Red Hat Linux 9 in partition D. The two partitions are in NTFS file system. During my installation of the the Linux, a prompt was displayed on screen with the message: "No hard drives have been found. You probably need to manually choose device drivers for the installation to succeed. Would you like to select drivers now?"

Please can anyone help me solve this problem?

Thanks.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hard drives

Will some one tell me what this means. "warning: ida 0 <slot 6> : command timed out on dev 1/42 blk 4824290 logical unit=0 blocks=5512102, size 2, cmd=0x20." I'm running SCO 505 on a proliant 1600r. Thnank you in advance. (3 Replies)
Discussion started by: franruiz
3 Replies

2. Solaris

formating and repartitioning an external hard drives

Version: solaris 10 x86 I just got a western digital external harddrive formated with fat 32. this drive came with some setup files which is meant for windows or mac. I want to reformat and partition this drive into two ( for solaris and windows) such that the setup files will still be there... (2 Replies)
Discussion started by: seyiisq
2 Replies

3. Filesystems, Disks and Memory

Help adding new hard drives

Folks; I just added 2 physical new hard drives to my SUSE server. My server is already running SUSE 10.3 version. Is there a command i can use to add the new space or even see if the system can sees them? (3 Replies)
Discussion started by: Katkota
3 Replies

4. Solaris

Reinstall old hard drives

I have a T2000 Sun-Fire server. I have 2 sets of drives in a raid 1. Lets call them Set A and Set B. I had Set A installed and working. I needed a new install so I so build up Set B. After some time I wanted to put Set A back in the server. Now the system will not boot off of Set A. I tried to boot... (7 Replies)
Discussion started by: stu1811
7 Replies

5. Hardware

Hard Drives and MBR

Hello everyone. I have a question which I may know the answer to, I'm just looking for a confirmation. When it comes to the MBR of a hard drive, i've read in multiple sources that it's always located in the first sector of the hard drive. Is the MBR there from the factory? When I buy a new blank... (3 Replies)
Discussion started by: Lost in Cyberia
3 Replies

6. Solaris

Trying to boot Solaris without hard drives in T5220

I have three Sun Oracle Netra T5220s. I am trying to just get the processor information psrinfo or prtdiag -v from the # prompt in single user mode. I am needing to know the commands to get to boot the CD/DVD of the Solaris OS. I am using it via Serial Port Management. Tinkering around I... (4 Replies)
Discussion started by: nerdboy
4 Replies

7. Linux

Create LVM of 2 Hard Drives while installing Centos 6.4.

Hello, I have install 2 HDD in my server and now installing the Centos6.4. I want create the LVM of those 2 HDD's so while i'm doing this it is not allowing me to select these 2 disk's from allowable disk list. Same problem if i tried to make Software RAID with creating LVM. Please help. (1 Reply)
Discussion started by: purushottamaher
1 Replies

8. Ubuntu

Hard Drives Undetected on My Machine - But Mounts on All Other Machines

Dear All, Hope you are doing great. I ran into a very strange issue. I have a Dell T7500 machine that runs ubuntu 12. I have 8 different drives from different manufacturers of varying sizes with data on them. These 8 drives were hooked to this Dell machine using external docking stations. Now,... (20 Replies)
Discussion started by: jacobs.smith
20 Replies

9. Solaris

Solaris 8 - Accessing Hard Drives

Hi, I have two SCSI Hard Drives in a Sun Solaris 8 server as shown below. I would like to access Disk1 and look at its contents, directory structure and files. How do I change my default directory from Disk 0 to Disk 1 and vice versa? Thank you. (5 Replies)
Discussion started by: ssabet
5 Replies

10. UNIX for Beginners Questions & Answers

Understanding volumes and hard drives

Ok so i thought i was smart but i can tell I need some help. I am playing around with understanding lvm and adding disks to a linux box. I added a disk and then ran what i thought were commands to add this disk to the box but I think I messed up and would like some help. My question is did i... (5 Replies)
Discussion started by: cptkirkh
5 Replies
GPTBOOT(8)						    BSD System Manager's Manual 						GPTBOOT(8)

NAME
gptboot -- GPT bootcode for UFS on BIOS-based computers DESCRIPTION
gptboot is used on BIOS-based computers to boot from a UFS partition on a GPT-partitioned disk. gptboot is installed in a freebsd-boot par- tition with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptboot only boots from tables with 128 partitions or less. PARTITION ATTRIBUTES
gptboot checks and manages several attributes of GPT UFS partitions. bootme Attempt to boot from this partition. If more than one partition has the bootme attribute set, gptboot will attempt to boot each one until successful. bootonce Attempt to boot from this partition only one time. Setting this attribute with gpart(8) automatically also sets the bootme attribute. Multiple partitions may have the bootonce and bootme attributes set. bootfailed The bootfailed attribute marks partitions that had the bootonce attribute set, but failed to boot. This attribute is managed by the system. See BOOTING and POST-BOOT ACTIONS below for details. USAGE
For normal usage, the user does not have to set or manage any of the partition attributes. gptboot will boot from the first UFS partition found. The bootonce attribute can be used for testing an upgraded operating system on an already-working computer. The existing system partition is left untouched, and the new version of the operating system to be tested is installed on another partition. The bootonce attribute is set on that new test partition. The next boot is attempted from the test partition. Success or failure will be shown in the system log files. After a successful boot of the test partition, a user script can check the logs and change the bootme attributes so the test partition becomes the new system partition. Because the bootonce attribute is cleared after an attempted boot, a failed boot will not leave the system attempting to boot from a partition that will never succeed. Instead, the system will boot from the older, known-working operating system that has not been modified. If the bootme attribute is set on any partitions, booting will be attempted from them first. If no partitions with bootme attributes are found, booting will be attempted from the first UFS partition found. BOOTING
gptboot first reads the partition table. All freebsd-ufs partitions with only the bootonce attribute set, indicating a failed boot, are set to bootfailed. gptboot then scans through all of the freebsd-ufs partitions. Boot behavior depends on the combination of bootme and bootonce attributes set on those partitions. bootonce + bootme Highest priority: booting is attempted from each of the freebsd-ufs partitions with both of these attributes. On each partition, the bootme attribute is removed and the boot attempted. bootme Middle priority: booting is attempted from each of the freebsd-ufs partitions with the bootme attribute. If neither bootonce nor bootme attributes are found on any partitions, booting is attempted from the first freebsd-ufs partition on the disk. POST-BOOT ACTIONS The startup script /etc/rc.d/gptboot checks the attributes of freebsd-ufs partitions on all GPT disks. Partitions with the bootfailed attribute generate a ``boot from X failed'' system log message. Partitions with only the bootonce attribute, indicating a partition that successfully booted, generate a ``boot from X succeeded'' system log message. The bootfailed attributes are cleared from all the partitions. The bootonce attribute is cleared from the partition that successfully booted. There is normally only one of these. FILES
/boot/gptboot bootcode binary /boot.config parameters for the boot blocks (optional) EXAMPLES
gptboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically installed in combination with gptboot. Install gptboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 gptboot can also be installed without the PMBR: gpart bootcode -p /boot/gptboot -i 1 ada0 Set the bootme attribute for partition 2: gpart set -a bootme -i 2 ada0 Set the bootonce attribute for partition 2, automatically also setting the bootme attribute: gpart set -a bootonce -i 2 ada0 SEE ALSO
boot.config(5), rc.conf(5), boot(8), gpart(8) HISTORY
gptboot appeared in FreeBSD 7.1. AUTHORS
This manual page written by Warren Block <wblock@FreeBSD.org>. BSD
February 5, 2014 BSD
All times are GMT -4. The time now is 02:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy