Data Recovery Case File · Solid State & Flash · Falling Through the Boot Order
That Message Means It Ran Out of Places to Look
His enquiry quotes a start-up message that looks alarming and is simply descriptive. After the screen froze, restarting produces "a message along the lines of check cable connection, then a network boot attempt." He took the machine to the shop where he bought the drive and they could not recover the data, though they can see the drive. Nothing there is about a cable — the machine looked for something to start from, found nothing, and fell through to the last option in its list, which is the network.
| Media | Solid-state system drive — machine failing to locate a bootable device and attempting network start-up; drive reportedly visible to a third party |
| Reported situation | Machine freezing during use · restart producing a message regarding cable connection followed by a network boot attempt · assessed by the retailer without recovery · drive reportedly detectable · contents required |
| Fault class | No bootable device located with the drive still enumerating — filesystem or boot structure damage rather than device absence |
| Equipment used | Previous provider's methods and any write activity established before assessment · drive assessed on a direct connection with enumeration confirmed separately from readability · imaged write-blocked before any reconstruction · boot and filesystem structures rebuilt from surviving copies on the image |
The decode: what the machine was actually doing
How a computer decides what to start from: its firmware holds an ordered list — try the internal drive, then a USB device, then an optical drive, then the network. It works down that list and starts from the first thing that offers a bootable system. The list almost always ends with the network, because that is how machines are set up remotely in offices, and it is enabled by default on a great many computers.
So what he is seeing: the firmware asked the drive for a bootable system and did not get one, moved on through the other options, and arrived at the last entry. The network attempt is not a fault — it is the machine faithfully doing the final thing on its list. The message about a cable is that attempt failing too, because there is no network boot service to answer it.
Why that message is more informative than it looks: reaching the end of the boot order means the firmware got a clear answer from every earlier option. It did not hang on the drive; it moved past it. That is consistent with a drive that responds normally and simply has no bootable system on it — which matches the report that the drive can be seen.
What that separates: a drive that has failed as a device is a different case from a drive that is present and has no bootable system. The second is much better — the drive works, the filesystem or boot structures are damaged, and the data sits behind them.
Why the freeze is the likely cause: a system that froze and was restarted was interrupted with work outstanding. Where that interruption catches boot structures or the filesystem mid-update, they are left in a state the firmware cannot use — and the machine falls through the boot order exactly as described.
Why the retailer's failure is not the end of it: a shop recovers data by connecting a drive and running consumer software. Where that returns nothing, it says the tool was unequal to the situation rather than that the data is gone. Worth asking what was run and whether anything was written — particularly whether a repair or reinstall was attempted, since either changes the position.
What must not happen: no reinstall and no boot repair. Both write to precisely the structures a reconstruction reads.
On the bench
The previous provider's methods and any write activity were established before assessment, a boot repair or reinstall attempt changing what remains possible. The drive was assessed on a direct connection with enumeration confirmed separately from readability — a machine reaching the end of its boot order having received clear answers from earlier options rather than hanging, which indicates a present drive with no bootable system rather than a failed device. Imaging ran write-blocked before any reconstruction, with boot and filesystem structures rebuilt from their surviving copies on the image.
The outcome
The prior handling established, enumeration confirmed separately from readability and the structures rebuilt from the image. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: your firmware holds an ordered list of places to start from and works down it, and that list nearly always ends with the network. So a network boot attempt means it tried everything else first and got clear answers — it did not hang on your drive, it moved past it.
Machine attempting a network boot at start-up
That message isn't about a cable and isn't a new fault. Your firmware holds an ordered list of places to look for a system to start from — internal drive, USB, optical, then the network — and it works down that list until something answers. Nearly every machine has the network as the last entry, enabled by default, because that's how computers get set up remotely in offices. So a network boot attempt means the firmware asked your drive, got no bootable system, moved past it, and reached the end of the list. That's actually encouraging: it means the drive answered rather than hanging, so it's present with damaged boot structures rather than failed as a device. Don't let anyone reinstall or run a boot repair.
Don't reinstall — call Guildford Data Recovery on 01483 901310; prior handling established first, enumeration confirmed separately from readability, structures rebuilt from their surviving copies on the image.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.