| stress_junkie |
04-12-2007 07:16 AM |
Use the fdisk utility with the -l parameter to ensure that the disk is organized the way that you think that it is.
Code:
fdisk -l /dev/hda
Disk /dev/hda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 1094 8787523+ 7 HPFS/NTFS
/dev/hda2 1095 1155 489982+ 82 Linux swap / Solaris
/dev/hda3 * 1156 2249 8787555 83 Linux
/dev/hda4 2250 30401 226130940 5 Extended
/dev/hda5 2250 3343 8787523+ 83 Linux
/dev/hda6 3344 4437 8787523+ 83 Linux
/dev/hda7 4438 11732 58597056 83 Linux
/dev/hda8 11733 19027 58597056 83 Linux
/dev/hda9 19028 30401 91361623+ 83 Linux
Post the results here.
Also, ensure that the mount points that you have put in /etc/fstab actually exist.
Code:
ls /mnt
backup hda1 hda5 hda8 hdb1 hdd2 hdd6 hdd8 sda2 win_c
cdrom hda3 hda7 hda9 hdd10 hdd5 hdd7 hdd9 tmp win_d
Then make sure that the partitions have a file system and that it is the type that you think it is. You can use the mount command to check this. Log in as root and try to mount the partitions manually. If you get an error message that says that you need to specify the file system type then either you have a different type of file system on the partition or there isn't any file system at all on that partition.
Code:
mount /dev/hda9 /mnt/hda9
mount: you must specify the filesystem type
The reason that this happened on my computer is that /dev/hda9 is an encrypted partition so the mount utility doesn't see a valid file system. This can also happen there is no file system at all or if you have put the wrong file system type in /etc/fstab for that partition.
The ext3 partitions can also be tested using the tune2fs utility.
Code:
tune2fs -l /dev/hda6
tune2fs 1.39 (29-May-2006)
Filesystem volume name: pclos
Last mounted on: <not available>
Filesystem UUID: cfd79796-14ea-4127-a75f-5de1541f5902
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 1098880
Block count: 2196880
Reserved block count: 109844
Free blocks: 1461461
Free inodes: 968776
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 536
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16160
Inode blocks per group: 505
Filesystem created: Mon Jan 8 21:27:14 2007
Last mount time: Wed Apr 11 11:03:46 2007
Last write time: Wed Apr 11 11:03:46 2007
Mount count: 66
Maximum mount count: -1
Last checked: Mon Jan 8 21:27:14 2007
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
First orphan inode: 533585
Default directory hash: tea
Directory Hash Seed: 9bc5f881-861b-4b11-a925-78aac3258e23
Journal backup: inode blocks
Let us know the results. :) |
