[arkeia-userlist] Dell Power Vault 100T"; // debut necessaire new version include($DOCUMENT_ROOT."/functions_dda.html"); //include("../../../functions_dda.html"); $next = ""; $previous = ""; $the_logo_gauche="arkeiaknox.gif"; $the_logo_droite="arkeia_468x60.gif"; $dir_offset="../../../"; include($DOCUMENT_ROOT."/header.html"); //include("../../../header.html"); // fin necessaire new version ?> [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



>
[arkeia-userlist] Dell Power Vault 100T
>
>
Hello list members,

I'm trying to set up a Dell PowerEdge 1300 with an internal DAT drive.
The Dell spec is PV 100T, physically it's a DAT DDS4 drive. SCSI
controller is Adaptec 7890. It's also got a Dell RAID controller, but I
don't think that's important.

The box is running stock Red Hat Linux 6.2, no changes to kernel or
drivers.

The drive shows up as /dev/st0 when the machine boots. I'm able to
manipulate the drive using the standard mt commands under Linux (and
probably other Unices). Arkeia also works fine using the null examples
in the manual.

I've tried to make Arkeia 4.2.6-1 connect to the DAT drive using the
STD-DAT definition. However, this leaves the drive dead. The log says
"Drive 'xx' is full"
"Can't open device '/dev/st0' for drive 'xx'

It seems that the process /usr/bin/knox/odts claims the drive, its
process state code shows up as "D", which man ps says is
"uninterruptible sleep". kill -9 PID does not affect this process.

What can I do to get the drive back short of rebooting the system? And
what is the correct drive definition if STD-DAT is not?

Any help appreciated.

-- 
Friendly greetings from the fringes of civilisation

Ragnar Wisløff
LinuxLabs AS
________________________________________
To be added or removed
Please visit http://www.arkeia.com/arkeialist.html
________________________________________