Linux Drive in a Windows PC? Reading ext4 Safely
Our founder and lead technician, Joseph Montanti, handles cases personally.
This one starts the same way every time. A NAS dies, or an old Linux tower gets retired, and somebody pulls the drive, plugs it into a Windows PC, and gets the scariest dialog in computing: "You need to format the disk in drive E: before you can use it." An unsupported Linux file system can prompt that message on Windows even when the drive is healthy.
On this page
Why Windows acts like your drive is blank
Windows natively understands its own file systems (NTFS, FAT32, exFAT) and nothing else. ext4, the default on most Linux systems and the storage layer inside most consumer NAS boxes from Synology, QNAP, WD, and Buffalo, simply isn't in Windows' vocabulary. When Windows sees a partition it can't parse, it reports the space as RAW and offers a format, because from its point of view the disk is unorganized space.
The critical thing to internalize: RAW in Disk Management does not mean your data is damaged. It means "I don't recognize this." The files, folders, and structure are all there, written in a dialect your PC never learned. Formatting would erase a perfectly healthy file system to replace it with one Windows likes. It's the computing equivalent of burning a book because it's in French.
Three safe ways to read ext4 on Windows
All three of these are read-only or can be used read-only, which is the entire point. Reading can't hurt. Writing can.
Option 1: DiskInternals Linux Reader (easiest)
A free Windows app that mounts ext2/ext3/ext4 (plus Btrfs, XFS, and others) in a file-explorer window, strictly read-only. Install it, plug in the drive, browse your folders, and copy what you need out to a Windows disk. For a single healthy drive out of a Linux PC or a one-bay NAS, this solves the whole problem in ten minutes.
Option 2: WSL2 (built into Windows, more technical)
Windows Subsystem for Linux can mount a physical drive with the wsl --mount command and read it with genuine Linux drivers. It's the most "correct" method and it's free, but it wants a bare-drive connection and command-line comfort, and you must resist the temptation to "fix" anything with fsck while you're in there. Mount, copy out, unmount.
Option 3: boot a Linux USB stick (most reliable)
Burn Ubuntu or Mint to a USB stick, boot the PC from it choosing "Try without installing," and the drive just appears on the desktop like it would on any Linux machine. Nothing touches your Windows install, and you're reading the drive with the exact software family that wrote it. Copy files to a second external drive formatted exFAT so both worlds can read it.
| Method | Best for | Watch out for |
|---|---|---|
| Linux Reader | Quick browse and copy, non-technical users | Free version copies; don't buy write features, you don't want them |
| WSL2 mount | Technical users, already on Windows 11 | Never run fsck/repair tools on a drive you're rescuing |
| Linux live USB | Stubborn cases, most compatibility | Copy out to exFAT so Windows can read the result |
The NAS trap: when the drive is "fine" but unreadable anyway
And NAS drives carry two complications that DIY guides skip.
Complication one: LVM and mdadm wrappers. Many NAS boxes (Synology especially) don't put a plain ext4 partition on the disk. They layer it: mdadm RAID metadata, then LVM volumes, then ext4 inside. Reader tools often can't see through all the layers, so even a healthy single-bay NAS drive can show nothing useful in Linux Reader. That doesn't mean the data's gone; it means the drive needs to be assembled the way the NAS assembled it, which a live Linux system can often do and Windows tools generally can't.
Complication two: multi-bay arrays. If your drive came out of a two-bay-or-bigger NAS that was configured RAID 0, RAID 5, or SHR, a single member drive is not supposed to be readable alone. Its data is striped across the set, deliberately interleaved with its siblings. Plugging members one by one into Windows and poking at them is how people turn a textbook RAID recovery into a forensic nightmare: any write to any member (a format prompt accepted, a "repair" tool run, Windows initializing a disk) can poison the array reconstruction.
When "unreadable" really does mean trouble
Sometimes the drive out of the Linux box genuinely is failing. The tells are different from the language-barrier problem:
- The drive clicks, beeps, or doesn't spin at all: mechanical failure, nothing about ext4 matters until the hardware is addressed. Power it down.
- Linux Reader or a live USB sees the partition but copying files throws I/O errors, hangs, or the drive disconnects: dying media. Every retry pushes it further. Stop and image it properly instead of cherry-picking files.
- The partition table is empty even under real Linux: possible corruption or a wiped table. Recoverable, but by imaging first and reconstructing second, not by running repair utilities against your only copy.
- It's the only copy of business data on a drive from a dead WD My Cloud or similar: weigh the DIY hours against what the data's worth before experimenting at all.
The rule that covers every case: read-only exploration is always fair game on a healthy drive. The moment the drive shows physical symptoms, or the moment any tool offers to fix, repair, initialize, or format, you've reached the edge of safe DIY. Copy that rule somewhere visible, because every tool you'll meet on this journey, from Windows itself to disk utilities to well-meaning forum advice, will offer you a button that writes.
Frequently Asked Questions
Can Windows read ext4 drives natively?
No. Windows understands NTFS, FAT32, and exFAT, and reports ext4 partitions as RAW, offering to format them. The data is intact; Windows just can't parse it. Use a read-only tool like DiskInternals Linux Reader, mount the drive in WSL2, or boot a Linux live USB to read the files safely.
Windows says I need to format the disk. Is my data gone?
No, that dialog is Windows meeting a file system it doesn't speak, and ext4 from a NAS or Linux machine triggers it constantly. Your data is only in danger if you accept the format or run repair tools. Cancel the dialog and read the drive with Linux-aware software instead.
Why can't I see files from my Synology or QNAP drive even with ext4 tools?
NAS vendors usually wrap ext4 inside mdadm RAID and LVM layers, and simple Windows readers can't always peel all three. A Linux live USB can often assemble the layers on a single-volume drive. Drives from multi-bay arrays are striped across members and generally can't be read alone at all; those need proper array reconstruction.
Is it safe to run chkdsk or fsck on an ext4 drive I need files from?
Don't. chkdsk doesn't understand ext4 and can damage it, and even fsck, the correct Linux tool, makes writes as it "fixes" things, which is exactly what you don't want on a drive holding the only copy of your data. Repair tools are for after your files are safely copied off, never before.
The ext4 drive reads with errors and copying keeps failing. What now?
Those are physical-failure symptoms, and repeated copy attempts accelerate the decline. Power the drive down. The professional approach is imaging the failing drive sector by sector onto healthy storage, then extracting files from the image. If the data matters, that's the point to hand it to a lab rather than push a dying drive through more retries.
Get help with data recovery
Bring your device to our Lincroft lab during opening hours, or mail it in.
How to mail your deviceThe $100 diagnostic is non-refundable once diagnostics start, and donor drives or replacement parts you approve are non-refundable once ordered, even if recovery fails.
Published by MDrepairs
MDrepairs is a data recovery and electronics repair lab in Lincroft, New Jersey. Our founder and lead technician Joseph Montanti films real cases for our YouTube channel, showing tools, repair steps and recovery outcomes.
Keep reading
- Chromebook Dead? Where Your Files Actually Live
- Laptop Screen Broken? How to Get Your Files
- Spilled on Your Laptop? Save the Data, Then the Laptop