Start a Conversation

Solved!

Go to Solution

706

May 21st, 2020 23:00

r210ii will not boot - MAS001partition not found - stuck.

Hey, all.  First time post here.  Glad to be here - looks like a very helpful community.  Be gentle

So after a failed memory upgrade from 2x4GB to 4x4GB (one stick of the new pair was bad), I started to have problems getting this previously working r210ii to boot. 

The biggest issue I see, selecting F10 gives me:

"MAS001 partiton not found!  

Unable to launch System Service image.

System halted!"

In the boot manager, in either UEFI or BIOS mode, I used to be able to select from HDD or USB devices.  Now I only have one option for each of HDD and Network boots - and either immediately fails with "Boot Failed."

Also same with the F12 option to boot PXE - immediate failure, no attempts at DHCP discovery as it would normally perform in the past.

System does have both iDrac Ethernet and Express devices and I can log into the iDrac web interface.  I have applied the LC_Repair_Package_1.7.5.4_A00.usc through the iDrac web interface serveral times and it makes no difference.

I have also tried removing the iDrac ethernet and Express devices.  Booted with nothing but a single RAM stick, power and VGA attached... cleared FLEA... waited 10 minutes with no power... waited 10 minutes after connecting power before powering on... all the things I've found via Google.

I'm pretty much out of options at this point.  I cannot boot any media at all - would love to try updating the BIOS but I can't even boot a simple DOS image.

 Ideas of what I can try next?

    

Moderator

 • 

790 Posts

May 22nd, 2020 06:00

Hi repulsor,

 

well, you did pretty much all the necessary steps to get the USC back to work, good job.
The fact that it did not solve the issue shows that the flash seems to be corrupted somehow. 

From what I see, the only way to get the system back working is to get a replacement motherboard.

 

You might search for a part with that Dell part number F9NPY or even the whole Service Kit: MY04J.

 

Best regards,
Stefan

4 Operator

 • 

3K Posts

May 22nd, 2020 08:00

You can try updating iDRAC using web interface and see whether it make any difference. Are you able to boot using an bootable USB key inserted to the server. If yes can you flash BIOS using bootable USB key. You can also try booting the server after removing iDRAC6 Express Card and iDRAC6 Enterprise Card 

 

5 Posts

May 22nd, 2020 21:00

I'll answer my own question.  I see that one can download the EXE files and uncompress them to get at the raw updates that can be uploaded through the iDRAC web interface.  Will try and report my results soon.

5 Posts

May 22nd, 2020 21:00

I was able to upload and apply the firmimg.d6 file from the payload directory of the iDRAC Update EXE package.

While it did complete with success, it did not restore the System Services image.  Still no luck booting from any network or media.

5 Posts

May 22nd, 2020 21:00

well, that's a bummer - but seeing as I've done everything, I'll get to shopping.  

Thanks for the advice.

5 Posts

May 22nd, 2020 21:00

I don't see that I can update from anything but the recovery .usc file in the iDRAC web interface.  If there is another file I can use, please do point me in the right direction.

I removed both the iDRAC Ethernet and Express cards and the behavior is unchanged. 

I cannot boot from USB stick.  I never get the option to select anything but the first EFI drive (no matter wether I select BIOS or UEFI in the Boot Manager)

Moderator

 • 

790 Posts

May 25th, 2020 02:00

Hey repulsor,

 

it's new to me, that updating the iDRAC could bring back also the system service image. But still it sounds weird that you are not able to boot from any device, no USB thumb drive, no disc no network, nothing. 
I don't know what happened when you installed the memory - as you mentioned, the system worked before and after the removal of the defective memory this error occurred first.

For me this sounds that something got damaged on the mainboard whilst the installation of the memory module.

 

I still recommend the mainboard replacement.

 

Best regards,
Stefan

No Events found!

Top