Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello all. Having a problem with an external HD on an FC2 system.
I have two partitions on the external HD - sda1 and sda2. I have the proper entries in /etc/fstab so that both partitions should mount automatically at boot - I know this because once booted up, I can mount them by doing a sudo mount -a.
HOWEVER, during the boot process, the partitions won't mount. I get error messages for each saying "not a valid block device."
Since there are no replies, I figured I'd update this a bit.
Trolling the net and various forums, having used google/linux, etc., I am wondering if my computer is looking to mount the USB drive BEFORE the usb modules have loaded. Since I am not sure what to look for in dmesg, I don't know if that is my problem or if it is, how I can fix it.
Also, this is what I get when I do an fdisk -l:
[root]# fdisk -l
Disk /dev/hda: 30.0 GB, 30005821440 bytes
16 heads, 63 sectors/track, 58140 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 203 102280+ 83 Linux
/dev/hda2 204 20000 9977688 83 Linux
/dev/hda3 57166 58140 491400 82 Linux swap
/dev/hda4 20001 57165 18731160 f W95 Ext'd (LBA)
/dev/hda5 20001 57165 18731128+ 83 Linux
Partition table entries are not in disk order
Disk /dev/sda: 30.0 GB, 30020272128 bytes
255 heads, 63 sectors/track, 3649 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 2024 16257748+ c W95 FAT32 (LBA)
/dev/sda2 2025 3649 13052812+ c W95 FAT32 (LBA)
I am particularly concerned with the entry "Partition table entries are not in disk order," as well as the fact that I have hda1 through hda5 when I THOUGHT, when installing FC2, I created only /boot / and /home.
What's going on here?!?!
Can't anyone help this poor man? [Paraphrasing a line from Blazing Saddles...]
WOW! 157 views and still no replies? Is it possible that I alone have inadvertently discovered a problem that affects only me?
Surely there must be an answer! Surely some Linux Master knows the deep dark secret to unraveling these problems! But when will that superhero appear? Can they not see the signal being flashed on the clouds?
LinuxMan (or LinuxWoman), where are you in our (okay, MY) hour of need?
I am particularly concerned with the entry "Partition table entries are not in disk order," as well as the fact that I have hda1 through hda5 when I THOUGHT, when installing FC2, I created only /boot / and /home.
Looking at the output of [root]# fdisk -l it looks as though:
/dev/hda1 is /boot
/dev/hda2 is probably /
/dev/hda3 is linux swap
/dev/hda4 is your windows 95 partition
/dev/hda5 is probably /home
That seems straightforward. I do not know what the relevance of "Partition table entries are not in disk order" is, but maybe it doesn't matter as your system is booting and running from /dev/hda alright.
Your external disk is set as two partitions, /dev/sda1 and /dev/sda2. They are both formatted as FAT32.
That seems straightforward.
Why aren't they mounting at boot time?
I do not know. Maybe you should post the contents of your /etc/fstab, and take a look in /var/log/messages to see if there is anything helpful there.
Your probably right about my hda partitions, EXCEPT I don't have a Win95 partition. I think hda5 is a logical partition on hda4, but I don't know how that happened. Here is my /etc/fstab:
You are correct hda4 is an extended partition and hda5 is a logical partition that resides in hda4. An extended partition allows one to create more than 4 partitions on a disk.
Even though you have 4 linux partitions on the drive the OS is really only using 2. / and swap. I can not tell which partition / is using without see the output of the mount command (with no options). The size of hda1 would appear that it was going to be mounted as /boot.
Partitions not in order is not a big deal. I can't tell why the drive was partitioned like it is but maybe you cancelled a previous install.
You are also correct that the USB modules are not loaded when the OS tries to mount them via the fstab file.
I've never looked into to changing the boot process so I do not know how to fix the problem via that route. You can compile the USB modules into the kernel or build a new initrd with the modules included. You can always add a line in the /etc/rc.local file to mount them because this is the last boot script to run.
Other than changing the boot process, you've mentioned three possible solutions: compiling the USB modules into the kernel, building a new initrd, and adding a line to /etc/rc.local.
Not really knowing, I'd guess you listed them in decreasing order of complexity to accomplish. In your view, what are the relative costs/benefits of each option?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.