Data Recovery Case File · Legacy & Obsolete Media · No Room to Work
A System Needs Free Space to Start, and a Nearly Full Drive May Not Have It
His enquiry contains two details that fit together. An older laptop whose drive was "nearly full after years of use", which "worked fine until I left it unused for a couple of months — now won't start." Neither detail alone explains much and together they suggest a great deal: a system start is a writing operation, and a drive with almost nothing left has nowhere to write.
| Media | Laptop hard drive of an earlier generation, reported nearly full after extended use — machine not starting following a period of disuse |
| Reported situation | Older laptop in extended service · hard drive nearly full · machine functioning normally before storage · machine left unused for approximately two months · machine no longer starting · safe mode attempted without result · original installation media no longer held · personal files and photographs required |
| Fault class | Start-up failure with free space exhaustion indicated — system unable to complete required writes; drive condition after disuse to be assessed separately |
| Equipment used | Free space exhaustion considered alongside device failure before either was assumed · drive removed and read independently of the machine · current draw measured on a controlled bench supply · imaged write-blocked at the block level before any interpretation · user content extracted from the image with system files excluded |
The decode: two explanations, both worth testing
Why a system start involves writing at all: it is not a read-only operation. The system writes logs, creates temporary files, expands a paging area and updates its own state before it reaches a usable desktop.
What happens when there is no room for that: the start fails partway. A system that cannot write its working files stops rather than continuing without them, and the failure often presents without a clear message.
Why a nearly full drive can work for years and then not: the margin shrinks gradually and the requirement varies. An update that needs a little more space than usual is enough to cross the line, and the failure arrives without warning.
Why safe mode failing does not settle it: a reduced start-up still writes. It loads fewer components and still requires working space, so a space problem defeats it as readily.
What the second explanation is: the drive itself. A machine left unused for months and then failing to start fits a drive that has developed a fault during the interval or during the restart.
Why the interval is relevant to that: board components age with elapsed time, and heads left resting can adhere to the surface. An older drive that stops and sits is at its most vulnerable at the next start.
Why the two are distinguishable without guesswork: the drive comes out and is read on its own. A drive that images cleanly points at the space problem; one that struggles points at itself.
Why that ordering suits his objective anyway: he wants his files, not a working machine. Reading the drive independently delivers the content regardless of which explanation is correct.
Why the missing installation media matters less than he thinks: restoring the machine would need it and recovering his content does not. The files come off the drive without any system being reinstalled.
What must not happen: no repeated attempts to start. If the drive has developed a mechanical fault, each attempt is another one — and if it has not, the space problem will not resolve itself either.
On the bench
Free space exhaustion was considered alongside device failure before either was assumed — system start-up writing logs, temporary files, paging area and state before reaching a usable desktop, so a drive without room fails partway and often without a clear message, while reduced start-up modes still require working space. Separately, board components age with elapsed time and resting heads may adhere, leaving an older drive most vulnerable at the next start. The drive was read independently of the machine.
The outcome
Both explanations considered before either was assumed, the drive read independently with draw measured, and user content extracted with system files excluded. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: your two details fit together. Starting a system is a writing operation, and a nearly full drive may have no room for it — though a drive left resting for months is also at its most vulnerable at the next start.
A machine that will not start on a nearly full drive
Stop attempting to start it, and have the drive read on its own rather than trying to fix the machine — you want the files, and reading the drive delivers them whichever explanation is right. Two are plausible together. Starting a system writes logs, temporary files and a paging area before it reaches a desktop, so a drive with almost no room can fail partway without a clear message, and safe mode writes too. Separately, an older drive left resting for months is at its most vulnerable on the next start. Missing installation media doesn't affect recovery.
Stop trying to start it — call Manchester Data Recovery on 0161 871 0788; free space exhaustion considered alongside device failure, drive read independently, user content extracted with system files excluded.
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.