Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Suse 9.2 and SATA drives
#1

How can I use my SATA drives under Suse 9.2 ? Suse finds all other IDE drives without any problem, but I am missing 2 drives. I have winXP on 1 IDE drive and Suse on another IDE drive. Suse only see itself and another IDE drive (not the XP). Any suggestions?

 

tia, kryppe

Reply
#2

what does fdisk -l report ?

 



Code:
fdisk -l




 

thats a l as in LARRY

 

cheers

 

anyweb

Reply
#3

This is what I get from fdisk-l

 



Code:
Disk /dev/hdc: 46.1 GB, 46115758080 bytes
255 heads, 63 sectors/track, 5606 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks   Id  System
/dev/hdc1               1         131     1052226   82  Linux swap / Solaris
/dev/hdc2             132        5606    43977937+  83  Linux

Disk /dev/hdd: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks   Id  System
/dev/hdd1   *           1       19457   156288321    7  HPFS/NTFS
linux:/sbin #




Reply
#4

theres your winxp drive

 

/dev/hdd1 * 1 19457 156288321 7 HPFS/NTFS

 

check if you have any NTFS kernel module loaded, if not, go get one or you won't be able to read the NTFS drive above

 

cheers

 

anyweb

Reply
#5

Not sure how to check for a NTFS kernel module, but I can access the /dev/hdd1 whitout problems, so I guess I have a working NTFS kernel module. It is not the drive with XP installed though and it is a IDE drive. Im currently missing 2 SATA drives, 1x120 gb and 1x160gb, and they are all NTFS

 

tia, kryppe

Reply
#6

ah ok then, well are they in a raid setup or something similar ? can you boot into windows and take a screenshot of 'disk administrator' (right click on my computer/choose manage/disak administration)

 

cheers

 

anyweb

Reply
#7

ah ok then, well are they in a raid setup or something similar ? can you boot into windows and take a screenshot of 'disk administrator' (right click on my computer/choose manage/disak administration)

 

cheers

 

anyweb

Reply
#8

The disks arent setup in RAID, however my mobo , EPoX EP-8KDA3+ Socket 754

nForce3 250GB, does have the option. All drives are used as "normal" , no RAID setup that is. Hope this helps.

 

tia, kryppe

<a class="ipsAttachLink ipsAttachLink_image" href="<fileStore.core_Attachment>/post-54-1104425094.jpg" data-fileid="245">[img]<fileStore.core_Attachment>/post-54-1104425094.jpg[/img]</a>



Attached Files
.jpg   diskmanagement.JPG (Size: 104.8 KB / Downloads: 0)
Reply
#9

Also found this under /var/log/boot.msg , not sure if it can help :/

 



Code:
<7>sata_nv version 0.03
<6>ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 11 (level, low) -> IRQ 11
<7>PCI: Setting latency timer of device 0000:00:0a.0 to 64
<6>ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD800 irq 11
<6>ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD808 irq 11
<4>nv_sata: Primary device added
<4>ata1 is slow to respond, please be patient
<3>ata1 failed to respond (30 secs)
<6>scsi0 : sata_nv
<4>nv_sata: Secondary device added
<4>ata2 is slow to respond, please be patient
<3>ata2 failed to respond (30 secs)
<6>scsi1 : sata_nv
<7>sata_sil version 0.54
<6>ACPI: PCI interrupt 0000:02:0c.0[A] -> GSI 5 (level, low) -> IRQ 5
<6>ata3: SATA max UDMA/100 cmd 0xF8804080 ctl 0xF880408A bmdma 0xF8804000 irq 5
<6>ata4: SATA max UDMA/100 cmd 0xF88040C0 ctl 0xF88040CA bmdma 0xF8804008 irq 5
<6>ata5: SATA max UDMA/100 cmd 0xF8804280 ctl 0xF880428A bmdma 0xF8804200 irq 5
<6>ata6: SATA max UDMA/100 cmd 0xF88042C0 ctl 0xF88042CA bmdma 0xF8804208 irq 5
<6>ata3: no device found (phy stat 00000000)
<6>scsi2 : sata_sil
<6>ata4: no device found (phy stat 00000000)
<6>scsi3 : sata_sil
<6>ata5: no device found (phy stat 00000000)
<6>scsi4 : sata_sil
<6>ata6: no device found (phy stat 00000000)
<6>scsi5 : sata_sil




 

tia, kryppe

Reply
#10

A solution has been found :)

 

After a suggestion that got me thinking, I moved the sata disks to another chipset on my mobo (having 2 different chipsets...) The disks where now recognized by suse and I had to make the following corrections on my system:

 

In my /etc/fstab file, I added :

 

/dev/sda5 /windows/D ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0

/dev/sdb1 /windows/E ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0

 

And also made sure there where the following directories under /windows/ :

 

mkdir /windows/D

mkdir /windows/E

 

 

and Im back :)

Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)