LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 03-10-2009, 02:59 AM   #1
Rollo69
Member
 
Registered: Sep 2005
Location: Charlotte, NC
Distribution: Slack 12.0
Posts: 190

Rep: Reputation: 30
Problem with sata drive


I've read a few post about sata problems and they have helped but not solved my problem. I have enabled sata in bios and recompiled my kernel so my sata controller is built into kernel. I'm running kernel 2.6.22.2 and Slack 10.2 . I'm unable to access the sata drive. I have partitioned the drive and put Slack 12.0 on half of it. The drive is 500 GB and partitioned using ext3.

Here's some more info:
Code:
~$ dmesg | grep ata
 BIOS-e820: 0000000037ef3000 - 0000000037f00000 (ACPI data)
Kernel command line: BOOT_IMAGE=Slack_sata ro root=301 boot=/dev/hda1
Memory: 902428k/916416k available (2919k kernel code, 13528k reserved, 1599k data, 292k init, 0k highmem)
      .data : 0xc03d9e63 - 0xc0569dac   (1599 kB)
libata version 2.21 loaded.
sata_via 0000:00:0f.0: version 2.2
sata_via 0000:00:0f.0: routed to hard irq line 11
scsi0 : sata_via
scsi1 : sata_via
ata1: SATA max UDMA/133 cmd 0x0001ff00 ctl 0x0001fe02 bmdma 0x0001fb00 irq 18
ata2: SATA max UDMA/133 cmd 0x0001fd00 ctl 0x0001fc02 bmdma 0x0001fb08 irq 18
ata1: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-7: WL500GSA1672, 07.02E07, max UDMA/133
ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata2.00: configured for UDMA/133
ReiserFS: hda1: using ordered data mode
ReiserFS: hda3: using ordered data mode
ReiserFS: hda4: using ordered data mode
Code:
~$ cat /etc/fstab
/dev/hda2        swap         swap        defaults         0   0
/dev/hda1        /            reiserfs    defaults         1   1
/dev/hda3        /usr         reiserfs    defaults         1   2
/dev/hda4        /var         reiserfs    defaults         1   2
/dev/sda2        /mnt/sata  ext3   users,auto,rw,defaults,umask=000  0  0
/dev/sdb         /mnt/usb    vfat   users,auto,rw,exec,umask=000 0  0
/dev/sdb1        /mnt/usb1    vfat   users,auto,rw,exec,umask=000 0  0
/dev/cdrw        /mnt/cdrw     auto        noauto,users,rw  0   0
/dev/dvd         /mnt/dvd       auto        noauto,users,ro  0   0
/dev/fd0         /mnt/floppy    auto        noauto,users     0   0
devpts           /dev/pts       devpts      gid=5,mode=620   0   0
proc             /proc          proc        defaults         0   0
Code:
/mnt$ ls -l
total 0
drwxrwxrwx  2 root users 48 2007-03-31 18:23 cdrw
drwxr-xr-x  2 root users 48 2007-05-19 11:34 dvd
drwxrwxrwx  2 root users 48 2002-03-16 02:34 floppy
drwxr-xr-x  2 root root  48 2002-03-16 02:34 hd
drwxrwxrwx  2 root users 48 2007-04-09 00:29 matrix
drwxrw-rw-  2 root users 48 2009-03-09 00:08 sata
drwxrwxrwx  2 root users 48 2008-11-23 02:56 usb
drwxrwxrwx  2 root users 48 2008-12-18 08:36 usb1
Code:
# lspci
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0336
00:00.1 Host bridge: VIA Technologies, Inc.: Unknown device 1336
00:00.2 Host bridge: VIA Technologies, Inc.: Unknown device 2336
00:00.3 Host bridge: VIA Technologies, Inc.: Unknown device 3336
00:00.4 Host bridge: VIA Technologies, Inc.: Unknown device 4336
00:00.5 PIC: VIA Technologies, Inc.: Unknown device 5336
00:00.7 Host bridge: VIA Technologies, Inc.: Unknown device 7336
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:02.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller
00:03.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller
00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge
00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
00:13.0 Host bridge: VIA Technologies, Inc. VT8237A PCI to PCIE Bridge
00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: VIA Technologies, Inc.: Unknown device 3230 (rev 11)
80:01.0 Class 0403: VIA Technologies, Inc. VIA High Definition Audio Controller (rev 10)
I'm not sure if I used the correct code in fstab for the drive. I based it on earlier fstab I had for dual booting window$.
I've tried to mount the drive and get an error about wrong fs type. I would like for it to mount when I boot up.

Any help would be appreciated.
Thanks in advance.

Last edited by Rollo69; 03-10-2009 at 03:03 AM.
 
Old 03-10-2009, 04:14 AM   #2
Linux.tar.gz
Senior Member
 
Registered: Dec 2003
Location: Paris
Distribution: Slackware forever.
Posts: 2,116

Rep: Reputation: 84
Did you tried "mount /dev/sda2 /mnt/sata " as root ?
And i'm not sure umask option is usable with ext3.
 
Old 03-10-2009, 04:38 AM   #3
ddaemonunics
Member
 
Registered: May 2008
Location: Romania
Distribution: Debian
Posts: 242

Rep: Reputation: 41
run fdisk -l and post the summary here
also
cat /proc/partitions
 
Old 03-10-2009, 05:38 AM   #4
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Pclinux, Mandriva, Kubuntu 10.10 Slck13_64-current
Posts: 2,005
Blog Entries: 3

Rep: Reputation: 112Reputation: 112
edit your /etc/fstab file to this .
Quote:
/dev/sda2 /mnt/sata ext3 defaults 0 0
now it will mount at boot and any user with disk in there group can access it. make sure the folder name sata exists in /mnt/sata <---

Last edited by Drakeo; 03-10-2009 at 05:40 AM.
 
Old 03-10-2009, 12:23 PM   #5
arniekat
LQ Newbie
 
Registered: Oct 2008
Location: San Diego, CA
Distribution: Slackware 13.37, Linux Mint 11
Posts: 18
Blog Entries: 37

Rep: Reputation: 4
Try passing the following boot-time option in lilo:
hda=noprobe
This will force the kernel to look for another hard drive controller and (hopefully) find the SATA drive as an sda# using your libata. You can also tell the kernel to use a specific library. For this, in lilo:
hda=noprobe libata.atapi_enabled=1
 
Old 03-10-2009, 07:28 PM   #6
Rollo69
Member
 
Registered: Sep 2005
Location: Charlotte, NC
Distribution: Slack 12.0
Posts: 190

Original Poster
Rep: Reputation: 30
I would like to say thank you to you guys for your responces. I will attempt to answer what I can now, but I am a work and not in front of the pc.

Quote:
Originally Posted by Linux.tar.gz View Post
Did you tried "mount /dev/sda2 /mnt/sata " as root ?
And i'm not sure umask option is usable with ext3.
Yes I did try as root the way you asked and with "mount -t ext3 /dev/sda2 /mnt/sata" but didn't work. I tried those commands using sudo and as user but all failed.
Quote:
Originally Posted by ddaemonunics View Post
run fdisk -l and post the summary here
also
cat /proc/partitions
I will get these for you once I'm in front of the computer. I did run fdisk -l as user and it only shows hda# if memory serves me well.
Quote:
Originally Posted by Drakeo View Post
edit your /etc/fstab file to this .
Quote:
/dev/sda2 /mnt/sata ext3 defaults 0 0

now it will mount at boot and any user with disk in there group can access it. make sure the folder name sata exists in /mnt/sata <---
I will adjust the fstab accordingly and I did create the /mnt/sata directory,
Code:
/mnt$ ls -l
drwxrw-rw-  2 root users 48 2009-03-09 00:08 sata
Quote:
Originally Posted by arniekat View Post
Try passing the following boot-time option in lilo:
hda=noprobe
This will force the kernel to look for another hard drive controller and (hopefully) find the SATA drive as an sda# using your libata. You can also tell the kernel to use a specific library. For this, in lilo:
hda=noprobe libata.atapi_enabled=1
I'll give it a shot.

Again thanks for you info and help. I will get back to you after work.
 
Old 03-11-2009, 12:37 AM   #7
Rollo69
Member
 
Registered: Sep 2005
Location: Charlotte, NC
Distribution: Slack 12.0
Posts: 190

Original Poster
Rep: Reputation: 30
Here's the info you asked for Ddaemonunics
Code:
# fdisk -l
Disk /dev/hda: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1         243     1951866   83  Linux
/dev/hda2             244         267      192780   82  Linux swap
/dev/hda3             268        4755    36049860   83  Linux
/dev/hda4            4756        4998     1951897+  83  Linux
Code:
# cat /proc/partitions
major minor  #blocks  name

   3     0   40146624 hda
   3     1    1951866 hda1
   3     2     192780 hda2
   3     3   36049860 hda3
   3     4    1951897 hda4
   8     0  488386584 sda
   8     1    4883728 sda1
   8     2     498015 sda2
   8     3  239256045 sda3
   8     4  243746212 sda4
Drakeo:
I have changed my fstab to match what you typed and I will see how it does after reboot.
 
Old 03-12-2009, 12:44 AM   #8
Rollo69
Member
 
Registered: Sep 2005
Location: Charlotte, NC
Distribution: Slack 12.0
Posts: 190

Original Poster
Rep: Reputation: 30
Solved sata issue

Well I am now able to mount/see my sata drive. I have 4 partitions on the sata drive. 1st partition is root (/) and 2nd is the swap. 3rd is /usr and 4th is partitioned for storage/backup/compiling/etc.

Well I changed my permissions for the sata directory. It was 766 now it's 777. I also changed my fstab as follows.
Code:
/dev/sda4        /mnt/sata        ext3    users,rw,defaults    0   0
I can now mount the 4th partition as user and shows up when I use fdisk -l as root. I'm not sure about the auto mounting from boot up yet, but will let you know if it does.

Maybe this will help someone else. Any way thanks guys for the help.
 
Old 03-12-2009, 02:47 AM   #9
Rollo69
Member
 
Registered: Sep 2005
Location: Charlotte, NC
Distribution: Slack 12.0
Posts: 190

Original Poster
Rep: Reputation: 30
After rebooting the drive mounted automatically.
 
  


Reply


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Sata Raid 1 and Single Sata drive drive order issue Kvetch Linux - Hardware 5 03-19-2007 06:50 PM
Installation problem in SATA drive shunmugaprasath Fedora 2 01-07-2007 08:19 AM
Problem with SATA drive SlackTRAXX Linux - Hardware 2 04-20-2006 10:02 PM
PCI-Sata drive problem xhatex Linux - Hardware 3 10-13-2005 09:01 PM
Sata Drive Problem linux_secret Linux - Hardware 1 07-28-2005 09:45 AM


All times are GMT -5. The time now is 09:54 AM.

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
Open Source Consulting | Domain Registration