Installing RedHat 8.0 onto Dell PowerEdge SC1425 - hdc: status error: status = 0x58 Post: 302079732

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Couldn't open status file /var/samba/STATUS.LCK

I believe i have most of samba configured right but i get this error each time time try to run it. I was given suggestion that i touch the file, i did, but i still cannot rid myself of this error. Any suggestions

2. Linux Benchmarks

Dell Dual Xeon PowerEdge 4600

Notes: System Configuration: Dell Computer Corporation PowerEdge 4600 (4 X Intel(R) XEON(TM) CPU 2.00GHz 1988.782 MHz) hyperthreaded System clock frequency: 99.0827 MHz Memory size (approximate): 2559 Megabytes ========================= CPUs ======================== CPU # CPU...

3. Linux Benchmarks

Dell Poweredge 2400 / 533

CPU/Speed: Dual PIII 533 Ram: 256Mb PC133 Motherboard: Unknown, Intel Chipset Cache: 256k on board Controller: PARC Raid 2/Si, AIC-7880U Disk: 30Gb RAID 5 Load: 1 user. Clean boot, init 5 but X-Windows not loaded. Kernel: See Benchmarks. pgms: gcc 3.2.3 ...

4. Solaris

Installing Solaris 10 on Dell PowerEdge 2800

hi, i am trying to install solaris 10 (on 4 cd's downloaded from the sun website) on my dell poweredge 2800 server. 2 xeon processors, 2GB of RAM and 2 NICS, 73 GB SCSI (maxtor ultra320, 3.5 series), i can give more details on request... the installation crashes when trying to detect the NICS...

5. Filesystems, Disks and Memory

Linux and Dell 1500sc Poweredge Server

Does anybody no how to get around the fact that the Red Hat installation does not see the SCSI hard drives. It lets you manually pick the proper device, but still fails saying no drive detected (or something to that effect). I was going to install windows 2003 Server and use VMware...but again,...

6. Programming

/dev/mem on Dell Poweredge

Hi, I have a C++ program to access /dev/mem and retrieve details like Vendor, Manufacturer details of the motherboard. This works fine on all the machines except for on Dell Poweredge 2850,1950... machines. I receive a 'EFAULT' when I try to access /dev/mem on these servers. I suspect some...

7. SCO

Dell PowerEdge 2600 tape backup

I was asked to get a Dell PowerEdge 2600 server, out of warranty, running SCO 3.2v5.06 to perform a full backup. I spent hours researching and preparing a strategy only to fail on-site. The only device names in /dev for a tape drive were /dev/xStp0 /dev/xcdt0 /dev/xct0 ...

8. Programming

How to track table status delete/update/insert status in DB2 V10 z/os?

Dear Team I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update ) Scenario We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted...

9. UNIX for Beginners Questions & Answers

Redhat Virtualization EN error : InitLogger main process terminated with status 1

My server has /var/log/messages with 'init: initLogger main process (608798) terminated with status 1' errors. I researched about the error and also followed the steps from stackexchange : 157059/error-init-ttys0-dev-ttys0-main-process-1612-terminated-with-status-1]linux - ERROR: init: ttyS0...

LEARN ABOUT OSF1

clear_wait

clear_wait(9r)															    clear_wait(9r)

NAME

       clear_wait - General: Clears the wait condition

SYNOPSIS

       void clear_wait(
	       thread_t thread,
	       int result,
	       boolean_t interrupt_only );

ARGUMENTS

       Specifies  a  pointer  to  the thread Specifies the outcome of the wait. You can pass one of the following values: This is a normal wakeup.
       The timeout period expired.  The clear_wait routine interrupted the wakeup.  Specifies a Boolean value that indicates  how  the	clear_wait
       routine clears the wait condition. You can pass one of the following values: Clears the wait condition only if the kernel thread is waiting
       in an interruptible state.  Clears the wait condition under any circumstances.

DESCRIPTION

       The clear_wait routine clears the wait condition for the specified kernel thread and starts executing the kernel thread, if appropriate. If
       the  kernel  thread is interruptible and is still waiting for the event, clear_wait sets the kernel thread state to TH_RUN and places it on
       the run queue.

RETURN VALUES

       None

SEE ALSO

       Routines: assert_wait_mesg(9r), mpsleep(9r), thread_block(9r), thread_wakeup(9r), thread_wakeup_one(9r)

																    clear_wait(9r)