LinuxQuestions.org - Unable to mount /dev/hdd

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Unable to mount /dev/hdd (https://www.linuxquestions.org/questions/slackware-14/unable-to-mount-dev-hdd-298084/)

Unable to mount /dev/hdd

Hi guys, just installed Slack 10.1 and seem to have a problem.

This is the output of cat /proc/partitions:

Code:

major minor  #blocks  name



  22    64 1073741823 hdd

  3    0  78150744 hda

  3    1  10490413 hda1

  3    2          1 hda2

  3    5  31463271 hda5

  3    6  26218048 hda6

  3    7    2104483 hda7

  3    8    4200966 hda8

  3    9    3670821 hda9

  3    64  39082680 hdb

  3    65          1 hdb1

  3    66  10490413 hdb2

  3    69    5261256 hdb5

  3    70  21229866 hdb6

  3    71    2096451 hdb7

Whenever I run mount /dev/hdd some_dir, I get the 'mount: /dev/hdd is not a valid block device'. I don't get it, I could mount this hard drive perfectly fine in Slack 10. Any ideas what I'm doing wrong?

what does :"$dmesg |grep hdd " say ?
is it recognised and how....

and how do you try to mount it ?

egag

dmesg | grep yields:

Code:

Kernel command line: BOOT_IMAGE=Slackware-10.1 ro root=308 hdc=ide-scsi hdd=ide-scsi

ide_setup: hdd=ide-scsi

    ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA

hdd: WDC WD2000JB-00GVA0, ATA DISK drive

 hdd:end_request: I/O error, dev 16:40 (hdd), sector 0

end_request: I/O error, dev 16:40 (hdd), sector 2

end_request: I/O error, dev 16:40 (hdd), sector 4

end_request: I/O error, dev 16:40 (hdd), sector 6

end_request: I/O error, dev 16:40 (hdd), sector 0

end_request: I/O error, dev 16:40 (hdd), sector 2

end_request: I/O error, dev 16:40 (hdd), sector 4

end_request: I/O error, dev 16:40 (hdd), sector 6

The first line which states the 'hdd=ide-scsi' has been removed from quite a while back. To mount the drive, I used:

Code:

mount /dev/hdd /mnt/thanatos

------
The first line which states the 'hdd=ide-scsi' has been removed from quite a while back
------

don't understand that...
is that option in the lilo.conf file ?

and is it a harddisk- or a cdrw-drive ?
if it's a hd. , ide-scsi is not ok.

egag

/dev/hdd is a hard drive. When I first installed slack 10.1 (fresh install), I accidently appended 'hdd=ide-scsi' in lilo.conf (/dev/hdd used to be a dvd-rw drive). Anyway, I soon realised my error and removed it from lilo.conf and rebooted. I'm not too familiar with dmesg and hence I thought that that line was from before when I tried to mount the drive without removing 'hdd=ide-scsi' from the boot option.

My lilo.conf now reads:

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

append="hdc=ide-scsi"

boot = /dev/hda

#compact        # faster, but won't work on all systems.

prompt

timeout = 300

# VESA framebuffer console @ 1024x768x64k

vga = 791

# ramdisk = 0    # paranoia setting

# End LILO global section

# Linux bootable partition config begins

image = /boot/vmlinuz

  root = /dev/hda8

  label = Slackware-10.1

  read-only # Non-UMSDOS filesystems should be mounted read-only for checking

# Linux bootable partition config ends

# Windows bootable partition config begins

other = /dev/hda1

  label = WindowsXP

  table = /dev/hda

# Windows bootable partition config ends

Hope this clears it up.

did you run "#lilo " after editing the config- file ?
if not, do that.....

egag

What output do you get from the following command ' /sbin/fdisk -l '. Requires root acces to run

Brian1
" Google the Linux way @ http://www.google.com/linux "

LOL!!! Of course. I didn't run lilo after I did that. How stupid can I possibly be?! Thanks. Will post back if that solves it.

Yup! That did it. I really should not even be allowed near a linux system after a mistake like that. Thanks a lot egag, and you too Brian1.

edit: nevermind :)

good to see you got it working

I fixed it. After running lilo, the partition came up right in /proc/partitions and I mounted the correct partition (/dev/hdd1). Thanks anyway guys!

Quote:

Originally posted by deveraux83
Yup! That did it. I really should not even be allowed near a linux system after a mistake like that. Thanks a lot egag, and you too Brian1.

ah...sometimes i forget that too.......and i'm not alone.
and the worst is that right now you think you'll never forget that,
but tomorrow or next month.... :)

egag