Hi Dale, [node1] ~ > ls -l /dev/sda* ls: /dev/sda*: No such file or directory
[node1] ~ > ls -lR /dev/discs/ /dev/discs/: total 16K drwxr-xr-x 2 root root 4.0K Jan 1 1970 . drwxr-xr-x 24 root root 12K Oct 1 07:22 .. lrwxrwxrwx 1 root root 30 Aug 18 2004 disc0 -> ../ide/host0/bus0/target0/lun0 lrwxrwxrwx 1 root root 30 Aug 18 2004 disc1 -> ../ide/host0/bus0/target1/lun0 Greetings! Fabian * Dale wrote 30 Sep 2005: > Fabian, > > I mean permission on the device file. Maybe udev broke it somehow. > > ls -l /dev/sda* > ls -lR /dev/discs > > if you could. > > Thanks, > > Dale > > On Fri, 2005-09-30 at 16:24 +0200, Fabian Braennstroem wrote: > > Hi Dale, > > > > what do you mean by permissions? Shouldn't I be able to > > check the drive with fdisk as root with: fdisk /dev/sda > > > > Fabian > > > > * Dale wrote 30 Sep 2005: > > > > > Are the permissions OK on the part devices (and the paths leading to > > > them)? If they are, I'm at a loss. > > > > > > Dale > > > > > > On Fri, 2005-09-30 at 08:02 +0200, Fabian Braennstroem wrote: > > > > Hi, > > > > > > > > * Dale wrote 29 Sep 2005: > > > > > > > > > Udev or devfs? If devfs, is there anything in /dev/discs? > > > > > > > > Udev; but there are two discs in /dev/discs. The listed > > > > 'parts' in /dev/discs are not mountable and udev seem to > > > > work all right. > > > > > > > > Fabian > > > > > > > > > > > > > > Dale > > > > > > > > > > On Thu, 2005-09-29 at 21:37 +0200, Fabian Braennstroem wrote: > > > > > > Hi, > > > > > > > > > > > > I tried 'cfdisk /dev/sda' which did not work: 'FATAL ERROR: > > > > > > Cannot open disk drive' and 'fdisk -l /dev/sda' doesn't > > > > > > print anything. Just using 'fdisk /dev/sda' I get: 'Unable > > > > > > to open /dev/sda' > > > > > > I just checked if I can mount the partitions with > > > > > > 'ScientificLinux' (Redhat-'Clone'); it worked fine. > > > > > > > > > > > > Fabian > > > > > > > > > > > > * Dale wrote 29 Sep 2005: > > > > > > > > > > > > > What do you mean you don't get any access to /dev/sda? > > > > > > > > > > > > > > Try "fdisk -l /dev/sda" as root. > > > > > > > > > > > > > > Dale > > > > > > > > > > > > > > On Thu, 2005-09-29 at 21:16 +0200, Fabian Braennstroem wrote: > > > > > > > > Hi Dale, > > > > > > > > > > > > > > > > * Dale wrote 29 Sep 2005: > > > > > > > > > > > > > > > > > /dev/sda should now be available to use, though. Is it a > > > > > > > > > 200gb drive > > > > > > > > > like is reported? > > > > > > > > > > > > > > > > I don't get any access to /dev/sda ... Yes it is a 200gb > > > > > > > > drive und I have four partitions on it; two of them for > > > > > > > > linux. Like I wrote in the beginning I already copied some > > > > > > > > data on it using Mepis... strange!? > > > > > > > > > > > > > > > > Greetings! > > > > > > > > Fabian > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dale > > > > > > > > > > > > > > > > > > On Thu, 2005-09-29 at 18:09 +0200, Fabian Braennstroem wrote: > > > > > > > > > > Hi Dale, > > > > > > > > > > > > > > > > > > > > that is strange; I just installed the kernel26-scsi and get > > > > > > > > > > no other result!? > > > > > > > > > > The kernel log looks similar: > > > > > > > > > > > > > > > > > > > > Sep 29 17:15:52 node1 kernel: libata version 1.11 loaded. > > > > > > > > > > Sep 29 17:15:52 node1 kernel: ata_piix version 1.03 > > > > > > > > > > Sep 29 17:15:52 node1 kernel: ACPI: PCI Interrupt > > > > > > > > > > 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 18 > > > > > > > > > > Sep 29 17:15:52 node1 kernel: PCI: Setting latency timer of > > > > > > > > > > device 0000:00:1f.2 to 64 > > > > > > > > > > Sep 29 17:15:52 node1 kernel: ata1: SATA max UDMA/133 cmd > > > > > > > > > > 0xEFE0 ctl 0xEFAE bmdma 0xEF60 irq 18 > > > > > > > > > > Sep 29 17:15:52 node1 kernel: ata2: SATA max UDMA/133 cmd > > > > > > > > > > 0xEFA0 ctl 0xEFAA bmdma 0xEF68 irq 18 > > > > > > > > > > Sep 29 17:15:52 node1 kernel: ata1: dev 0 cfg 49:2f00 > > > > > > > > > > 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:20ff > > > > > > > > > > Sep 29 17:15:52 node1 kernel: ata1: dev 0 ATA, max UDMA7, > > > > > > > > > > 390721968 sectors: lba48 > > > > > > > > > > Sep 29 17:15:52 node1 kernel: ata1: dev 0 configured for > > > > > > > > > > UDMA/133 > > > > > > > > > > Sep 29 17:15:52 node1 kernel: scsi2 : ata_piix > > > > > > > > > > Sep 29 17:15:52 node1 kernel: ata2: SATA port has no device. > > > > > > > > > > Sep 29 17:15:52 node1 kernel: scsi3 : ata_piix > > > > > > > > > > Sep 29 17:15:52 node1 kernel: Vendor: ATA Model: > > > > > > > > > > SAMSUNG SP2004C Rev: VM10 > > > > > > > > > > Sep 29 17:15:52 node1 kernel: Type: Direct-Access > > > > > > > > > > ANSI SCSI revision: 05 > > > > > > > > > > Sep 29 17:15:52 node1 kernel: SCSI device sda: 390721968 > > > > > > > > > > 512-byte hdwr sectors (200050 MB) > > > > > > > > > > Sep 29 17:15:52 node1 kernel: SCSI device sda: drive cache: > > > > > > > > > > write back > > > > > > > > > > Sep 29 17:15:52 node1 kernel: SCSI device sda: 390721968 > > > > > > > > > > 512-byte hdwr sectors (200050 MB) > > > > > > > > > > Sep 29 17:15:52 node1 kernel: SCSI device sda: drive cache: > > > > > > > > > > write back > > > > > > > > > > Sep 29 17:15:52 node1 kernel: > > > > > > > > > > /dev/scsi/host2/bus0/target0/lun0: p1 p2 < p5 p6 > > > > > > > > > > > Sep 29 17:15:52 node1 kernel: Attached scsi disk sda at > > > > > > > > > > scsi2, channel 0, id 0, lun 0 > > > > > > > > > > Sep 29 17:15:52 node1 kernel: Attached scsi generic sg0 at > > > > > > > > > > scsi2, channel 0, id 0, lun 0, type 0 > > > > > > > > > > > > > > > > > > > > Before I checked the /dev/hd* devices, but there was none > > > > > > > > > > which I can get access to with cfdisk, except /dev/hda my > > > > > > > > > > running ide-drive. > > > > > > > > > > > > > > > > > > > > Greetings! > > > > > > > > > > Fabian > > > > > > > > > > > > > > > > > > > > * Dale wrote 29 Sep 2005: > > > > > > > > > > > > > > > > > > > > > Fabian, > > > > > > > > > > > > > > > > > > > > > > ata_piix isn't libata. It might show up now as hdX but > > > > > > > > > > > in order for you > > > > > > > > > > > to have it show up as sdX, you'll need the kernel26-scsi > > > > > > > > > > > kernel. > > > > > > > > > > > > > > > > > > > > > > Dale > > > > > > > > > > > > > > > > > > > > > > On Thu, 2005-09-29 at 16:42 +0200, Fabian Braennstroem > > > > > > > > > > > wrote: > > > > > > > > > > > > Hi Dale, > > > > > > > > > > > > > > > > > > > > > > > > thanks for the quick response, but doesn't the kernel > > > > > > > > > > > > log > > > > > > > > > > > > say that it found libata and the drive? > > > > > > > > > > > > > > > > > > > > > > > > Greetings! > > > > > > > > > > > > Fabian > > > > > > > > > > > > > > > > > > > > > > > > * Dale wrote 29 Sep 2005: > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 2005-09-29 at 15:45 +0200, Fabian > > > > > > > > > > > > > Braennstroem wrote: > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > > > > > > > no I installed the default 'kernel26' from arch, > > > > > > > > > > > > > > but I am > > > > > > > > > > > > > > not able to access (with mount or cfdisk /dev/sda) > > > > > > > > > > > > > > the sata drive. The kernel log says: > > > > > > > > > > > > > > > > > > > > > > > > > > Try kernel26-scsi instead. SATA support is in the > > > > > > > > > > > > > scsi kernel in Arch > > > > > > > > > > > > > (since libata uses the scsi core). > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dale _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
