mounting additional ext3

Forum: Other Help Topics
Topic: mounting additional ext3
started by: simplebob

Posted by simplebob on Aug. 05 2005,13:43

So here is my new problem, I added a new hard drive, and i can mount it using:

Code Sample

sudo mount -t ext3 /dev/hdf1 /media

and that works fine. I can then cd to /media and see whats in there. But I now want to mount that every time DSLinux boots up. So I added a line in /etc/fstab that looks like this:

Code Sample

/dev/hdf1 /media ext3 auto,users,exec 0 0

And now when I restart my computer I get this "EXT3-fs warning: Maximal mount count reached, running e2fsck is recommended" after it checks /etc/fstab on startup, is there something wrong with the entry I put in fstab? I google "mounting a ext3 file system automatically in /etc/fstab" and read on how to do it, but I think my effort was futile. I also tried a couple different options in fstab, none of which worked.

Here is my whole /etc/fstab just in case.

Code Sample

# /etc/fstab: filesystem table.
# filesystem mountpoint type options dump pass
/dev/hde2 / ext2 defaults,errors=remount-ro 0 1
proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/hdf1 /media ext3 auto,users,exec 0 0
# partitions found by dsl
#/dev/hde2 /mnt/hde2 auto noauto,users,exec 0 0
/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0
# Added by KNOPPIX
/dev/hde1 none swap defaults 0 0

Any one have any Ideas on what I should change?

Posted by mikshaw on Aug. 05 2005,16:15

Did that actually prevent you from accessing the drive? I get the same, or very similar, message every time i start DSL...never really paid attention to it because it didn't prevent me from doing anything.

By the way, the fact that it says "warning" and not "error" is a pretty good sign that it's nothing serious.

Posted by mstrhelix on Aug. 07 2005,02:00

are you sure the drive name is /dev/hdf1

?

do a dmesg |grep hd

that will list all your hard drives
and see if hdf1 is in their if not that might be your problem

Posted by simplebob on Aug. 09 2005,16:25

dmesg |grep hd gave me this output:

Code Sample

dsl@box:~$ dmesg |grep hd
Kernel command line: BOOT_IMAGE=knoppix ro root=2102 hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce
ide_setup: hda=scsi
ide_setup: hdb=scsi
ide_setup: hdc=scsi
ide_setup: hdd=scsi
ide_setup: hde=scsi
ide_setup: hdf=scsi
ide_setup: hdg=scsi
ide_setup: hdh=scsi
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
ide2: BM-DMA at 0xb400-0xb407, BIOS settings: hde:DMA, hdf:DMA
ide3: BM-DMA at 0xc000-0xc007, BIOS settings: hdg:pio, hdh:pio
hde: WDC WD400EB-00CPF0, ATA DISK drive
hdf: WDC WD400JB-00ETA0, ATA DISK drive
hdg: HL-DT-ST GCE-8400B, ATAPI CD/DVD-ROM drive
hdh: LITE-ON DVDRW SOHW-812S, ATAPI CD/DVD-ROM drive
hdh: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hdh: set_drive_speed_status: error=0x04
hde: attached ide-disk driver.
hde: host protected area => 1
hde: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=77545/16/63
hdf: attached ide-disk driver.
hdf: host protected area => 1
hdf: 78165360 sectors (40021 MB) w/8192KiB Cache, CHS=4865/255/63
hde: hde1 hde2
hdf: hdf1
hdg: attached ide-scsi driver.
hdh: attached ide-scsi driver.

so i am going to assume that by that, hdf1 is in fact recognized. any other recommendations? is there something wrong with my entry in fstab?