Re: [Linux-PowerEdge] [E] Re: replacing a failed hard drive with PERC HBA mode

2017-08-10 Thread Cameron Smith
In regard to: Re: [Linux-PowerEdge] [E] Re: replacing a failed hard
> drive...:
>
> > On 08/10/2017 05:49 PM, Tim Mooney wrote:
>
> >> The particular system that has the failed drive happens to not be at the
> >> 2.x release for iDRAC 7.
> >>
> >> We're going to schedule an outage for this weekend and remedy that.
> We're
> >> also going to pull a report from our OME system to try identify any
> other
> >> systems that don't have recent iDRAC 7 or iDRAC 8 versions.
>
> > Shouldn't need any downtime. Just download and run
> > https://downloads.dell.com/FOLDER04020316M/1/iDRAC-with-
> Lifecycle-Controller_Firmware_XTPX4_LN_2.41.40.40_A00.BIN
>
> I've done that kind of thing for smaller version bumps for things like
> the NIC, but considering it's iDRAC and we're going from 1.57.something
> to 2.41.40.40, I felt like it would be a lot safer to do this during
> an outage.  I also didn't know if there were any dependencies involved,
> with other component versions (other things also needing to be updated,
> in a particular order, because of the change in major version # of
> the iDRAC).
>
> I appreciate the tip though!  If we find any other systems that have
> iDRAC that's in the 1.x series and the system isn't as critical, I may
> give the individual .BIN update a try.
>
> Tim
>
>
Using the 64-bit EXE through the DRAC should be just fine.
I recommend to clear out anything left over in the lifecycle controller job
queue and then reset the drac from the DRAC main page before you start.

After you upload it to the DRAC using the DRAC GUI in iDRAC Settings >
Update and Rollback and set it to run it's a good idea to ping the drac IP.
The installation usually takes a few minutes and then you should see the IP
go down while the DRAC reboots and then usually after about 2 minutes it
comes back up. You should then be able to log back into the DRAC and see it
running on the new version.

Cameron
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


Re: [Linux-PowerEdge] [E] Re: replacing a failed hard drive with PERC HBA mode

2017-08-10 Thread Tim Mooney
In regard to: Re: [Linux-PowerEdge] [E] Re: replacing a failed hard drive...:

> On 08/10/2017 05:49 PM, Tim Mooney wrote:

>> The particular system that has the failed drive happens to not be at the
>> 2.x release for iDRAC 7.
>> 
>> We're going to schedule an outage for this weekend and remedy that.  We're
>> also going to pull a report from our OME system to try identify any other
>> systems that don't have recent iDRAC 7 or iDRAC 8 versions.

> Shouldn't need any downtime. Just download and run 
> https://downloads.dell.com/FOLDER04020316M/1/iDRAC-with-Lifecycle-Controller_Firmware_XTPX4_LN_2.41.40.40_A00.BIN

I've done that kind of thing for smaller version bumps for things like
the NIC, but considering it's iDRAC and we're going from 1.57.something
to 2.41.40.40, I felt like it would be a lot safer to do this during
an outage.  I also didn't know if there were any dependencies involved,
with other component versions (other things also needing to be updated,
in a particular order, because of the change in major version # of
the iDRAC).

I appreciate the tip though!  If we find any other systems that have
iDRAC that's in the 1.x series and the system isn't as critical, I may
give the individual .BIN update a try.

Tim
-- 
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


Re: [Linux-PowerEdge] [E] Re: replacing a failed hard drive with PERC HBA mode

2017-08-10 Thread Robert Jacobson
On 8/10/2017 5:03 PM, Patrick Boutilier wrote:
>
> Shouldn't need any downtime. Just download and run 
> https://downloads.dell.com/FOLDER04020316M/1/iDRAC-with-Lifecycle-Controller_Firmware_XTPX4_LN_2.41.40.40_A00.BIN

You can also upload the windows binary updater (e.g. 
iDRAC-with-Lifecycle-Controller_Firmware_XTPX4_WN64_2.41.40.40_A00.EXE) to the 
iDRAC web interface.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


Re: [Linux-PowerEdge] [E] Re: replacing a failed hard drive with PERC HBA mode

2017-08-10 Thread Patrick Boutilier

On 08/10/2017 05:49 PM, Tim Mooney wrote:

In regard to: RE: [E] Re: [Linux-PowerEdge] replacing a failed hard drive...:


If you're not seeing that function in the iDRAC, make sure you are
running the latest version.  I'm currently running  firmware version
2.41.40.40


You're right, it is a function of iDRAC version.  Despite the post
I initially quoted, I've since found documentation that vdisk management
was added in the 2.x releases for iDRAC 7 and apparently iDRAC 8.

The particular system that has the failed drive happens to not be at the
2.x release for iDRAC 7.

We're going to schedule an outage for this weekend and remedy that.  We're
also going to pull a report from our OME system to try identify any other
systems that don't have recent iDRAC 7 or iDRAC 8 versions.

Thanks much to everyone that's responded!  It's been very helpful in
filling in what we were missing.


Shouldn't need any downtime. Just download and run 
https://downloads.dell.com/FOLDER04020316M/1/iDRAC-with-Lifecycle-Controller_Firmware_XTPX4_LN_2.41.40.40_A00.BIN





Tim



<>___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


Re: [Linux-PowerEdge] [E] Re: replacing a failed hard drive with PERC HBA mode

2017-08-10 Thread Kingston, Scott J
Tim,

If you're not seeing that function in the iDRAC, make sure you are running the 
latest version.  I'm currently running  firmware version 2.41.40.40


Best Regards,
Scott

-Original Message-
From: linux-poweredge-boun...@dell.com 
[mailto:linux-poweredge-boun...@dell.com] On Behalf Of Robert Jacobson
Sent: Thursday, August 10, 2017 1:45 PM
To: 'Tim Mooney' ; 'Artit Jirapatnakul' 
Cc: linux-poweredge@dell.com
Subject: [E] Re: [Linux-PowerEdge] replacing a failed hard drive with PERC HBA 
mode


To see which RAID functions are supported by iDRAC, see this document (starting 
on page 191):

https://urldefense.proofpoint.com/v2/url?u=http-3A__topics-2Dcdn.dell.com_pdf_idrac7-2D8-2Dlifecycle-2Dcontroller-2Dv2.40.40.40-5FUse=DwICAg=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=sZA28jIebnZqNAL0vpYk2d6QxpNmuA4geqEmLP6D8ow=ajqJCFewveioxV3sBWaRe_28ULsqsfjWg5Yp_7flBcY=cCs2zfbbmxAKmKWoTTAuNBLeLs0HLKOOqgjdTKUuXhk=
r's%20Guide_en-us.pdf


-Original Message-
From: linux-poweredge-boun...@dell.com
[mailto:linux-poweredge-boun...@dell.com] On Behalf Of Tim Mooney
Sent: Thursday, August 10, 2017 12:01 PM
To: Artit Jirapatnakul 
Cc: linux-poweredge@dell.com
Subject: Re: [Linux-PowerEdge] replacing a failed hard drive with PERC HBA
mode

In regard to: Re: [Linux-PowerEdge] replacing a failed hard drive with
PERC...:

> Does the H710 support HBA mode? I thought it wasn't until the PERC9 
> series that HBA mode was supported.

I'm fairly certain it's in HBA mode.  It reports "User Mode" in the iDRAC
7 web interface, when looking at the controller view.

> If that's the case, you probably just have to create a RAID0 virtual 
> disk with the single drive. I guess you could confirm by seeing if you 
> have any other virtual disks listed in the storage section of the iDRAC.

There are 3 other vdisks listed in the "Storage->Virtual Disks" section of
the iDRAC7 interface: vdisk0, vdisk2, and vdisk3.  It's vdisk1 that I'm
trying to get to appear.

Scott Kingston's response gave me enough information to confirm that iDRAC 7
does not support creating a vdisk via that interface, so right now I'm
looking at the remote access options via other tools.

Thanks!

Tim

> On Wed, Aug 9, 2017 at 6:14 PM, Tim Mooney  wrote:
>
>>
>> Hi All!
>>
>> I need to replace a hard drive in a Dell R720 that's running RHEL 6.9.
>> The problem is that the replacement drive shows up as "Ready" in the 
>> physical disks area of iDRAC, instead of "Online".  It does not 
>> automatically show up as a vdisk in the virtual disks area.
>>
>> The PERC H710 mini is in HBA mode, not RAID mode, so it's not 
>> handling the mirroring.  That's being done at the OS level with Linux's
mdadm.
>>
>> This hard drive is part of an mdadm RAID1.  The drive failed 
>> completely, so mdadm failed each of the partitions out of the individual
MD devices.
>> I removed the failed MD components and then forced the OS to forget 
>> about /dev/sdb, with
>>
>> # echo 1 > /sys/block/sdb/device/delete
>>
>> I pulled the failed hard drive from the hot-swap bay, installed the 
>> Dell replacement drive in the carrier, and inserted the replacement 
>> hard drive into the bay.  The drive LED blinked and went green, and 
>> iDRAC shows the physical disk as "Ready", instead of "Online", and 
>> the replacement is missing completely from the vdisk area.
>>
>> The OS did not auto-detect a hard drive being added to the bus, and 
>> even a rescan via
>>
>> # echo '- - -' > /sys/class/scsi_host/host0/scan
>>
>> does not trigger it to recognize the replacement drive is there.  I'm 
>> guessing that's because I need to do something at the 
>> PERC/iDRAC/Lifecycle level to get the drive to switch to "Online" and
make it a vdisk.
>>
>> How do I go about doing that?
>>
>> We do not currently have any Dell OS-level RPMs installed, so no omsa 
>> or srv-admin or whatever.  After being on this list for a couple of 
>> years, my confidence in those tools is extremely limited.
>>
>> It seems like 'megaclisas' might be able to help, but I have been 
>> completely unable to find a working link to that tool, after the
>> LSI->Avago->Broadcomm transition.  If anyone has a working link to 
>> LSI->Avago->get
>> it, I would appreciate seeing it.
>>
>> Could 'racadm' via ssh perform the necessary magic to get this drive 
>> so that the PERC is presenting it as a disk to the OS?  Is there 
>> something easier than that, that also doesn't require a huge mess of 
>> questionable Dell RPMs be installed?
>>
>> Any suggestions are much appreciated,
>>
>> Tim
>> --
>> Tim Mooney
tim.moo...@ndsu.edu
>> Enterprise Computing & Infrastructure  701-231-1076
>> (Voice)
>> Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
>> North Dakota State University, Fargo, ND 58105-5164
>>
>> ___
>> Linux-PowerEdge mailing list
>> 

Re: [Linux-PowerEdge] replacing a failed hard drive with PERC HBA mode

2017-08-10 Thread Tim Mooney
In regard to: Re: [Linux-PowerEdge] replacing a failed hard drive with PERC...:

> Does the H710 support HBA mode? I thought it wasn't until the PERC9 series
> that HBA mode was supported.

I'm fairly certain it's in HBA mode.  It reports "User Mode" in the iDRAC
7 web interface, when looking at the controller view.

> If that's the case, you probably just have to create a RAID0 virtual disk
> with the single drive. I guess you could confirm by seeing if you have any
> other virtual disks listed in the storage section of the iDRAC.

There are 3 other vdisks listed in the "Storage->Virtual Disks" section
of the iDRAC7 interface: vdisk0, vdisk2, and vdisk3.  It's vdisk1 that
I'm trying to get to appear.

Scott Kingston's response gave me enough information to confirm that
iDRAC 7 does not support creating a vdisk via that interface, so right
now I'm looking at the remote access options via other tools.

Thanks!

Tim

> On Wed, Aug 9, 2017 at 6:14 PM, Tim Mooney  wrote:
>
>>
>> Hi All!
>>
>> I need to replace a hard drive in a Dell R720 that's running RHEL 6.9.
>> The problem is that the replacement drive shows up as "Ready" in the
>> physical disks area of iDRAC, instead of "Online".  It does not
>> automatically show up as a vdisk in the virtual disks area.
>>
>> The PERC H710 mini is in HBA mode, not RAID mode, so it's not handling
>> the mirroring.  That's being done at the OS level with Linux's mdadm.
>>
>> This hard drive is part of an mdadm RAID1.  The drive failed completely,
>> so mdadm failed each of the partitions out of the individual MD devices.
>> I removed the failed MD components and then forced the OS to forget about
>> /dev/sdb, with
>>
>> # echo 1 > /sys/block/sdb/device/delete
>>
>> I pulled the failed hard drive from the hot-swap bay, installed the Dell
>> replacement drive in the carrier, and inserted the replacement hard drive
>> into the bay.  The drive LED blinked and went green, and iDRAC shows the
>> physical disk as "Ready", instead of "Online", and the replacement is
>> missing completely from the vdisk area.
>>
>> The OS did not auto-detect a hard drive being added to the bus, and even
>> a rescan via
>>
>> # echo '- - -' > /sys/class/scsi_host/host0/scan
>>
>> does not trigger it to recognize the replacement drive is there.  I'm
>> guessing that's because I need to do something at the PERC/iDRAC/Lifecycle
>> level to get the drive to switch to "Online" and make it a vdisk.
>>
>> How do I go about doing that?
>>
>> We do not currently have any Dell OS-level RPMs installed, so no omsa or
>> srv-admin or whatever.  After being on this list for a couple of years,
>> my confidence in those tools is extremely limited.
>>
>> It seems like 'megaclisas' might be able to help, but I have been
>> completely unable to find a working link to that tool, after the
>> LSI->Avago->Broadcomm transition.  If anyone has a working link to get
>> it, I would appreciate seeing it.
>>
>> Could 'racadm' via ssh perform the necessary magic to get this drive so
>> that the PERC is presenting it as a disk to the OS?  Is there something
>> easier than that, that also doesn't require a huge mess of questionable
>> Dell RPMs be installed?
>>
>> Any suggestions are much appreciated,
>>
>> Tim
>> --
>> Tim Mooney tim.moo...@ndsu.edu
>> Enterprise Computing & Infrastructure  701-231-1076
>> (Voice)
>> Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
>> North Dakota State University, Fargo, ND 58105-5164
>>
>> ___
>> Linux-PowerEdge mailing list
>> Linux-PowerEdge@dell.com
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>
>

-- 
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


Re: [Linux-PowerEdge] [E] replacing a failed hard drive with PERC HBA mode

2017-08-10 Thread Tim Mooney
In regard to: RE: [E] [Linux-PowerEdge] replacing a failed hard drive with...:

> Without having OMSA installed on the server, I believe that you have 3
> options to recreate the vdisk.  You can either use the iDRAC and go to
> the Storage > Virtual Disks and section and select the Create tab.
> This page should allow you to create the vdisk.

A colleague and I looked all over in the iDRAC 7 interface and we cannot
find a "Create" tab anywhere in either the Virtual Disks section or even
the Physical Disks section.  He too was expecting there to be something
exposed by iDRAC that would allow us to do it, but it appears to be
missing for some reason.

Now that you've given me something specific to search on, it looks like
this is just something that's missing from iDRAC 7:


http://en.community.dell.com/techcenter/systems-management/f/4494/t/19499703

I'm following that trail now, to see if I can make that work.

> The other option is to go in through the LC and drill into the storage
> section to create the vdisk. This is my least favorite option.
>
> Lastly, you could use the CRTL-R option during boot to open the Raid
> Controller setup page to re-create the vdisk.

I'm familiar with both of these options.  In this case, it's probably what
I'll end up doing, just to get the replacement drive visible to the OS.

I very much appreciate your response!  It's given me a few different
avenues to pursue.

Tim

> -Original Message-
> From: linux-poweredge-boun...@dell.com 
> [mailto:linux-poweredge-boun...@dell.com] On Behalf Of Tim Mooney
> Sent: Wednesday, August 9, 2017 6:15 PM
> To: linux-poweredge@dell.com
> Subject: [E] [Linux-PowerEdge] replacing a failed hard drive with PERC HBA 
> mode
>
>
> Hi All!
>
> I need to replace a hard drive in a Dell R720 that's running RHEL 6.9.
> The problem is that the replacement drive shows up as "Ready" in the physical 
> disks area of iDRAC, instead of "Online".  It does not automatically show up 
> as a vdisk in the virtual disks area.
>
> The PERC H710 mini is in HBA mode, not RAID mode, so it's not handling the 
> mirroring.  That's being done at the OS level with Linux's mdadm.
>
> This hard drive is part of an mdadm RAID1.  The drive failed completely, so 
> mdadm failed each of the partitions out of the individual MD devices.
> I removed the failed MD components and then forced the OS to forget about 
> /dev/sdb, with
>
>   # echo 1 > /sys/block/sdb/device/delete
>
> I pulled the failed hard drive from the hot-swap bay, installed the Dell 
> replacement drive in the carrier, and inserted the replacement hard drive 
> into the bay.  The drive LED blinked and went green, and iDRAC shows the 
> physical disk as "Ready", instead of "Online", and the replacement is missing 
> completely from the vdisk area.
>
> The OS did not auto-detect a hard drive being added to the bus, and even a 
> rescan via
>
>   # echo '- - -' > /sys/class/scsi_host/host0/scan
>
> does not trigger it to recognize the replacement drive is there.  I'm 
> guessing that's because I need to do something at the PERC/iDRAC/Lifecycle 
> level to get the drive to switch to "Online" and make it a vdisk.
>
> How do I go about doing that?
>
> We do not currently have any Dell OS-level RPMs installed, so no omsa or 
> srv-admin or whatever.  After being on this list for a couple of years, my 
> confidence in those tools is extremely limited.
>
> It seems like 'megaclisas' might be able to help, but I have been completely 
> unable to find a working link to that tool, after the
> LSI->Avago->Broadcomm transition.  If anyone has a working link to get
> it, I would appreciate seeing it.
>
> Could 'racadm' via ssh perform the necessary magic to get this drive so that 
> the PERC is presenting it as a disk to the OS?  Is there something easier 
> than that, that also doesn't require a huge mess of questionable Dell RPMs be 
> installed?
>
> Any suggestions are much appreciated,
>
> Tim
>

-- 
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


Re: [Linux-PowerEdge] replacing a failed hard drive with PERC HBA mode

2017-08-10 Thread Artit Jirapatnakul
Hi,

Does the H710 support HBA mode? I thought it wasn't until the PERC9 series
that HBA mode was supported.

If that's the case, you probably just have to create a RAID0 virtual disk
with the single drive. I guess you could confirm by seeing if you have any
other virtual disks listed in the storage section of the iDRAC.

Art

On Wed, Aug 9, 2017 at 6:14 PM, Tim Mooney  wrote:

>
> Hi All!
>
> I need to replace a hard drive in a Dell R720 that's running RHEL 6.9.
> The problem is that the replacement drive shows up as "Ready" in the
> physical disks area of iDRAC, instead of "Online".  It does not
> automatically show up as a vdisk in the virtual disks area.
>
> The PERC H710 mini is in HBA mode, not RAID mode, so it's not handling
> the mirroring.  That's being done at the OS level with Linux's mdadm.
>
> This hard drive is part of an mdadm RAID1.  The drive failed completely,
> so mdadm failed each of the partitions out of the individual MD devices.
> I removed the failed MD components and then forced the OS to forget about
> /dev/sdb, with
>
> # echo 1 > /sys/block/sdb/device/delete
>
> I pulled the failed hard drive from the hot-swap bay, installed the Dell
> replacement drive in the carrier, and inserted the replacement hard drive
> into the bay.  The drive LED blinked and went green, and iDRAC shows the
> physical disk as "Ready", instead of "Online", and the replacement is
> missing completely from the vdisk area.
>
> The OS did not auto-detect a hard drive being added to the bus, and even
> a rescan via
>
> # echo '- - -' > /sys/class/scsi_host/host0/scan
>
> does not trigger it to recognize the replacement drive is there.  I'm
> guessing that's because I need to do something at the PERC/iDRAC/Lifecycle
> level to get the drive to switch to "Online" and make it a vdisk.
>
> How do I go about doing that?
>
> We do not currently have any Dell OS-level RPMs installed, so no omsa or
> srv-admin or whatever.  After being on this list for a couple of years,
> my confidence in those tools is extremely limited.
>
> It seems like 'megaclisas' might be able to help, but I have been
> completely unable to find a working link to that tool, after the
> LSI->Avago->Broadcomm transition.  If anyone has a working link to get
> it, I would appreciate seeing it.
>
> Could 'racadm' via ssh perform the necessary magic to get this drive so
> that the PERC is presenting it as a disk to the OS?  Is there something
> easier than that, that also doesn't require a huge mess of questionable
> Dell RPMs be installed?
>
> Any suggestions are much appreciated,
>
> Tim
> --
> Tim Mooney tim.moo...@ndsu.edu
> Enterprise Computing & Infrastructure  701-231-1076
> (Voice)
> Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


Re: [Linux-PowerEdge] [E] replacing a failed hard drive with PERC HBA mode

2017-08-10 Thread Kingston, Scott J
Tim,

Without having OMSA installed on the server, I believe that you have 3 options 
to recreate the vdisk.  You can either use the iDRAC and go to the Storage > 
Virtual Disks and section and select the Create tab.   This page should allow 
you to create the vdisk.

The other option is to go in through the LC and drill into the storage section 
to create the vdisk. This is my least favorite option.

Lastly, you could use the CRTL-R option during boot to open the Raid Controller 
setup page to re-create the vdisk.

Personally, I've had very good luck using the omsa tools and perform this 
function right from the linux command line.

Best Regards,
Scott

-Original Message-
From: linux-poweredge-boun...@dell.com 
[mailto:linux-poweredge-boun...@dell.com] On Behalf Of Tim Mooney
Sent: Wednesday, August 9, 2017 6:15 PM
To: linux-poweredge@dell.com
Subject: [E] [Linux-PowerEdge] replacing a failed hard drive with PERC HBA mode


Hi All!

I need to replace a hard drive in a Dell R720 that's running RHEL 6.9.
The problem is that the replacement drive shows up as "Ready" in the physical 
disks area of iDRAC, instead of "Online".  It does not automatically show up as 
a vdisk in the virtual disks area.

The PERC H710 mini is in HBA mode, not RAID mode, so it's not handling the 
mirroring.  That's being done at the OS level with Linux's mdadm.

This hard drive is part of an mdadm RAID1.  The drive failed completely, so 
mdadm failed each of the partitions out of the individual MD devices.
I removed the failed MD components and then forced the OS to forget about 
/dev/sdb, with

# echo 1 > /sys/block/sdb/device/delete

I pulled the failed hard drive from the hot-swap bay, installed the Dell 
replacement drive in the carrier, and inserted the replacement hard drive into 
the bay.  The drive LED blinked and went green, and iDRAC shows the physical 
disk as "Ready", instead of "Online", and the replacement is missing completely 
from the vdisk area.

The OS did not auto-detect a hard drive being added to the bus, and even a 
rescan via

# echo '- - -' > /sys/class/scsi_host/host0/scan

does not trigger it to recognize the replacement drive is there.  I'm guessing 
that's because I need to do something at the PERC/iDRAC/Lifecycle level to get 
the drive to switch to "Online" and make it a vdisk.

How do I go about doing that?

We do not currently have any Dell OS-level RPMs installed, so no omsa or 
srv-admin or whatever.  After being on this list for a couple of years, my 
confidence in those tools is extremely limited.

It seems like 'megaclisas' might be able to help, but I have been completely 
unable to find a working link to that tool, after the
LSI->Avago->Broadcomm transition.  If anyone has a working link to get
it, I would appreciate seeing it.

Could 'racadm' via ssh perform the necessary magic to get this drive so that 
the PERC is presenting it as a disk to the OS?  Is there something easier than 
that, that also doesn't require a huge mess of questionable Dell RPMs be 
installed?

Any suggestions are much appreciated,

Tim
-- 
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.us.dell.com_mailman_listinfo_linux-2Dpoweredge=DwICAg=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=sZA28jIebnZqNAL0vpYk2d6QxpNmuA4geqEmLP6D8ow=82TxaQbJOMVzeljnbvq5r-zW_CuQtGC5OAd5jupPX5k=VZCI5Y3JSZjjmFrYtVFxNqudRSycdwpEQtBs2x1tuaA=
 

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


Re: [Linux-PowerEdge] Enough contiguous physical memory is not available to perform the BIOS update running under, this Operating System.

2017-08-10 Thread john
Just had this same issue with the latest SUU for R710. Any update on 
fixing this bug?

Server is out of warranty.

Thanks,

John

On Thu, 8 Jun 2017, sash...@dell.com wrote:

> Date: Thu, 8 Jun 2017 07:50:08 +
> From: sash...@dell.com
> To: linux-powere...@lists.us.dell.com
> Subject: Re: [Linux-PowerEdge] Enough contiguous physical memory is not
> available to perform the BIOS update running under, this Operating System.
> 
> Hi,
>
> We've checked with the dependent team regarding the problem you faced and the 
> suggestion was to reboot the system to release contiguous memory.
> However, if you still face the issue after reboot, we advise you to please 
> get in touch with Dell Technical Support.
>
> Regards,
> Sashi
> sash...@dell.com
>
> From: linux-poweredge-bounces-Lists On Behalf Of Malte Schmidt
> Sent: Sunday, June 4, 2017 7:43 PM
> To: linux-poweredge-Lists 
> >
> Subject: Re: [Linux-PowerEdge] Enough contiguous physical memory is not 
> available to perform the BIOS update running under, this Operating System.
>
>
> Just a kind reminder that this problem is not solved yet.
>
> Is there any update on this?
>
> Best regards
>
> On 01/18/2017 09:10 PM, Vincent Hoffman-Kazlauskas wrote:
>
> Just a me too, but I was running dsu from a standard install not a
>
> liveCD, I rebooted and tried again a few times just in case.
>
> A centos6 livecd on the same box worked fine.
>
>
>
> Vince
>
>
>
> On 18/01/2017 18:24, Malte Schmidt wrote:
>
> Running dsu on CentOS 7 (live, the DSET-iso), i am getting the following
>
> error even after 3 reboots.
>
>
>
> Questions: Is this an known issue? How to fix it?
>
>
>
> [*]1 BIOS
>
> Current Version : 2.2.10 Upgrade to : 6.4.0
>
>
>
> [...]
>
>
>
> Enter your choice : c
>
> Fetching R610_BIOS_C6MRW_LN_6.4.0 ...
>
> Installing R610_BIOS_C6MRW_LN_6.4.0 ...
>
> Collecting inventory...
>
> .
>
> Running validation...
>
>
>
> BIOS
>
>
>
> The version of this Update Package is newer than the currently installed
>
> version.
>
> Software application name: BIOS
>
> Package version: 6.4.0
>
> Installed version: 2.2.10
>
>
>
>
>
> Executing update...
>
> WARNING: DO NOT STOP THIS PROCESS OR INSTALL OTHER DELL PRODUCTS WHILE
>
> UPDATE IS IN PROGRESS.
>
> THESE ACTIONS MAY CAUSE YOUR SYSTEM TO BECOME UNSTABLE!
>
> .
>
> Device: BIOS
>
>  Application: BIOS
>
>  Enough contiguous physical memory is not available to perform the BIOS
>
> update running under
>
>  this Operating System. Reboot and try again.
>
>
>
> R610_BIOS_C6MRW_LN_6.4.0 could not be installed
>
>
>
> Done! Please run 'dsu --inventory' to check the inventory
>
>
>
>
>
>
>
> ___
>
> Linux-PowerEdge mailing list
>
> Linux-PowerEdge@dell.com
>
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>
>
>
>
>
>
>
> ___
>
> Linux-PowerEdge mailing list
>
> Linux-PowerEdge@dell.com
>
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>
>

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge