Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Hardware
User Name
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?


  Search this Thread
Old 12-03-2007, 02:47 PM   #1
LQ Newbie
Registered: Dec 2007
Posts: 12

Rep: Reputation: 0
Unable to mount SATA drives on boot

I have an ASUS P5RD1-V motherboard which has the ALI/ULI SATA RAID chipset.

I'd been running RedHat AS3 on it for some time, using a single IDE (PATA) drive. For a futer project, I need to populate out the SATA drives to provide additional storage space.

I originally upgraded to RedHat AS4.6 in order to get the SATA drivers, but was never able to get the a true hardware driver to work, so I backed out all the driver changes for that. Don't want the software RAID, so eventually decided to use them as straight disks. Turned off the hardware RAID in the bios so that the system would treat them as individual drives.

Now comes the fun part: Redhat sees all four drives as /dev/sda, /dev/sdb, etc. I am able to partition the drives (one big 500MB part), format them, label them, mount them manually, etc.

However, when I add them to /etc/fstab, I can't seem to boot the system. If I add them as "LABEL=xxx" entries, then fsck.ext3 cannot find them by their label names. If I add them as device entries (/dev/sda1 /mount01...) then the fsck of the boot partition fails misserably. In both cases I'm allowed to enter single-user state, at which point I can mount the drives manually, etc.

What's missing? Why will a standard entry not work?
Old 12-03-2007, 03:15 PM   #2
Registered: Nov 2007
Location: New Orleans, LA, USA
Distribution: Xubuntu
Posts: 67

Rep: Reputation: 6
What do /var/log/syslog, /var/log/messages & /var/log/boot say? (These are Debian names. RHAS log files might be named slightly different.)

Also, is the SATA driver a module or linked directly in?
Old 12-04-2007, 11:51 AM   #3
LQ Newbie
Registered: Dec 2007
Posts: 12

Original Poster
Rep: Reputation: 0
Logs show no problems

The logs all show no problems up to that point.
The SATA driver is a module and the logs show that the driver is loaded and all the drives are recognized and setup as devices by the time it gets to the error.
The really interesting thing is, after I login to the single-user maintenance shell, I can re-issue the exact fsck command being used by the rc.sysinit script, and it runs perfectly.
Old 12-04-2007, 04:20 PM   #4
Registered: Mar 2007
Location: North Carolina
Distribution: Slackware 12.0, Gentoo, LFS, Debian, Kubuntu.
Posts: 906

Rep: Reputation: 38
Musical Drives.

Might want to check and see what udev is naming them. They may not be getting named the same every boot causing the hang. Here is a good link if that is the problem

Last edited by Hern_28; 12-04-2007 at 04:21 PM. Reason: typo
Old 12-05-2007, 11:46 AM   #5
LQ Newbie
Registered: Dec 2007
Posts: 12

Original Poster
Rep: Reputation: 0
Might have something.....

Nope, it's not musical disk drives. They are being assigned the same major/minor numbers on each boot.

I do have it working, but it involved adding
/bin/sleep 10
just prior to the code with does the fsck and mounts. Looks like the driver is taking it's sweet time initiallizing.

Could it be related to the fact the the module is loaded twice?
Kmodule lists the sata_uli driver as OTHER/RAID depending on whether or not I have the hardware RAID bios enable. In either case, rc.sysinit puts "sata_uli" in the $other module list when processing the output from kmodule.

However, the files modules.conf and modprobe.conf both have the line
alias scsi_hostadapter sata_uli
in them, so the output of "modprobe -c" called in rc.sysinit ends up adding the sata_uli module to the $scsi list. Then when rc.sysinit starts loading modules, it loads it twice, once when it processes the $scsi list and once when it processes the $other list.

Should I just remove the alias from the modprobe.conf file? Would that cause any problems? It doesn't look like it should.
Old 12-05-2007, 11:56 AM   #6
LQ Newbie
Registered: Dec 2007
Posts: 12

Original Poster
Rep: Reputation: 0
just a slow module load????

Well, imperical testing shows that the double load of the sata_uli module is not the problem. It's just a slow init sequence. For some reason, the extra 10 second wait is needed before the operating system can see the labels on the drives. Anyone know what causes the read and if there is a way to speed it up?


asus, driver, mount, sata

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
2 hard drives, XP on my main sata drives, 10.2 on my IDE LILO doesnt show on boot up Dachy Slackware 14 01-03-2008 07:01 AM
Fedora Core 3 unable to find SATA hard drives Denali03 Linux - Newbie 1 03-17-2005 08:14 PM
NFTS sata raid drives - won't mount jamangold Linux - Newbie 0 07-25-2004 06:57 PM
Mount SATA RAID drives in debian? EcceVery Debian 8 05-12-2004 04:24 PM
cannot mount SATA drives manub Red Hat 0 03-13-2004 09:44 AM > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 06:34 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration