3ware woes, seem to be missing vital /proc files...
From: Stephen Tait (tait_at_digitallaw.co.uk)
Date: 09/07/04
- Previous message: Clemens Schwaighofer: "gkrellmss and alsa"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 07 Sep 2004 16:35:25 +0100 To: debian-user@lists.debian.org
Different this time, I promise!
After much mucking about, the 3ware 9500 is working beautifully as I would
expect and is sitting there with a nice fat 750GB LVM. But I can't get 3DM2
(3ware Disk Management daemon mk. 2) to run. It complains about not being
able to start a listening socket...?
I straced it and it came back with this;
zaphod:/home/pika/3dm2# strace 3dm2
execve("/usr/sbin/3dm2", ["3dm2"], [/* 16 vars */]) = 0
uname({sys="Linux", node="zaphod", ...}) = 0
fcntl64(0, F_GETFD) = 0
fcntl64(1, F_GETFD) = 0
fcntl64(2, F_GETFD) = 0
geteuid32() = 0
getuid32() = 0
getegid32() = 0
getgid32() = 0
getrlimit(0x3, 0xbffff548) = 0
setrlimit(RLIMIT_STACK, {rlim_cur=2044*1024, rlim_max=RLIM_INFINITY}) = 0
getpid() = 1274
rt_sigaction(SIGRTMIN, {0x80ebcb0, [], 0x4000000}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {0x80ebbbc, [], 0x4000000}, NULL, 8) = 0
rt_sigaction(SIGRT_2, {0x80ebd1c, [], 0x4000000}, NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [RTMIN], NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [33], NULL, 8) = 0
_sysctl({{CTL_KERN, KERN_VERSION}, 2, 0xbffff550, 34, (nil), 0}) = 0
brk(0) = 0x81ef000
brk(0x81f0000) = 0x81f0000
open("/proc/devices", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x40000000
read(3, "Character devices:\n 1 mem\n 2 p"..., 1024) = 465
read(3, "", 1024) = 0
close(3) = 0
munmap(0x40000000, 4096) = 0
open("/proc/devices", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x40000000
read(3, "Character devices:\n 1 mem\n 2 p"..., 1024) = 465
close(3) = 0
munmap(0x40000000, 4096) = 0
stat64("/dev/twa0", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 0), ...}) = 0
stat64("/dev/twa1", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 1), ...}) = 0
stat64("/dev/twa2", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 2), ...}) = 0
stat64("/dev/twa3", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 3), ...}) = 0
stat64("/dev/twa4", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 4), ...}) = 0
stat64("/dev/twa5", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 5), ...}) = 0
stat64("/dev/twa6", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 6), ...}) = 0
stat64("/dev/twa7", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 7), ...}) = 0
stat64("/dev/twa8", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 8), ...}) = 0
stat64("/dev/twa9", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 9), ...}) = 0
stat64("/dev/twa10", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 10), ...}) = 0
stat64("/dev/twa11", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 11), ...}) = 0
stat64("/dev/twa12", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 12), ...}) = 0
stat64("/dev/twa13", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 13), ...}) = 0
stat64("/dev/twa14", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 14), ...}) = 0
stat64("/dev/twa15", {st_mode=S_IFCHR|0600, st_rdev=makedev(253, 15), ...}) = 0
open("/dev/null", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = -1 ENOTDIR (Not a
directory)
open("/proc/scsi/3w-9xxx", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) =
-1 ENOENT (No such file or directory)
fork() = 1275
semget(IPC_PRIVATE, 0, 0zaphod:/home/pika/3dm2# (0x0C:0x0005): Failed to
start listening socket
Now, I'm an absolute clueless n00b when it comes to stuff like this. All
/proc/scsi contains is:
zaphod:/home/pika/3dm2# ls -l /proc/scsi/
total 0
-r--r--r-- 1 root root 0 Sep 7 15:58 device_info
-r--r--r-- 1 root root 0 Sep 7 15:58 scsi
with no mention of the 3w-9xxx driver anywhere. Is this some kind of
RH/SuSE specific thing (since 3ware only officially support those distros),
or is it because I compiled the driver into the kernel rather than as a
module? Or something else entirely that mere admins like me can't dream of?
Googling for the error returns pretty much nothing. Anyone have any ideas?
-- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
- Previous message: Clemens Schwaighofer: "gkrellmss and alsa"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
