You mentioned a local CD/DVD option, which we do have premade. I'll link to it below. This utility does include updates to the Lifecycle Controller, the BIOS, and the iDRAC. It should flash everything in the chassis to the latest revisions. That having been said, there will be a lot of skipped packages, because it would have updates to any supported hardware that could be installed in the system. Running this package will probably take around an hour, but may potentially take longer. It really depends on how many updates get applied and how many get skipped. Repository Manager does let you build a custom .ISO, so that may also be an option for you.
Just to confirm, this utility can be downloaded and burned onto a disc which we can then insert into the CD/DVD drive on the server and boot from the disc? Are there any additional steps on top of that? Will give it a shot and keep you posted here.
The process is a super simple one, essentially fire and forget. The system would boot to the image, and the image automatically kicks off a shell script to run updates. There's not really any human interaction needed. It's sort of one of those things where you verify that it boots and kicks off with the updates, then break for lunch. Generally, it's about done when you come back.
You'll still need to load drivers, since this utility only touches firmware. But, it should have the OS driver pack loaded in there. My expectation is that upon completion, you should be able to use the LCC and install the OS. Worst case scenario would be to grab your PERC driver, extract the payload, and place the contents onto a USB so that you can provide it to Windows at the "Where do you want to install Windows" screen, but my expectation is that you won't need to do that.
I'm glad to hear the updates went smoothly, but the install issues are certainly puzzling. You might consider reinstalling again, just in case the issue was just some weird one-off type problem. One thing that I try when running into issues is to not just reinstall, but to actually delete and create a new virtual disk and let it run a background initialization. That way, it's coming with as clean a slate as possible. It's best to do this after determining if you want to use BIOS or UEFI boot mode.
The update utility worked like a charm. The BIOS and LCC were successfully installed. I had to manually install the OS Driver Pack (via LCC) but that also went through successfully.
I attempted to install Windows 2012R2 and went through the initial installation just fine:
-Initiated OS Deployment through the LCC and selected the 2012R2 drivers. Initial Windows installation screens appear and installation of files went through flawlessly but just when I thought I was in the clear, after performing the first reboot, I would get greeted with a black screen with the "Windows Boot Manager" title, stating, "Windows failed to start. A recent hardware or software change might be the cause."
If it means anything, I booted using UEFI as the boot mode. With the BIOS, LifeCycle Controller,and OS Driver Pack updated and current, I have no idea why I'm still getting errors...
For sake of testing, I'd go ahead and toggle the boot mode from UEFI to BIOS mode. If you intend on keeping the OS and data volume separate, you may very well be fine using that mode anyway.
To answer your question, no, I don't believe the PERC firmware would play into this. It could certainly stop the storage from presenting to the installer at all, but we're seeing a different behavior.
Went ahead and tried to re-install with no success. I can confirm that the OS is being installed since there was a Reserved and Primary partition from the previous failed install on the "Where do you want to install Windows" screen. At that point, I rebooted the server and recreated the virtual disks. They are now performing a background initialization. Will attempt to install once they are complete. Would the PERC firmware version be a factor? Our current PERC BIOS version is at 2.04.00.
After testing both modes, the same result would come up. So I chose to go with UEFI since it is compatible with the OS and for the enhanced security. One thing I might be messing up on is at the "Where do you want to install Windows" screen. At that screen, I'm selecting the only drive that's available (Drive 1, Unallocated Space) and clicking continue. Not sure if I'm supposed to be loading a driver instead. Currently, the virtual disks have been initialized and the OS is installing. Hoping it gets past the reboot..
The link https://dell.app.box.com/v/bootabler710/folder/60646213395 no longer works. Where is a working and bootable iso file? I've heard something about making your own repository, but that sounds extremely complex for something that should be simple. If the repository route is the only option, does someone have detailed tutorial on how to do this? I really don't know where to begin. Frustrating.
Dell-DylanJ
4 Operator
•
2.9K Posts
1
March 19th, 2019 10:00
Hi Nick,
You mentioned a local CD/DVD option, which we do have premade. I'll link to it below. This utility does include updates to the Lifecycle Controller, the BIOS, and the iDRAC. It should flash everything in the chassis to the latest revisions. That having been said, there will be a lot of skipped packages, because it would have updates to any supported hardware that could be installed in the system. Running this package will probably take around an hour, but may potentially take longer. It really depends on how many updates get applied and how many get skipped. Repository Manager does let you build a custom .ISO, so that may also be an option for you.
Let me know if this helps out.
https://dell.app.box.com/v/bootabler710/folder/60646213395
Nick58
1 Rookie
•
9 Posts
0
March 19th, 2019 11:00
Hi Dylan,
Thank you for the very fast response!
Just to confirm, this utility can be downloaded and burned onto a disc which we can then insert into the CD/DVD drive on the server and boot from the disc? Are there any additional steps on top of that? Will give it a shot and keep you posted here.
Thank you again!
Dell-DylanJ
4 Operator
•
2.9K Posts
0
March 19th, 2019 11:00
The process is a super simple one, essentially fire and forget. The system would boot to the image, and the image automatically kicks off a shell script to run updates. There's not really any human interaction needed. It's sort of one of those things where you verify that it boots and kicks off with the updates, then break for lunch. Generally, it's about done when you come back.
Nick58
1 Rookie
•
9 Posts
0
March 19th, 2019 12:00
Awesome! I'm about to run it now. After it is done, would we then be able to load Server 2012R2 or would there by any additional steps in between?
Dell-DylanJ
4 Operator
•
2.9K Posts
0
March 19th, 2019 13:00
You'll still need to load drivers, since this utility only touches firmware. But, it should have the OS driver pack loaded in there. My expectation is that upon completion, you should be able to use the LCC and install the OS. Worst case scenario would be to grab your PERC driver, extract the payload, and place the contents onto a USB so that you can provide it to Windows at the "Where do you want to install Windows" screen, but my expectation is that you won't need to do that.
Dell-DylanJ
4 Operator
•
2.9K Posts
0
March 20th, 2019 10:00
I'm glad to hear the updates went smoothly, but the install issues are certainly puzzling. You might consider reinstalling again, just in case the issue was just some weird one-off type problem. One thing that I try when running into issues is to not just reinstall, but to actually delete and create a new virtual disk and let it run a background initialization. That way, it's coming with as clean a slate as possible. It's best to do this after determining if you want to use BIOS or UEFI boot mode.
Nick58
1 Rookie
•
9 Posts
0
March 20th, 2019 10:00
Dylan,
The update utility worked like a charm. The BIOS and LCC were successfully installed. I had to manually install the OS Driver Pack (via LCC) but that also went through successfully.
I attempted to install Windows 2012R2 and went through the initial installation just fine:
-Initiated OS Deployment through the LCC and selected the 2012R2 drivers. Initial Windows installation screens appear and installation of files went through flawlessly but just when I thought I was in the clear, after performing the first reboot, I would get greeted with a black screen with the "Windows Boot Manager" title, stating, "Windows failed to start. A recent hardware or software change might be the cause."
If it means anything, I booted using UEFI as the boot mode. With the BIOS, LifeCycle Controller,and OS Driver Pack updated and current, I have no idea why I'm still getting errors...
Dell-DylanJ
4 Operator
•
2.9K Posts
0
March 20th, 2019 11:00
For sake of testing, I'd go ahead and toggle the boot mode from UEFI to BIOS mode. If you intend on keeping the OS and data volume separate, you may very well be fine using that mode anyway.
To answer your question, no, I don't believe the PERC firmware would play into this. It could certainly stop the storage from presenting to the installer at all, but we're seeing a different behavior.
Nick58
1 Rookie
•
9 Posts
0
March 20th, 2019 11:00
Nick58
1 Rookie
•
9 Posts
0
March 20th, 2019 12:00
Nick58
1 Rookie
•
9 Posts
1
March 20th, 2019 13:00
The install was able to complete after I re-created the virtual disks like you suggested. Thank you for all the help Dylan! You da man!
Sincerely,
Nick
Dell-DylanJ
4 Operator
•
2.9K Posts
0
March 20th, 2019 13:00
Very glad that did it for you, Nick!
dellymanny3
1 Message
0
December 6th, 2019 16:00
The link https://dell.app.box.com/v/bootabler710/folder/60646213395 no longer works. Where is a working and bootable iso file? I've heard something about making your own repository, but that sounds extremely complex for something that should be simple. If the repository route is the only option, does someone have detailed tutorial on how to do this? I really don't know where to begin. Frustrating.
cobe18
3 Posts
0
February 12th, 2020 00:00
Yes same issue here and R710 no longer listed in Dell Repository Manager catalog, so not sure where to get updates from or build iso.
jdkillian
2 Posts
0
February 12th, 2020 18:00
Looks like Im needing this as well. Appears to be a dead link