I'm putting together a new Mythbox, running 6. that has a small SCSI drive (manual install) that is up and running. I expected to add a large SATA drive to Storage groups, but I can't get it recognized as sdb or hda. If you run sda as a scsi, does this preclude another sdx as being a SATA ?

Google says: Mixed SATA/SCSI configurations are not supported under Linux.

But is this correct ? I guess I can always set it up to run from the 1TB sata. but I wanted to see if the 10k rpm scsi improved disk performance any.

I really doubt that's true. Sounds like it came from something like this link, which applies to a specific HP product (and just because HP doesn't support the configuration under Linux doesn't mean it won't work).

IIRC usb drives show up in Arch as /dev/sdX, and they obviously use a different driver than SATA hard drives, which also show up as /dev/sdX. If your SATA hard drive is not showing up, it could be many things.

Obvious but easily forgotten things - has the disk been partitioned and formatted for Linux?

Look through the output of dmesg, and see if there are any references to your hard drive or SATA controller (and post them - or just post the entire output of dmesg). That will at least let us see if your controller and disk are being detected.

Is the SATA controller integrated into the motherboard? If so, what motherboard? If not, what kind of controller?

_________________
MBE/FE: R6, P4 2.8 GHz/2 GB/2 TB, GeForce 6200 512 MB, PVR-150, Cisco RNG-100 cable box
FE: R6, P4 2.0 GHz/1 GB, GeForce4 MX 420 64 MB, diskless netboot

My linHes said it didn't have fdisk, so rather than dl it, I ran from a 'Mepis' live disk and used 'Qparted' to format ext3 (xfs wasn't an option on that software.
Only question I had, was I wrote a msdos header... didn't know if that was right but in the mepis filemanager, I was able to wrire a '/tv' folder to the volume
Kwickdisk interestingly showed the scsi as sdb and the sata as sda. Booting from the scsi shows it as sda in Linhes, and no sign of sdb [/quote]



input: AT Translated Set 2 keyboard as /class/input/input1
SCSI subsystem initialized
aic79xx 0000:0a:08.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
libata version 3.00 loaded.
pata_acpi 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
pata_acpi 0000:00:1f.1: setting latency timer to 64
pata_acpi 0000:00:1f.1: PCI INT A disabled
pata_acpi 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
pata_acpi 0000:00:1f.2: setting latency timer to 64
pata_acpi 0000:00:1f.2: PCI INT B disabled
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: forcing PORTS_IMPL to 0xf
ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 4 ports 1.5 Gbps 0xf impl IDE mode
ahci 0000:00:1f.2: flags: 64bit ncq pm led pmp slum part
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@0xd2400c00 port 0xd2400d00 irq 19
ata2: SATA max UDMA/133 abar m1024@0xd2400c00 port 0xd2400d80 irq 19
ata3: SATA max UDMA/133 abar m1024@0xd2400c00 port 0xd2400e00 irq 19
ata4: SATA max UDMA/133 abar m1024@0xd2400c00 port 0xd2400e80 irq 19
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-8: ST31000528AS, CC37, max UDMA/133
ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access ATA ST31000528AS CC37 PQ: 0 ANSI: 5
ata_piix 0000:00:1f.1: version 2.12
ata_piix 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
ata_piix 0000:00:1f.1: setting latency timer to 64
scsi5 : ata_piix
scsi6 : ata_piix
ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x2080 irq 14
ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x2088 irq 15
ata5.00: ATAPI: HL-DT-ST DVDRAM GSA-4163B, AX13, max UDMA/66
ata5.01: ATAPI: HL-DT-ST RW/DVD GCC-4482B, 1.01, max UDMA/33
ata5.00: limited to UDMA/33 due to 40-wire cable
ata5.00: configured for UDMA/33
ata5.01: configured for UDMA/33
ata6: port disabled. ignoring.
scsi 5:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-4163B AX13 PQ: 0 ANSI: 5
scsi 5:0:1:0: CD-ROM HL-DT-ST RW/DVD GCC-4482B 1.01 PQ: 0 ANSI: 5
Driver 'sd' needs updating - please use bus_type methods
sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 5:0:0:0: Attached scsi CD-ROM sr0
sr1: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
sr 5:0:1:0: Attached scsi CD-ROM sr1
scsi4 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
<Adaptec AIC7901 Ultra320 SCSI adapter>
aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66MHz, 512 SCBs
target4:0:0: asynchronous
scsi 4:0:0:0: Direct-Access IBM-ESXS PYH073W3-ETS10FN RXQL PQ: 0 ANSI: 4
scsi4:A:0:0: Tagged Queuing enabled. Depth 32
target4:0:0: Beginning Domain Validation
target4:0:0: wide asynchronous
target4:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU RDSTRM RTI WRFLOW PCOMP (6.25 ns, offset 80)
target4:0:0: Ending Domain Validation
sd 4:0:0:0: [sdb] 143374000 512-byte hardware sectors: (73.4 GB/68.3 GiB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: d3 00 10 08
sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
sd 4:0:0:0: [sdb] 143374000 512-byte hardware sectors: (73.4 GB/68.3 GiB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: d3 00 10 08
sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
sdb: sdb1 sdb2 sdb3
sd 4:0:0:0: [sdb] Attached SCSI disk
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
rtc_cmos 00:04: RTC can wake from S4




An IBM 6225 with a sub-board running scsi, and sata on the motherboard
I have a similar 6225, with the scsi removed, running one sata from the motherboard.

According to the output of your dmesg, you should have two available disks:



/dev/sda is a 1 TB disk (guessing this is your SATA)
/dev/sdb must be your SCSI disk

If that dmesg output is from Linhes, it seems like it should be working... you said when you boot from the SCSI it shows up as /dev/sda, but in your dmesg output it's listed as /dev/sdb.

Have you tried mounting by hand? i.e.,



(You may have to adjust that command). Also, I think Linhes now makes use of udev and UUIDs to permanently identify disks - it's possible for /dev/sda and /dev/sdb to be different drives at different boots. The solution is to set it up in your /etc/fstab so that the unique UUIDs are mapped to specific devices. There are other posts on the forum about doing that.

_________________
MBE/FE: R6, P4 2.8 GHz/2 GB/2 TB, GeForce 6200 512 MB, PVR-150, Cisco RNG-100 cable box
FE: R6, P4 2.0 GHz/1 GB, GeForce4 MX 420 64 MB, diskless netboot

Thanks langelgjm,

For pointing me in the right direction. It would have been easy to write off running them together based on bad advice on the net, but you pointed out that my machine did 'see' both drives, and with proper prepping of sda it's now showing up in 'df' [didn't before]



I believe the problem started when, as I noted above, I partitioned the drive with QTparted from a Mepis live CD.
I rolled dice and put on a MSdos header which may have been the problem. I had installation problems with 6, and network problems (I miss netconfig) Once I got them ironed out, and downloaded all the updates, my LinHes now had fdisk. So I partitioned the drive again, with the (xfs this time)

As noted above, sda now shows up. The rest of the exercise was following the KM wiki instructions under 'storage groups'. The i tb drive is now up and running.

This is a testbed, I don't know if having a screaming 10k rpm drive has any advantage doing the linux housekeeping, but I'll watch it a while, and see. (Not risking WAF on this machine yet...)

So the box I referred to above had been in heavy production up til now, when the backend couldn't be reached. Dmesg showed segfaulting in something called qtlib ?

I tried to fix with restore; no dice. Then the two line 6.02 update; still segfaulting, no backend.

Deep breath did auto-upgrade from the 6.02 CD. This got it running again, but the 2 drive problem noted above came back, the TB sata wasn't getting recognized. I eventually had to follow the wiki drive setup procedure, erasing the content (no loss in this case...) and getting the second drive recognized again.

But say I wanted to keep the content. Other than copying it off and then copying back on, was there a procedure that could have got the second drive recognized by the new LinHes without partition and mkdir of the drive, erasing it ?