can't mount slave drive on slackware 12

anotherpenguin · 11-18-2008, 10:15 PM

I recently added a slave drive but my slackware 12 doesn't recognize it,
My bios shows the drive.

okos · 11-18-2008, 10:33 PM

What do you get with

su
fdisk -l

Do can you see the device? /dev/hdc or /dev/sdc (or something similar)
How is the disk formatted? ntfs?
If ntfs, you need fuse and ntfs-3g

anotherpenguin · 11-18-2008, 10:43 PM

root@darkstar:/home/natsume# fdisk -l

Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 3538 28418953+ 83 Linux
/dev/hda2 3539 4632 8787555 5 Extended
/dev/hda3 4633 4870 1911735 82 Linux swap
/dev/hda5 3539 4632 8787523+ b W95 FAT32

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2550 20482843+ c W95 FAT32 (LBA)
/dev/sda2 2551 9729 57665317+ f W95 Ext'd (LBA)
/dev/sda5 2551 6374 30716248+ b W95 FAT32
/dev/sda6 6375 9729 26949006 b W95 FAT32

I should be getting hdc
I don't know how the disk is formatted, it is either FAT32 or NTFS.

okos · 11-19-2008, 09:09 PM

Quote:

Originally Posted by anotherpenguin

root@darkstar:/home/natsume# fdisk -l

Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 3538 28418953+ 83 Linux
/dev/hda2 3539 4632 8787555 5 Extended
/dev/hda3 4633 4870 1911735 82 Linux swap
/dev/hda5 3539 4632 8787523+ b W95 FAT32

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2550 20482843+ c W95 FAT32 (LBA)
/dev/sda2 2551 9729 57665317+ f W95 Ext'd (LBA)
/dev/sda5 2551 6374 30716248+ b W95 FAT32
/dev/sda6 6375 9729 26949006 b W95 FAT32

I should be getting hdc
I don't know how the disk is formatted, it is either FAT32 or NTFS.

hda is your master hdd and you did not show anything formatted in ntfs.

Your slave hdd is sda formatted in fat32 with four partitions.
The /dev/sda is the device recognized by linux. I don't know what (LBA) stands for.

The default mount point is /media for slackware, however you can put the mount point anywhere of your choosing. I personally put the mount point for a usb hdd in my home directory. I did that because every time I open a console, the default directory is my home directory. It gives easier access to the usb drive. The mount point is the file you create where you will access all of the files on the 2nd drive.

Two things you will need to do.

1. Create four mount points. Make four directories and name them as you choose and where you choose. I named one of mine as "backup" etc ....
Next mount the partition

su
mount /dev/sda1 /location/of/your/mount/point/
cd /location/of/your/mount/point/ (You should be able to now access all of the files for the first partition on the slave drive.)
Now do the same for the other three parititions.

2. You will need to edit your /etc/fstab file so you will be mounted everytime you boot.

I suggest to add something like this. Edit it to meet your needs.
/dev/sda2 /backup vfat auto,users,exec,rw,sync 1 0

yzhong · 11-19-2008, 09:38 PM

1.LBA is Logical block addressing.Before LBA, hard drives could encounter a 1024-cylinder limit, where the BIOS could not find a file after that point, such as a boot loader or kernel files.
2.After you do as Okos said, you can type in "mount" or "more /etc/mtab" to double check the result.

okos · 11-20-2008, 10:03 PM

Quote:

Originally Posted by yzhong

1.LBA is Logical block addressing.Before LBA, hard drives could encounter a 1024-cylinder limit, where the BIOS could not find a file after that point, such as a boot loader or kernel files.

Thanks for the lesson. I just learned something new

Perhaps the best thing would be to reformat the disk with smaller partitions so that the bios will would recognize each partition in full?

anotherpenguin · 11-28-2008, 11:06 AM

My IDE connector was faulty, crap.
I wasted so much time on this.
Thanks for your help guys

onebuck · 11-28-2008, 11:25 AM

Hi,

Quote:

Originally Posted by okos

hda is your master hdd and you did not show anything formatted in ntfs.

Your slave hdd is sda formatted in fat32 with four partitions.
The /dev/sda is the device recognized by linux. I don't know what (LBA) stands for.

The default mount point is /media for slackware, however you can put the mount point anywhere of your choosing. I personally put the mount point for a usb hdd in my home directory. I did that because every time I open a console, the default directory is my home directory. It gives easier access to the usb drive. The mount point is the file you create where you will access all of the files on the 2nd drive.

The '/dev/hda' is the master on ide0. If the slave is on ide0 then the device would be 'dev/hdb'. If the device master on ide1 then the slave would be '/dev/hdd'.

'LBA' faults can be corrected by placing 'lba32' in your lilo.conf file.

Too expand; the mount point is a directory that you create on the filesystem to mount the filesystem;

Code:

excerpt from 'man mount';
NAME
       mount - mount a file system

SYNOPSIS
       mount [-lhV]

       mount -a [-fFnrsvw] [-t vfstype] [-O optlist]
       mount [-fnrsvw] [-o options [,...]] device | dir
       mount [-fnrsvw] [-t vfstype] [-o options] device dir

DESCRIPTION
       All files accessible in a Unix system are arranged in one big tree, the
       file hierarchy, rooted at /.  These files can be spread out  over  sev-
       eral  devices. The mount command serves to attach the file system found
       on some device to the big file tree. Conversely, the umount(8)  command
       will detach it again.

       The standard form of the mount command, is
              mount -t type device dir
       This  tells the kernel to attach the file system found on device (which
       is of type type) at the directory dir.  The previous contents (if  any)
       and  owner  and  mode of dir become invisible, and as long as this file
  system remains mounted, the pathname dir refers to the root of the file
       system on device.

Code:

~# ls -al /mnt
total 56
drwxr-xr-x 13 root root 4096 2008-05-11 12:24 ./
drwxr-xr-x 21 root root 4096 2008-09-14 17:44 ../
-rw-r--r--  1 root root  376 2006-09-25 22:09 README
drwxr-xr-x  2 root root 4096 2006-09-25 20:02 cdrecorder/
drwxr-xr-x  2 root root 4096 2002-03-16 01:34 cdrom/
drwxr-xr-x  2 root root 4096 2006-09-25 20:02 dvd/
drwxr-xr-x  2 root root 4096 2002-03-16 01:34 floppy/
drwxr-xr-x  2 root root 4096 2002-03-16 01:34 hd/
drwxr-xr-x  2 root root 4096 2006-09-25 20:02 memory/
drwxr-xr-x  2 root root 4096 2008-05-11 12:24 sda/
drwxr-xr-x  2 root root 4096 2008-05-11 12:22 sda11/
drwxr-xr-x  2 root root 4096 2006-09-25 20:03 tmp/
drwxrwxrwx  1 root root 4096 2008-05-01 19:02 winxp/
drwxr-xr-x  2 root root 4096 2006-09-25 20:02 zip/

I would read the 'man mount'.