Joshuacurtis1

Caliburger, a fast food chain has today seen the end to a long term dream of an automated burger flipping robot with Flippy taking orders at it's Pasadena restaurant, the chain eventually wants the robots in 50 of its stores.

Creator Miso Robotics drummed up 14 million dollars in investment to fund the development of Flippy
Over time Miso hope that Flippy can be taught how to chop, fry, grill, add cheese and even season food
At $60,000 a pop he's not a cheap as a burger chef yet however Miso point out his price will fall in time plus he will save money in other areas such as food waste
https://techcrunch.com/2018/03/05/flippy-the-robot-hamburger-chef-goes-to-work/
 
This raises some interesting questions for me, in 10 years when all fast food restaurants have Flippies what do all the people who no longer have jobs do for work?

The image is prompting you to insert a boot device. This could be the installation media, or it could be a HDD with Windows Server 2000 already working. Basically, that image just means "no boot device found".
 
Second: Repairing the RAID and using the Windows 2000 installation Media are two totally different and unrelated things (Depending on how RAID was setup).
 
If RAID was setup using built-in motherboard RAID, OR through a Hardware RAID card, you'll need to repair the RAID array BEFORE doing anything with the Installation Media.
 
I do not believe that Windows can create a bootable RAID1 Mirror that has the OS on it, so odds are, the RAID Array was created using Motherboard BIOS, or a hardware RAID card.
 
You'll need to figure out which first before doing anything with the installation media. Because you see a prompt about RAID configuration, I'm leaning towards a Hardware RAID Card.
 
Enter the RAID Configuration page, and look at the array status (Probably "degraded"). Find out which disk dropped out of the array - replace with a comparable disk (same model ideally, if not, same RPM and same capacity). Once replaced, start a rebuild.
 
After the rebuild is complete, restart the server and see if it just boots up normally.

You must be young.
 
That's a Floppy Disk - the server is basically saying "no boot device found", and is asking you to insert a boot drive (via Floppy, but you can no doubt use any boot device, including CD/DVD - possibly USB, if a server that old even supports USB Boot).
 
If a drive has failed, you likely need to rebuild the array.
 
When the computer boots, does it flash on the screen a RAID configuration option? Normally you press Ctrl + C to open it.
 
You need to replace the bad drive, then start the rebuild.
 
If the array cannot be recovered, you'll need to replace any bad drives, create a new RAID array, and reinstall from scratch.
 
Hopefully you've been backing up any important data...

1. To check that a HDD has actually failed, you'll need to run a HDD testing software on it. Each HDD manufacturer has their own tool for that - eg: SeaGate SeaTools, WD Data Lifeguard, etc. So find out what HDD make it is first. You can plug the drives into another computer, load up the software, and run a long self test (non-destructive). It'll check for bad sectors, read errors, etc.
 
2. You need to check that RAID Configuration prompt you saw earlier. It should clearly list any Arrays created (working or degraded). Take some pictures and post here if you're not sure what you're looking at.
 
3. The rebuild process entirely depends on how the RAID array was created, and what brand (Eg: LSI vs Adaptec, etc). If you can answer question 2 first, that'll help you figure out question 3. Generally, you select the array, and there should be a "rebuild" option or button.

Update: I removed the drives from the server, then reinserted them and it booted correctly, with all volumes and data shown correctly... Bizzare but I'm not going to question it. Thank you for all your help, and the information you provided, it will allow me to do much more in the future!

Sometimes a perfectly functional disk can get dropped out of an array if, for example, it takes too long to respond to the RAID controller, or encounters some other hiccup.
 
It's also possible the RAID controller tried to write to a bad sector. A few bad sectors are normal for an old drive - HDD's have spare sectors that are used to remap the bad ones, but there's only a small number of spare sectors. Once the spares get used up, the drive is basically dying.
 
Any bad sectors generally point to a drive that's aging, and should be replaced soon though - personally, I'll replace a drive as soon as any bad sectors are discovered. You can use a drive with bad sectors for non-critical stuff, but don't put anything important on them.

Hey everyone. First of all, I really enjoy LTT content.
So there was one thing i was thinking about, that might be a cool idea for a project:

What to do with your old, but still 100% functional smartphones?
Many can be jailbroken or rooted, so they can literally run any software. They come with built-in wifi, 3g, bluetooth, camera, etc...
So why not turn them into IoT devices or other gadgets? 
 
for example: an old smartphone has a way better desing than a raspberry pi with the the camera attatched. plus it has an internal battery