Data Recovery Case File · NAS & Network Storage · The Same Failure on Repeat
A Repeating Start-Up Cycle Is a Unit Reaching the Same Point and Restarting
His enquiry describes a loop in unusual detail. A network unit that will not finish starting, where "the drive spins up and it sounds like data is being read, the indicator continues flashing, the drive sounds like it slows down and the whole process repeats" — and he switches it off after a while out of concern about heat. That cycle is one failure happening over and over, and each repetition is another attempt at the region that is failing.
| Media | Single-drive network storage unit — start-up sequence commencing, reading audibly, decelerating and repeating without completing; unit powered off by the owner to limit heating |
| Reported situation | Network unit failing to complete its start-up process · drive spinning up and reading audibly · start-up indication continuing without resolving · drive audibly decelerating · sequence repeating from the beginning · indicator eventually remaining lit · unit switched off by the owner out of concern about heating · content required |
| Fault class | Unit start-up failing at a consistent point — system region unreadable with repeated attempts; drive otherwise rotating and responding |
| Equipment used | Repeating cycle interpreted as one failure recurring rather than progressive deterioration · no further powering of the unit permitted · drive removed and read independently of the unit on a controlled bench supply · imaged write-blocked under strict per-sector timeouts with system regions revisited across passes · native volume format interpreted from the image |
The decode: what the unit is doing each time round
How a network unit starts: by reading its own operating software from a system area on the drive. That software is what runs the unit, serves its shares and drives its indicators, and nothing else can happen until it loads.
What the audible reading represents: that attempt in progress. The drive is being asked for the system area and is trying to deliver it, which is why he can hear activity rather than silence.
What the deceleration and restart represent: the attempt failing. A unit that cannot load its software has no way to report the problem, so it resets and begins again — which is the only response available to it.
Why the repetition is the important observation: the same failure is recurring. A unit reaching a different point each time would suggest something progressive; reaching the same point suggests one unreadable region.
Why that region is likely small: the unit's operating software occupies a modest partition. User content sits in a separate and much larger area the start-up sequence never reaches.
Why that is the encouraging part: the failure is in the part that runs the unit, not the part that holds his files. A unit that cannot start says nothing about whether the content behind it is readable.
Why each cycle nonetheless costs something: every repetition re-reads the same failing region. Repeated reading of a marginal area is precisely what turns it unreadable, and a unit left to loop does that indefinitely.
Why his decision to switch it off was right: he stopped the loop. The concern about heat was sound and the effect was better than he knew — it also stopped the repeated reading.
Why the unit should not be started again to try: it will do the same thing. The cycle is deterministic rather than a matter of luck, and another attempt gains nothing while spending the drive.
What is done instead: the drive comes out and is read directly, bypassing the unit's start-up entirely. The user area is imaged without the system area ever needing to load, and the unit's own volume format is interpreted from the image.
On the bench
The repeating cycle was interpreted as one failure recurring rather than progressive deterioration — network units loading operating software from a system area on the drive before anything else can proceed, so audible reading indicates that attempt in progress and deceleration with restart indicates its failure, a unit having no other way to respond. Reaching the same point each time indicates a single unreadable region, while user content occupies a separate and larger area the sequence never reaches. The drive was read independently of the unit.
The outcome
The cycle interpreted as one recurring failure, no further powering of the unit permitted, and the drive read independently under capped timeouts. 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: switching it off was the right call for a better reason than you knew. Each cycle re-read the same failing region — and that region holds the software that runs the unit, not your files.
A network unit stuck in a start-up loop
Leave it switched off rather than trying again — the cycle is deterministic rather than a matter of luck, and each repetition re-reads the same failing region, which is precisely what turns a marginal area unreadable. What you're hearing is the unit trying to load its own operating software from a system area on the drive, failing, and resetting because it has no other way to respond. That area is small and separate from where your content sits, so a unit that can't start tells you nothing about whether your files are readable. The drive comes out and reads directly.
Leave it off — call Manchester Data Recovery on 0161 871 0788; cycle interpreted as one recurring failure, drive read independently of the unit, system regions revisited across passes.
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.