LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
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?

Notices

Reply
 
Search this Thread
Old 12-10-2006, 05:47 PM   #1
rsriprac
LQ Newbie
 
Registered: Dec 2006
Posts: 3

Rep: Reputation: 0
Unhappy Unable to access PATA drive after reboot


Hello,

I have been having a problem with getting access to a drive I installed. My motherboard is a Asus PC-DL Deluxe and it comes with an onboard Promise 378 RAID controller. Kernel version is 2.6.18 flavor Fedora 6. I am not setting it to any RAID but just using it to connect to additional hard drive.

The drive shows up fine under sda. I was able to partition it with fdisk:

Code:
Disk /dev/sda: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       19929   160079692   83  Linux
And I was successful in mounting it to /mnt/sda1. I am able to write to the drive without any problems. So I edited the /etc/fstab file and added:

Code:
/dev/sda1               /mnt/sda1               ext3    defaults        0 0
After I rebooted the drive does not mount and I can not mount it manually:

Code:
$ sudo mount -v /dev/sda1 /mnt/sda1 -t ext3
mount: /dev/sda1 is not a valid block device
Here is my dmsg:


Code:
SCSI subsystem initialized
libata version 2.00 loaded.
sata_promise 0000:03:04.0: version 1.04
ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 23 (level, low) -> IRQ 193
sata_promise PATA port found
ata1: SATA max UDMA/133 cmd 0xF0836200 ctl 0xF0836238 bmdma 0x0 irq 193
ata2: SATA max UDMA/133 cmd 0xF0836280 ctl 0xF08362B8 bmdma 0x0 irq 193
ata3: PATA max UDMA/133 cmd 0xF0836300 ctl 0xF0836338 bmdma 0x0 irq 193
scsi0 : sata_promise
ata1: SATA link down (SStatus 0 SControl 0)
scsi1 : sata_promise
ata2: SATA link down (SStatus 0 SControl 300)
scsi2 : sata_promise
ata3.00: ATA-7, max UDMA/133, 320173056 sectors: LBA48 
ata3.00: ata3: dev 0 multi count 0
ata3.00: configured for UDMA/133
  Vendor: ATA       Model: Maxtor 4R160L4    Rev: RAMB
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1
sd 2:0:0:0: Attached scsi disk sda
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
device-mapper: multipath: version 1.0.4 loaded
device-mapper: multipath round-robin: version 1.0.0 loaded
device-mapper: table: 253:0: multipath: error getting device
device-mapper: ioctl: error adding target to table
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
audit(1165767520.088:2): enforcing=1 old_enforcing=0 auid=4294967295
security:  3 users, 6 roles, 1560 types, 166 bools, 1 sens, 1024 cats
security:  58 classes, 48173 rules
sd 2:0:0:0: Attached scsi disk sda
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
device-mapper: multipath: version 1.0.4 loaded
device-mapper: multipath round-robin: version 1.0.0 loaded
device-mapper: table: 253:0: multipath: error getting device
device-mapper: ioctl: error adding target to table
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
audit(1165767520.088:2): enforcing=1 old_enforcing=0 auid=4294967295
security:  3 users, 6 roles, 1560 types, 166 bools, 1 sens, 1024 cats
security:  58 classes, 48173 rules
SELinux:  Completing initialization.
SELinux:  Setting up existing superblocks.
SELinux: initialized (dev dm-0, type ext3), uses xattr
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
SELinux: initialized (dev devpts, type devpts), uses transition SIDs
SELinux: initialized (dev eventpollfs, type eventpollfs), uses task SIDs
SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
SELinux: initialized (dev cpuset, type cpuset), not configured for labeling
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
audit(1165767520.444:3): policy loaded auid=4294967295

Last edited by rsriprac; 12-10-2006 at 05:52 PM.
 
Old 12-10-2006, 06:18 PM   #2
Brian1
Guru
 
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that. Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700

Rep: Reputation: 61
Run the command as root to see what it sees. ' fdisk -l '

Brian
 
Old 12-11-2006, 02:49 AM   #3
rsriprac
LQ Newbie
 
Registered: Dec 2006
Posts: 3

Original Poster
Rep: Reputation: 0
Here is what I get:

Code:
sudo fdisk -l

Disk /dev/hda: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1          13      104391   83  Linux
/dev/hda2              14       14946   119949322+  8e  Linux LVM

Disk /dev/hdc: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1   *           1       19929   160079661   8e  Linux LVM

Disk /dev/hdd: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdd1   *           1       19929   160079661   8e  Linux LVM

Disk /dev/sda: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       19929   160079661   8e  Linux LVM
 
Old 12-11-2006, 02:59 PM   #4
Brian1
Guru
 
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that. Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700

Rep: Reputation: 61
/dev/sda1 is an LVM partition. Not a real ext2/3 or similiar filesystem type partition. You need to use LVM commands to add to your LVM and partition out of that. Compare the line for /dev/dha1 for correct fstab setup. Once partition is mounted then you need to create a logical volume in it or attach it to an exsiting Logical Volume. Not a fan of LVM so not much help on the commands to use LVM.

Brian
 
Old 12-12-2006, 12:15 AM   #5
rsriprac
LQ Newbie
 
Registered: Dec 2006
Posts: 3

Original Poster
Rep: Reputation: 0
Hello. I've reformatted it to a regular Linux ext3 and I have the same problem. Once I reboot I can not access the drive (i.e. mount it).


Code:
sudo fdisk -l
Password:

Disk /dev/hda: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1          13      104391   83  Linux
/dev/hda2              14       14946   119949322+  8e  Linux LVM

Disk /dev/hdb: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdb1               1       19929   160079661   83  Linux

Disk /dev/hdc: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1   *           1       19929   160079661   8e  Linux LVM

Disk /dev/hdd: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdd1   *           1       19929   160079661   8e  Linux LVM

Disk /dev/sda: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       19929   160079661   83  Linux
 
Old 12-12-2006, 04:13 PM   #6
Brian1
Guru
 
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that. Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700

Rep: Reputation: 61
Lets run through all the steps.
1. repartitioned the drive and set drive type. Saved and exited fdisk
2. Formatted the drive as ext2 or ext3.
3. The mount point directory /mnt/sda1 exist.
4. running the command ' mount -t ext3 /dev/sda1 /mnt/sda1 '. Does it work?
If it does not mount I am not sure what is missing. I would think since fdisk can see it then the sata module for it is loaded.

I will give it a thought over the next few days.
Brian
 
Old 12-12-2006, 06:52 PM   #7
kilgoretrout
Senior Member
 
Registered: Oct 2003
Posts: 2,298

Rep: Reputation: 138Reputation: 138
Can you also post the output of:

$ cat /proc/partitions

See if sda and sda1 are showing up there.
 
Old 12-19-2006, 02:49 PM   #8
AzCoder
LQ Newbie
 
Registered: Nov 2004
Location: Prescott, AZ
Distribution: Fedora, Ubuntu, CentOS, Suse
Posts: 6

Rep: Reputation: 0
Me Too

I have a K8V-SE Deluxe motherboard with the same Promise controller. I have two PATA drives connected. I was able to see them correctly under FC5. I upgraded to FC6 and I could no longer mount either drive (sda & sdb). sda has sda1 & sda2 ntfs file systems and sdb has sdb1 & sdb2 ext3 partitions and sdb3 has a swap partition. The kernel sees them on boot and fdisk -l sees them, but they can not be mounted. I always get the error "mount: /dev/xxxx is not a valid block device". I wiped out my update and did a new install of fc6, still get the same problem. I applied all the updates and still get the same error! Where can I go from here?

BTW, I have Rawhide installed on another identical machine, and it sees all of the partitions and they all can be mounted!!!
 
Old 12-19-2006, 05:12 PM   #9
White Fang
LQ Newbie
 
Registered: Dec 2006
Posts: 2

Rep: Reputation: 0
Fedora Core 6 and sata_promise

There seem to be major issues with the sata_promise driver implemented in the fedora core 6 distribution. It could be this driver at work here since the errors you report are far from standard. There are several threads on the fedora support forum, please take a look at these since there is a solution to most sata_promise driver screw-ups there.

see:
1. http://www.fedoraforum.org/forum/sho...d.php?t=128298

2. http://forums.fedoraforum.org/showthread.php?t=133481


Hope this solves the problem...
 
  


Reply

Tags
mount, pata, reboot


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
Unable to Access USB DVD Drive in FC5 bdprem Fedora 2 10-11-2006 12:47 PM
unable to access my LS-120 drive using kernel 2.4.26 malbaugh MEPIS 2 12-10-2005 11:30 AM
Unable to access Win 98 or C Drive mrbenn Linux - Newbie 11 04-13-2004 04:20 AM
unable to access scsi drive Homzz Slackware 1 04-12-2004 08:36 PM
Red Hat 8.0 - unable to access SCCI drive Conor Long Linux - Distributions 13 07-02-2003 04:19 PM


All times are GMT -5. The time now is 03:43 PM.

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