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 10-30-2007, 07:14 PM   #1
ilw
LQ Newbie
 
Registered: Nov 2004
Posts: 8

Rep: Reputation: 0
Grub error 17


i have grub installed and can boot into ubuntu gutsy fine normally. But i've also got another hard drive which has a messed up partition & windows NTLDR on it, and if i connect that hard drive grub gets as far as stage 1.5 and then spits out error 17.

I've looked around on the web and i reckon that its because adding the hard drive is mucking up the boot order/device map, but i don't know how to solve this problem as i can't boot with the drive connected (supergrub also didn't seem to manage to boot my system) and i can't do anything to the drive when its not attached. I thought i could do something by booting with the live-cd, but i'm not sure exactly what to do and i can't access the internet from the live-cd version because i need extra drivers & ndiswrapper so i thought i'd ask for advice and try and work out exactly what to do before fiddling around too much with grub as i totally don't understand it.

My bios has all the hard drives set to auto and is supposed to try hdd 0 first (changing this to hdd 1-3 seemed to do nothing), but also looks for other boot devices. The bios only seems to pick up IDE hard drives (its an A7N8X deluxe which i think I had to flash to get SATA support).


Without the extra drive (when I add the extra drive it goes on as slave on either IDE0 or IDE1 and i've checked the jumper settings are correct)
fdisk -l reports the following set up
Code:
Disk /dev/hda: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa957b1bf

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1       10010    80405293+   7  HPFS/NTFS

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x07159e41

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        4863    39062016   83  Linux
/dev/sda2            4864        5106     1951897+  82  Linux swap / Solaris

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00013cb6

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       19457   156288321    6  FAT16
device.map shows:

Code:
(hd0)	/dev/hda
(hd1)	/dev/sda
(hd2)	/dev/sdb


menu.lst shows:

Code:
# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default		0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout		3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title		Windows 95/98/NT/2000
# root		(hd0,0)
# makeactive
# chainloader	+1
#
# title		Linux
# root		(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=074c9d6a-c235-4ef2-a129-b27316dd217d ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title		Ubuntu 7.10, kernel 2.6.22-14-generic
root		(hd1,0)
kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=074c9d6a-c235-4ef2-a129-b27316dd217d ro quiet splash
initrd		/boot/initrd.img-2.6.22-14-generic
quiet

title		Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root		(hd1,0)
kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=074c9d6a-c235-4ef2-a129-b27316dd217d ro single
initrd		/boot/initrd.img-2.6.22-14-generic

title		Ubuntu 7.10, memtest86+
root		(hd1,0)
kernel		/boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

and finally fstab shows:

Code:
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/sda1
UUID=074c9d6a-c235-4ef2-a129-b27316dd217d /               ext3    defaults,errors=remount-ro 0       1
# /dev/hda1
UUID=2CC0D0FBC0D0CBE8 /media/hda1     ntfs    defaults,umask=007,gid=46 0       1
# /dev/sdb1
UUID=ECD09AC8D09A9902 /media/sdb1     ntfs    defaults,umask=007,gid=46 0       1
# /dev/sda2
UUID=ce4ae8ae-0b4a-41fd-93ad-b0bcc8991cc2 none            swap    sw              0       0
/dev/hdd        /media/cdrom0   udf,iso9660 user,noauto,exec 0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec 0       0


Any help greatly appreciated

Last edited by ilw; 10-30-2007 at 07:16 PM.
 
Old 10-31-2007, 05:34 AM   #2
bigrigdriver
LQ Addict
 
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian stable
Posts: 5,908

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
To make certain that the hardware (jumper settings), BIOS, and grub are all working from the same game plan, do the following to see if matters improve:
1) Set the jumper on sda to master; jumper on sdb to slave; jumper on hda to master.
2) Edit the BIOS settings. Set sda to Primary Master, sdb to Primary Slave, and hda to Secondary Master.
3) Edit the BIOS settings. Set the boot order as follows: hdd (cdrom drive) first, sda second, sdb third, hda fourth.
4) Boot into Ubnuntu (or from Ubuntu as liveCD) and edit /boot/grub/menu.lst. You present menu.lst doesn't seem to have an entry for Windows, although there is an example entry:
Quote:
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1]
which you can copy and edit to read:
Quote:
title Windows 95/98/NT/2000
root (hd2,0)
map (hd2) (hd0)
map (hd0) (hd2)
makeactive
chainloader +1
At this point, it doesn't matter whether hda1 is bootable. It does matter that hda1 is taking over the boot process and bombing out because of a corrupt filesystem. First get things to a sane state that allows grub to boot sda without interference from hda, even when hda is connected.

Once that is done, you can try to mount hda manually to pull off any data you wan to save, then reformat, reinstall windows, or whatever else you want to do.

Last edited by bigrigdriver; 10-31-2007 at 05:41 AM.
 
Old 10-31-2007, 06:23 AM   #3
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
There are some confusions

(1) Sata has no master and slave jumper setting. It never has.

(2) The OP may be talking about hooking the 4th disk because this statement
Quote:
i have grub installed and can boot into ubuntu gutsy fine normally. But i've also got another hard drive which has a messed up partition & windows NTLDR on it, and if i connect that hard drive grub gets as far as stage 1.5 and then spits out error 17.
suggests Linux is booting happliy from partition (h1,0) meaning there is a (hd0) which should be hda. Thus hda is always required and "adding a disk with Windows NTLDR on it causing the Linux to fail to boot" should be unrelated to disk hda and has to be either sdb or a 4th disk. Since Linux did booted in order to obtain the information therefore it should adding a 4th disk that causes the problem.

(3) The Linux menu.lst has no entry for booting system other than Linux. Thus the ntfs partition of hda1 has never been booted. The "#" in front of every line in menu.lst is inactive and ignored by Grub.

(4) If the Linux system boots up successfully with the 3 disks of hda, sda and sdb then the new disk if added causing Grub to fail is not featured in the information supplied by the OP. Therefore amending the menu.lst at this stage may be inadvisable.

-------------------------------------------------------------------

I would suggest the problem investigated as follow

(a) When Linux boots up activate a Grub shell and record the disk order as seen by Grub by commands
Code:
sudo grub
geometry (hd0)
geometry (hd1)
geometry (hd2)
quir
Check to ensure (hd0) has 82Gb, (hd1) 320Gb and (hd2) 160Gb. If this is the case the information in Post #1 is verified and can be trusted.

(b) Power down the PC. Hook up the troubled hard disk. Insert any Live CD or Ubuntu installable Live CD. Boot it up and do the same thing again but add an extra command
Code:
geometry (hd3)
.

If the geometry of the first 3 disks remain unchanged then adding the 4th disk should not affect Grub.

If the geometries of the disks change then re-order them in the Bios.

My prediction is the new disk to be added may be wrongly set up. An example is the OP fed a Pata disk already jumpered as master the same ribbon cable of hda thereby causing a confusion to the Bios which cannot decide which one is correct so it plays safe by ignoring both disks. A consequence would be the disappearance of hda causing the Bios to obtain the Grub files from the new 2nd disk which is sdb. Grub error 17 is "cannot mount partition" because sdb1 isn't a Linux partition and does not have a matching uuid number as sda1 but Grub has been instructed to search it from partition (hd1,0).

If my prediction is correct then Grub should see only 2 disks when 4 have been connected.

Last edited by saikee; 10-31-2007 at 06:29 AM.
 
Old 10-31-2007, 04:37 PM   #4
ilw
LQ Newbie
 
Registered: Nov 2004
Posts: 8

Original Poster
Rep: Reputation: 0
Cheers for the help guys.

@bigrigdriver: I'm pretty sure i've got the jumper settings round the right way (mainly because i had the jumper set wrong at first and it gave a different error...), also my bios doesn't let me specify boot order from sata drives, or if it does its not clear which drive is which as they're just labelled hdd0 hdd1 hdd2 hdd3 and i have no idea which is which.
Your suggestion of getting to a state where hda boots so i can pull data off sounds perfect, but i'm not sure if your current instructions will let me do that as i think i wasn't clear enough or you misinterpreted what i'd written when describing the problem. I think Saikee understands what i was trying to say and probably explains it better than i did.

@Saikee: I did what you suggested, but wasn't sure about reordering the hard drives in the bios. I had already tried doing this earlier without success, but as i said above the bios doesn't seem to 100% support SATA and i have no idea which drive is which in bios. I'll try again, but i thought i'd post the results of the grub geometry to see if you or anyone else has any other suggestions while I'm fiddling in bios.


When i have 3 hard drives installed and boot normally into ubuntu my grub geometry is:
Code:
grub> geometry (hd0)
drive 0x80: C/H/S = 10011/255/63, The number of sectors = 160836480, /dev/hda
   Partition num: 0,  Filesystem type unknown, partition type 0x7

grub> geometry (hd1)
drive 0x81: C/H/S = 38913/255/63, The number of sectors = 625142448, /dev/sda
   Partition num: 0,  Filesystem type is ext2fs, partition type 0x83
   Partition num: 1,  Filesystem type unknown, partition type 0x82

grub> geometry (hd2)
drive 0x82: C/H/S = 19457/255/63, The number of sectors = 312581808, /dev/sdb
   Partition num: 0,  Filesystem type unknown, partition type 0x6



When i connect up the additional hard drive and boot using a live cd my geometry looks like:
Code:
grub> geometry (hd0)
drive 0x80: C/H/S = 10011/255/63, The number of sectors = 160836480, /dev/hda
   Partition num: 0,  Filesystem type unknown, partition type 0x7

grub> geometry (hd1)
drive 0x81: C/H/S = 24792/255/63, The number of sectors = 398297088, /dev/hdd
   Partition num: 0,  Filesystem type unknown, partition type 0x7

grub> geometry (hd2)
drive 0x82: C/H/S = 38913/255/63, The number of sectors = 625142448, /dev/sda
   Partition num: 0,  Filesystem type is ext2fs, partition type 0x83
   Partition num: 1,  Filesystem type unknown, partition type 0x82

grub> geometry (hd3)
drive 0x83: C/H/S = 19457/255/63, The number of sectors = 312581808, /dev/sdb
   Partition num: 0,  Filesystem type unknown, partition type 0x6

and i ran fdisk -l while in the live-cd boot as well just to see what it would say:

Code:
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x07159e41

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        4863    39062016   83  Linux
/dev/sda2            4864        5106     1951897+  82  Linux swap / Solaris

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00013cb6

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       19457   156288321    6  FAT16

Disk /dev/hda: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa957b1bf

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1       10010    80405293+   7  HPFS/NTFS

Disk /dev/hdd: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000076dc

   Device Boot      Start         End      Blocks   Id  System
/dev/hdd1               1       24792   199141708+   7  HPFS/NTFS




Thanks again!
 
Old 10-31-2007, 04:55 PM   #5
ilw
LQ Newbie
 
Registered: Nov 2004
Posts: 8

Original Poster
Rep: Reputation: 0
Bios testing took less time than i thought, but didn't produce anything useful (i don't think).
Code:
first boot device               result

hdd0                            grub error 17 
hdd1                            system hung with no grub messages at all
hdd2                            grub error 17
hdd3                            grub error 17
However I should point out that I think when i set it to hdd2 or hdd3, it didn't actually try and load anything from the sata disks, instead i think it found nothing bootable on the ide ports and went to the second boot device (which i had set to hdd0 at all times) and this gave the grub error 17. My bios gives me the option of booting from 4 hard drives, but i think thats because there are 4 possibe ide ports its jsut a coincidence that i actually have 4 hard drives (similarly the bios offers me the option of booting from ls120 drive, but i don't have one...)
 
Old 10-31-2007, 05:17 PM   #6
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
As fate has it your new disk is the 4th one and it did upset the booting order.

You can tell which disk by (1) size and (2) partition it contains.

Before you added the 4th disk the only bootable system is sda1 with partition Type 83 for Linux. In the 3-disk setup Grub confirms sda is (hd1). Therefore when you select Utbuntu to boot Grub executes
Code:
title		Ubuntu 7.10, kernel 2.6.22-14-generic
root		(hd1,0)
kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=074c9d6a-c235-4ef2-a129-b27316dd217d ro quiet splash
initrd		/boot/initrd.img-2.6.22-14-generic
because Grub counts from zero and the 1st partition of the 2nd disk is (hd1,0).

In the 4-disk setup the (hd1) position was given to your 4th disk which is about 200Gb large and has a single Type 7 (NTFS) partition inside. The name hdd suggests it is a Pata disk and is the slave of the secondary IDE cable.

The whole thing is crystal clear me.

Explanation------------------------------------------------

You are using a old Linux which has a kernel older than 2.6.20. If it is newer then it is one of the few that still supports Pata disk names of hda, hdb, hdc and hdd, as newer kernels have abandoned Pata disk device names and call them same as SCSI/Sata/USB disks like sda, sdb, sdc,sdd, sde etc.

The hda and hdb are master and slave in the primary IDE channel whereas hdc and hdd are the same but in the secondary IDE channel. The names are fixed as per the mobo connection points. The fact that hdd was read means it have been correectly jumpered.

Your mobo could be relatively old too but very reliable in detecting the Pata disk before Sata. Therefore hda and hdd are detected first and so become disk (hd0) and (hd1) in the Bios from which Grub obtains the information. The Sata sda and sdb are detected after the Pata so they take up the disk position as (hd2) and (hd3).

Now the cure (4- disk setup, assuming no change in the Bios after Post #4)------------------------------------------------------

You Linux will boot if you use a Live CD, say a Ubuntu, make a mount point /mnt/sda1, mount the device /dev/sda1 on it and edit it /boot/grub/menu.lst
Code:
sudo su
mkdir /mnt/sda1
mount /dev/sda1 /mnt/sda1
gedit /mnt/sda1/boot/grub/menu.lst
and amend the booting instructions (marked in red) as follow
Code:
title		Ubuntu 7.10, kernel 2.6.22-14-generic
root		(hd2,0)
kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=074c9d6a-c235-4ef2-a129-b27316dd217d ro quiet splash
initrd		/boot/initrd.img-2.6.22-14-generic
quiet

title		Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root		(hd2,0)
kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=074c9d6a-c235-4ef2-a129-b27316dd217d ro single
initrd		/boot/initrd.img-2.6.22-14-generic

title		Ubuntu 7.10, memtest86+
root		(hd2,0)
kernel		/boot/memtest86+.bin
I expect your next post to be a good news and we can all go home. (Do not forget to read Post #7 & 8 too)

Last edited by saikee; 10-31-2007 at 05:50 PM.
 
Old 10-31-2007, 05:37 PM   #7
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 18,479

Rep: Reputation: 3095Reputation: 3095Reputation: 3095Reputation: 3095Reputation: 3095Reputation: 3095Reputation: 3095Reputation: 3095Reputation: 3095Reputation: 3095Reputation: 3095
A good reason to always have the boot partition on the same physical disk as the (active) MBR.
The grub MBR record has a device flag that indicates where it's code is. If, as seems likely, your additional disk appears as hd1, you have to fix the MBR to point some where else.
And "un-fix" it when you take the additional disk out again.

Boot a liveCD, from a terminal locate your (disk based) /boot/grub directory, and use the "root" and "setup" commands to re-write the MBR.
I'm sure saikee has something on how to do this.

Edit: D'oh; too slow typing up a reply again.

Last edited by syg00; 10-31-2007 at 05:39 PM.
 
Old 10-31-2007, 05:47 PM   #8
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
syg00,

Thanks you for reminding me as I have missed out the restoring Grub from the (hd1,0) partition.

This should be done while the boot up Ubuntu CD is still operation. There are two methods which give identical results

Linux way------------------------------
Code:
sudo su
chroot /mnt/sda1
grub-install /dev/hda
exit
reboot
This allows the user to get "inside" the unbootable Ubuntu of sda1 and fire up the grub-install command. As the instruction was issued inside sda1 so a connection with the MBR of hda is made.

Grub shell/Grub prompt way (using Grub)------------------------------
Code:
sudo su
grub
root (hd2,0)
setup (hd0)
quit
reboot
The "sudo su" can be omitted if you are already in root.

Last edited by saikee; 10-31-2007 at 05:49 PM.
 
Old 10-31-2007, 07:03 PM   #9
ilw
LQ Newbie
 
Registered: Nov 2004
Posts: 8

Original Poster
Rep: Reputation: 0
Good news indeed, you may all go home safe in the knowledge that another linux noob has been helped

Thanks!


Very small point, but just in case other people end up finding & following these instructions, i ran into a minor error while following the instructions
Code:
sudo su
chroot /mnt/sda1
grub-install /dev/hda
exit
reboot
as i received an error saying:

Code:
root@ubuntu:/home/ubuntu# chroot /mnt/sda1
root@ubuntu:/# grub-install /dev/hda
/dev/hda: Not found or not a block device.
wasn't sure if there should be a number after the hda? but i followed your alternate grub instructions and they went smoothly
 
Old 11-01-2007, 08:13 AM   #10
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
ilw ,

Just a storm in a tea cup.

Your installed Linux is older. The Live CD Linux is newer.

Linux with 2.6.20 kernel or newer has abandoned the Pata disk device names hda, hdb, hc and hdd.#

All hard disks of SCSI, Pata, Sata and USB type in newer Linux are called sda, sdb, sdc, sdd, sde,.......etc and handled by libATA module.

Thus the Live CD Linux does not has a device name for hda. Don't take my word for it see it yourself in root console by commands
Code:
fdisk -l
ls /dev
If hda is available it will be inside /dev directory
 
  


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
Sofware RAID 1 + Fedora Core 3 + Boot Error L1 + GRUB 21 ERROR najeebsyed2 Linux - Hardware 0 10-25-2007 02:20 PM
Grub error 17, and wont reinstall using grub-install! chiefreborn Linux - General 6 06-06-2007 11:29 AM
Error Grub stage2 loading error (using FC6) on seperate hdd Anifield Linux - Newbie 7 03-20-2007 02:14 PM
Grub Error 17: Cannot mount selected partition and other Grub problems Sebastian Naitsabes Linux - General 1 07-05-2005 09:33 AM

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

All times are GMT -5. The time now is 03:53 PM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration