Lenovo ST150 Dead Board How to Move Your Data to Another Server
When the board is hopeless — or the server is being replaced anyway — the data still has to come home. This page gives the safe order: read the disks according to your RAID level, image before experimenting when it matters, copy with verification, and rebuild the shares and permissions everyone forgets.
✍️ Technical Anshu🖥️ Lenovo ThinkSystem ST150⏱️ Half a day for a careful move
🎥 Watch the ST150 fix guide in the video — and see why the data usually survives the board
The board is dead and the decision is made — repair is not happening, or not happening fast enough. What remains is the job that actually matters to everyone waiting: getting the data off the disks and onto a working server, complete and usable. This is a calmer job than it feels. Disks outlive boards routinely, mirrors can be read directly, and even striped sets have a proper road home. The pages below walk it in order, including the unglamorous half — shares, permissions and verification — that separates a data move from a data rescue.
Dead board, live data — the move in order
Recover access first
Read the disks on a bench PCRAID 1 and single disks read directly
Identical board or same controllerFor multi-disk RAID 5 and 10 sets
Disk image before experimentsThe safety copy of everything
Then move house
Copy data, verify counts and spot filesNever move by faith
Rebuild shares and permissionsThe part everyone forgets
Keep the old disks untouched for weeksYour rollback plan
👆 A dead board almost never means dead data. The order is: read the disks safely, copy with verification, and keep the originals untouched until the new home has earned trust.
1
Start From the Reassuring Fact
A motherboard failure destroys a computer, not the information inside it. The ST150's disks hold your data independently of the board, and the board dying — even dramatically — rarely touches them. Your job is to read those disks in the safest possible order and land the data on a working machine, whether that is a repaired ST150, a replacement tower, or temporary storage while you decide. Panic is the only real enemy here: most data losses in dead-server stories happen during rushed experiments, not during the original failure.
2
Reading the Disks — What Your RAID Level Allows
Single disk or RAID 1 (mirror): the friendliest cases. A mirror member holds a complete copy of everything, and it can usually be attached to another Windows or Linux machine — or a USB dock — and read directly. Work from one member only and keep the other untouched as your spare copy.
RAID 5 or RAID 10: the data is striped across the set, so the disks must be read together by a compatible controller — realistically the repaired or replacement ST150 board (the board-swap page covers that happy path), or recovery software that can assemble the array virtually. Do not format, initialise or "repair" individual members.
RAID 0: said plainly — striping without redundancy means the set works whole or not at all. If every member still spins and reads, recovery software may assemble it; if one member is dead, the data is effectively gone and professional recovery is the only remaining door.
3
Image First When the Data Really Matters
If this server held the only copy of business data, make disk images before any recovery attempt — clone each drive to a file or a same-size disk using imaging software, and do all experiments against the images. Imaging is slow and needs spare capacity, which is exactly why it gets skipped, and exactly why its absence gets regretted. For a simple mirror or single disk with a healthy drive, a plain verified file copy is a reasonable shortcut; for striped arrays and clicking or erroring disks, images first is not caution, it is the method.
4
Landing on the New Server — The Forgotten Half
Copying the files is the visible half of the move; the invisible half is what makes them useful again:
Recreate the shares and permissions. Data that arrives without its access rules is a Monday-morning problem for the whole office — note the old share names and who could see what, from documentation or the recovered system itself.
Verify the copy properly: file counts and total size compared, and a human opening a sample of real files — documents, the accounts database, the application data — not just green progress bars.
If the server ran an application or database, restore it the application's way (its own backup/restore or data-folder procedure) rather than assuming raw file copies are enough.
Keep the original disks untouched and labelled for at least a few weeks after the move. They are your rollback when someone discovers, on day nine, the folder that the copy missed.
🔴 Never experiment on the only copy: no initialising, no formatting, no "repair" prompts on the original disks. If the data matters and the array is striped, image the disks first and experiment on the images.
🎥 Watch the Fix Guide in the Video
See the ST150 options in the video, and how the data side of the story is handled.
Almost certainly not. The data lives on the disks, which are independent of the board. Mirror and single-disk setups can usually be read on another machine directly; striped RAID 5 or 10 sets need a compatible controller or recovery software. The danger is rushed experiments, not the dead board itself.
Can I read an ST150 RAID disk in a USB dock?
A single disk or one member of a RAID 1 mirror — usually yes, it holds a complete readable copy. Members of RAID 5, RAID 10 or RAID 0 sets cannot be read alone because the data is striped across the set; those need the whole set assembled by a compatible controller or recovery software.
Should I repair the server or move the data to a new one?
If the data is urgent, do both in the right order: read and secure the data first, then decide the ST150's fate without pressure. A tested replacement board usually restores the original server exactly as it was, which is the least disruptive homecoming — decide with the data already safe.
This guide is based on the Lenovo ST150 motherboard video by Technical Anshu • Stuck on a step? Ask in the video comments — answers come there 🙏