Statistically speaking, it is unlikely that three HDD's would all have the same problem at the same time.... even if they are from the same batch, which leads me to believe it might be power related.
Ron -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, June 01, 2010 1:00 PM To: [email protected] Subject: clug-talk Digest, Vol 67, Issue 1 Send clug-talk mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://clug.ca/mailman/listinfo/clug-talk_clug.ca or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of clug-talk digest..." Today's Topics: 1. Re: Poweredge Disk Problem (William Astle) 2. Re: Poweredge Disk Problem ([email protected]) 3. membership card (Michael John Walters) 4. Re: Need drivers (Joe S) ---------------------------------------------------------------------- Message: 1 Date: Mon, 31 May 2010 22:34:16 -0600 From: William Astle <[email protected]> To: [email protected] Subject: Re: [clug-talk] Poweredge Disk Problem Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii; format=flowed On 10-05-31 06:35 PM, Ron Campbell wrote: > In any case, I don't think that is the biggest problem, the drives > themselves are not dependant on the PERC controller to 'spin up'. They > should do this even if they only have power connected. I think you have > drive / power problems, not a PERC controller problem. That's not strictly true depending on the hardware. I'm not entirely certain how this is accomplished but, in some systems, the spin-up is actually controlled by the raid controller itself. Whether this is accomplished through some funky stuff in the enclosure/case or if there is some sort of signalling on the data cable, I know it is done - usually to limit power draw during startup. Of course, the drives will spin up automatically in the absence of any stimulus to the contrary - they wouldn't be terribly useful if they didn't. All that said, I'd guess you have a disk that is failing in a way that the controller is not able to handle. -- William Astle [email protected] ------------------------------ Message: 2 Date: Tue, 1 Jun 2010 02:42:31 -0600 (MDT) From: [email protected] To: CLUG General <[email protected]> Subject: Re: [clug-talk] Poweredge Disk Problem Message-ID: <[email protected]> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Sun, 30 May 2010, Craig McLean wrote: > Date: Sun, 30 May 2010 19:21:34 -0600 > From: Craig McLean <[email protected]> > Reply-To: CLUG General <[email protected]> > To: 'CLUG General' <[email protected]> > Subject: [clug-talk] Poweredge Disk Problem > > Hello. > > > > I'm trying to setup OpenNAS on a Dell Poweredge 1800 server with 3 300GB > SCSI Hot Swappable disks. I'm experiencing some unusual behaviour. When I > turn the server on the disks periodically decide not to spin up. On this > server it is normal for the disks to start up a few moments after power is > applied, however for some reason that doesn't happen. When this happens the > POST process gets stuck at initializing the Dell PERC 4 RAID card. > > > Obviously this isn't an OpenNAS problem, however I am hoping somebody > who knows more about Dell server hardware will have some hints on what > is going on here. > My first two instincts would be to check the RAID card and the power supply. Most decent RAID cards have the ability to stagger the start up of the drives so that they all do not spin up at the same time placing undue stress on the PS. Check in the BIOS of the RAID card for such a setting, if it is not set, try staggering the start-up of the various drives. Can you test this system with a different (it could be same make/model or different) RAID card just to see if the disks power up reliably? You may also wish to try moving the RAID card to another PCI/PCI-X/PCIe slot if possible. Having said that, 3 drives is not something that usually stresses a power supply unless the power supply itself is failing. Try replacing the power supply if possible. Your priorities will dictate the order in which you proceed. If data integrity is most important, then start with the power supply. If time and convenience are more important than I would look at the RAID card first. Hth, __ Gustin ------------------------------ Message: 3 Date: Tue, 01 Jun 2010 10:53:20 -0600 From: Michael John Walters <[email protected]> To: clug talk <[email protected]> Subject: [clug-talk] membership card Message-ID: <[email protected]> Content-Type: text/plain; charset="UTF-8" Hello Clug Talk and Mr. Kwong, If I were go to the meeting Wednesday 2010 June 2 at 19:00 would I be able to sign my name and get my tier two membership card? If so, I will show up at the meeting. Otherwise I will stay home. Regards, Michael ------------------------------ Message: 4 Date: Tue, 1 Jun 2010 11:09:16 -0600 From: Joe S <[email protected]> To: CLUG General <[email protected]> Subject: Re: [clug-talk] Need drivers Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" eth0 is the Macronix card eth3 is the Realtek I checked my firewall and I had eth1 set. I changed it to eth0 and I got the Macronix card working. I still can't get the Realtek to work. There is no light blinking in the ethernet card when I insert the cable like there is with the Macronix card. Does that mean the card is dead, or do I not have the right driver for it? On May 31, 2010 01:03:12 pm Gustin Johnson wrote: > Most modern distros have a mapping of MAC address to device name. > Usually something like /etc/udev/rules.d/70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. # PCI device 0x10d9:0x0531 (tulip) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:80:c6:fb:8f:16", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x8086:0x100e (e1000) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:08:74:dc:12:35", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x1106:0x3106 (via-rhine) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:5a:07:f4:5b", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x10ec:0x8139 (8139too) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:a1:b0:10:7f:f1", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" > What distro are you using? Debian Lenny ------------------------------ _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca End of clug-talk Digest, Vol 67, Issue 1 **************************************** _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
