headers
Rahul Nabar | 1 Mar 2010 01:28
Picon

mixing SAS and SATA drives in a Dell SC1435

I had a power edge SC1435 with a small SAS drive connected to a PERC-i
card. I wanted more storage and have bought a large SATA drive. I
removed the SAS and connected the SATA to the PERC-i controller. It
recognizes it but randomly freezes the disk intermittently.

Can't figure out what the problem is. On the other hand the
motherboard seems to have two SATA risers on it. Should this be a
better option to connect?

Also, I read that Dell does not recommend mixing SAS and SATA drives
in the SC1435. Does that apply to drives connected to the PERC-i
alone? Or can I have a SAS-drive connected to the PERC-i and a SATA
connected directly to the motherboard riser?

--

-- 
Rahul

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 0 comments |
headers
Steve Tempest | 1 Mar 2010 09:05
Picon

Centos Update 1950 wont boot 2.6.18-164.11.1.el5

Hi,

 

Recently I updated my centos 5.0 server to the latest kernel/patches 5.4, when I restarted the server it seems the raid drivers are broken as it won’t boot.

 

The server has the PERC 6/i raid controller and it boots just find running an earlier kernel (2.6.18-53.1.21.el5). I’ve spent a fair bit of time searching around to see if there are any bugs reported that fit this problem and can’t find any.

 

Below is what comes up on the screen when booking off the newer kernel 2.6.18-164.11.1.el5:

 

Red Hat nash version 5.1.19.6 starting

unable to access resume device (/dev/VolGroup00/LogVol01)

mount: could not find filesystem ‘/dev/root’

setuproot: moving /dev failed: No such file or directory

setuproot: error mounting /proc: No such file or directory

setuproot: error mounting /sys: No such file or directory

switchroot: mount failed: No such file or directory

Kernel panic – not syncing: Attempted to kill init!

 

I’m not sure what exactly is the issue here as the raid controller was working just fine with the earlier version of the kernel?

 

Any help working out what are the best next steps would be greatly appreciated.

 

 

Cheers

 

Steve

Notice This email and any attachments are strictly confidential and subject to copyright. They may contain privileged information. If you are not the intended recipient please delete the message and notify the sender. You should not read, copy, use, change, alter or disclose this email or its attachments without authorisation. The company and any related or associated companies do not accept any liability in connection with this email and any attachments including in connection with computer viruses, data corruption, delay, interruption, unauthorised access or unauthorised amendment. Any views expressed in this email and any attachments do not necessarily reflect the views of the company or the views of any of our related or associated companies. 
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 6 comments |
headers
Nick Lunt | 1 Mar 2010 09:12

RE: Checking servers for firmware/driver updates etc


> -----Original Message-----
> From: Stephen Dowdy [mailto:sdowdy <at> ucar.edu]
> Sent: 26 February 2010 19:01
> To: Patrick_Fischer <at> dell.com; linux-poweredge <at> lists.us.dell.com
> Cc: Nick Lunt
> Subject: Re: Checking servers for firmware/driver updates etc
> 
> Patrick_Fischer <at> dell.com wrote, On 02/26/2010 03:28 AM:
> > We provide 2 Tools.
> ...
> > Old: IT Assistant (requires a Windows 32 Bit OS)
> > New: DMC (requires a w23 Host or VM)
> >
> > Both tools are able to compare server revisions with the actual
> Updates.
> > So you can run the comparison report to see which machines need to
be
> > updated. A snmp configuration on each machine is a must have.
> ...
> > Maybe some of the Linux guys are able to run such reports with
Nagios
> > or anything else, maybe with reading out the FW and driver strings
> > (omreport) and compare it with the latest versions from the Update
> DVD
> > dell provide ca. 1 time per quarter.
> 
> I manage 100s of Debian, RHEL, and SLES boxes here.
> 
> I enclose a script that's hit/miss to do *some* inventory.
> Here's sample output:
> 
> [root <at> server1 MegaRAID]# /opt/sbin/ral-superinv
> Hostname:        [server1]
> Manufacturer:    [Dell Inc.]
> Model:           [PowerEdge 2950]
> Serial Number:   [XXXXXXX]
> BIOS Version:    [2.4.3] *(!=2.6.1)
> BMC Version:     [2.28] *(!=2.37)
> PERC5i Version:  [1.03, 1.03]
> PERC5E Version:  [1.03, 1.03, 1.03, 1.03, 1.03, 1.03, 1.03]
> SASBP Version:   [1.05]
> MD1000 Version:  [A.04, A.04, A.04, A.04, A.04]
> 
> It's seriously flawed, predominantly because it requires constant
> manual updating to report out-of-rev BIOS, etc.  Why do i do this and
> not run OMSA?

Hi Stephen

thanks for the info, I appreciate you sharing your script.

__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4903 (20100228) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 0 comments |
headers
Edward S.P. Leung | 1 Mar 2010 09:40
Picon

Dell R710 + PERC 6/i Raid Controller Card + Linux Fedora 11/12 System

Dear All,
 
As the title....
Is there a Raid monitoring ( utility / management ) tool for Linux Fedora System ?
If so, how to download and install with FC System ?
 
Thanks !
 
Edward.
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 2 comments |
headers
Jon Marston | 1 Mar 2010 10:27
Favicon

RE: SCSI Tape drive on PowerEdge 2970 / LSI2032

Thanks for both your responses.

It does sound to be some kind of faulty connection somewhere, but I've
tried the tape drive and cable on another server (SCSI 160 card) and it
works without issues (putting it back on the original server brings back
the issue so I don't think it needed reseating or anything). How likely
is it that something within the card could be knackering bits 0 and 2?

Anyhow, we have someone from Dell onsite today to mess about with the
SCSI card, in case the connection problem is caused by that.

Thanks,

Jon

-----Original Message-----
From: linux-poweredge-bounces <at> dell.com
[mailto:linux-poweredge-bounces <at> dell.com] On Behalf Of Jefferson Ogata
Sent: 27 February 2010 02:03
To: linux-poweredge <at> dell.com
Subject: Re: SCSI Tape drive on PowerEdge 2970 / LSI2032

On 2010-02-27 00:45, John LLOYD wrote:
>> From: "Jon Marston" <jonm <at> januahortorum.com>
>> The problem we're having is that the SCSI card identified the Drive
at
>> ID 6 with a name of 'PP <at> JPPH PHPRHPH 2', which doesn't sound right to
>> me.
[snip]
> Or the cable is broken or pins are broken.

I'd lean with this explanation. Note that that "PP <at> JPPH PHPRHPH 2" is
exactly what you get when you take "QUANTUM ULTRIUM 3" and clear bits 0
and 2 in every character.

Check the pins on both the cable and the terminator. Those 68-pin
connectors are a bitch.

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 1 comment |
headers
Jon Marston | 1 Mar 2010 11:29
Favicon

RE: SCSI Tape drive on PowerEdge 2970 / LSI2032

Yeah, the card was faulty.

Thanks for your help anyway guys.

 - jon

-----Original Message-----
From: linux-poweredge-bounces <at> dell.com
[mailto:linux-poweredge-bounces <at> dell.com] On Behalf Of Jon Marston
Sent: 01 March 2010 09:27
To: Linux-PowerEdge <at> dell.com
Subject: RE: SCSI Tape drive on PowerEdge 2970 / LSI2032

Thanks for both your responses.

It does sound to be some kind of faulty connection somewhere, but I've
tried the tape drive and cable on another server (SCSI 160 card) and it
works without issues (putting it back on the original server brings back
the issue so I don't think it needed reseating or anything). How likely
is it that something within the card could be knackering bits 0 and 2?

Anyhow, we have someone from Dell onsite today to mess about with the
SCSI card, in case the connection problem is caused by that.

Thanks,

Jon

-----Original Message-----
From: linux-poweredge-bounces <at> dell.com
[mailto:linux-poweredge-bounces <at> dell.com] On Behalf Of Jefferson Ogata
Sent: 27 February 2010 02:03
To: linux-poweredge <at> dell.com
Subject: Re: SCSI Tape drive on PowerEdge 2970 / LSI2032

On 2010-02-27 00:45, John LLOYD wrote:
>> From: "Jon Marston" <jonm <at> januahortorum.com>
>> The problem we're having is that the SCSI card identified the Drive
at
>> ID 6 with a name of 'PP <at> JPPH PHPRHPH 2', which doesn't sound right to
>> me.
[snip]
> Or the cable is broken or pins are broken.

I'd lean with this explanation. Note that that "PP <at> JPPH PHPRHPH 2" is
exactly what you get when you take "QUANTUM ULTRIUM 3" and clear bits 0
and 2 in every character.

Check the pins on both the cable and the terminator. Those 68-pin
connectors are a bitch.

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 0 comments |
headers
Joe Gooch | 1 Mar 2010 15:53
Favicon

RE: Dell R710 + PERC 6/i Raid Controller Card + Linux Fedora 11/12 System

http://linux.dell.com/storage.shtml

 

Right at the top, SAS RAID and non-RAID

 

I successfully use the MegaCLI – Linux package on Mandriva with my R710’s.

 

Joe

 

From: linux-poweredge-bounces <at> dell.com [mailto:linux-poweredge-bounces <at> dell.com] On Behalf Of Edward S.P. Leung
Sent: Monday, March 01, 2010 3:40 AM
To: linux-poweredge <at> dell.com
Subject: Dell R710 + PERC 6/i Raid Controller Card + Linux Fedora 11/12 System

 

Dear All,

 

As the title....

Is there a Raid monitoring ( utility / management ) tool for Linux Fedora System ?

If so, how to download and install with FC System ?

 

Thanks !

 

Edward.

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 1 comment |
headers
J. Epperson | 1 Mar 2010 15:57

Re: Centos Update 1950 wont boot 2.6.18-164.11.1.el5

On Mon, March 1, 2010 03:05, Steve Tempest wrote:
> The server has the PERC 6/i raid controller and it boots just find
> running an earlier kernel (2.6.18-53.1.21.el5). I've spent a fair bit of
> time searching around to see if there are any bugs reported that fit this
> problem and can't find any.
>
> Below is what comes up on the screen when booking off the newer kernel
> 2.6.18-164.11.1.el5:
>
> Red Hat nash version 5.1.19.6 starting
>
> unable to access resume device (/dev/VolGroup00/LogVol01)
>
> mount: could not find filesystem '/dev/root'
>
> setuproot: moving /dev failed: No such file or directory
>
> setuproot: error mounting /proc: No such file or directory
>
> setuproot: error mounting /sys: No such file or directory
>
> switchroot: mount failed: No such file or directory
>
> Kernel panic - not syncing: Attempted to kill init!
>
>
>
> I'm not sure what exactly is the issue here as the raid controller was
> working just fine with the earlier version of the kernel?
>

This smells like a busted initrd.  Check if the initrd file for it looks
curiously truncated.  If so (and maybe if not, won't break anything else)
with the earlier kernel booted, do a manual mkinitrd for the new kernel.

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 5 comments |
headers
PJF | 1 Mar 2010 17:56

RE: Centos Update 1950 wont boot 2.6.18-164.11.1.el5

> From: linux-poweredge-bounces <at> dell.com [mailto:linux-poweredge-
> bounces <at> dell.com] On Behalf Of J. Epperson
> 
> On Mon, March 1, 2010 03:05, Steve Tempest wrote:
> > The server has the PERC 6/i raid controller and it boots just find
> > running an earlier kernel (2.6.18-53.1.21.el5). I've spent a fair bit
> of
> > time searching around to see if there are any bugs reported that fit
> this
> > problem and can't find any.
> >
> > Below is what comes up on the screen when booking off the newer
> kernel
> > 2.6.18-164.11.1.el5:
> >
> > Red Hat nash version 5.1.19.6 starting
> >
> > unable to access resume device (/dev/VolGroup00/LogVol01)
> >
> > mount: could not find filesystem '/dev/root'
> >
> > setuproot: moving /dev failed: No such file or directory
> >
> > setuproot: error mounting /proc: No such file or directory
> >
> > setuproot: error mounting /sys: No such file or directory
> >
> > switchroot: mount failed: No such file or directory
> >
> > Kernel panic - not syncing: Attempted to kill init!
> >
> >
> >
> > I'm not sure what exactly is the issue here as the raid controller
> was
> > working just fine with the earlier version of the kernel?
> >
> 
> This smells like a busted initrd.  Check if the initrd file for it
> looks
> curiously truncated.  If so (and maybe if not, won't break anything
> else)
> with the earlier kernel booted, do a manual mkinitrd for the new
> kernel.

Running 2.6.18-164.11.1.el5 on a 1950 III with a PERC 6/I here - no issues.

--
pjf

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 0 comments |
headers
Stroller | 1 Mar 2010 19:15
Picon

Re: Kernel .config for non-RAID 2850 scsi controller - IGNORE


On 1 Mar 2010, at 16:29, Stroller wrote:
> ...
> I've just acquired a PowerEdge 2850 for which the RAID key is  
> unfortunately missing (let me know off-list if you have one of these  
> for sensible money). I can boot it with a live CD and the hard-disk  
> is recognised - I believe this is operating in a non-RAID, non- 
> hotswap mode. I have partitioned he drive & copied over a Gentoo  
> stage installation, but when I boot I get a kernel panic because I  
> can't find what drivers to enable in the kernel.

Please ignore the above request for help (if it comes through - I sent  
it 90 minutes ago, and it's not showing up here yet).

The drivers were exactly where I'd been told to look for them, but for  
some reason I still hadn't seen them for looking:

Device Drivers --->
  Fusion MPT device support  --->
   <*>   Fusion MPT ScsiHost drivers for SPI
   <*>   Fusion MPT ScsiHost drivers for FC
   <M>   Fusion MPT ScsiHost drivers for SAS
   (40)  Maximum number of scatter gather entries (16 - 128)
   <*>   Fusion MPT misc device (ioctl) driver
   <M>   Fusion MPT LAN driver
   [*]   Fusion MPT logging facility

I was completely confused that these weren't under:

Device Drivers --->
  SCSI device support  --->
   SCSI low-level drivers  --->

which is where I found the "LSI MPT Fusion SAS 2.0 Device Driver"  
mentioned in my previous post. There is undoubtedly a good reason for  
this.

Stroller.

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 0 comments |

Gmane