Have you ever been working on a document on your computer, only to have a power outage or unexpected crash? When you try to open the document again, you get an error message saying that “the file system wasn’t closed safely.” This can be a frustrating experience, but it’s actually a fairly common problem. In this article, I’ll explain what this error means and how you can fix it. I’ll also provide some tips for preventing this error from happening in the future. So if you’ve ever been plagued by the “file system wasn’t closed safely” error, read on for help!
Table of Contents
| Column 1 | Column 2 | Column 3 |
|—|—|—|
| Problem | Cause | Solution |
| The file system wasn’t safely closed on Windows. | The file system may have been interrupted while it was being written to. | Try restarting your computer and see if the error goes away. If the error persists, you can try the following: |
| * Check for corrupted files. Run the System File Checker utility to scan for and repair any corrupted system files. |
| * Update your drivers. Make sure that your drivers are up to date, especially your storage drivers. |
| * Reinstall your operating system. If all else fails, you may need to reinstall your operating system. |
The error “The file system wasn’t safely closed” is a Windows error message that can occur when you try to close a file or folder. It can also occur when you try to eject a removable storage device, such as a USB drive or SD card.
The error message is usually accompanied by a blue screen of death (BSOD). The BSOD is a graphical error screen that displays a stop code, which is a hexadecimal number that identifies the specific error that occurred. In the case of the “The file system wasn’t safely closed” error, the stop code is usually 0x00000024.
The “The file system wasn’t safely closed” error can occur for a number of reasons. Some of the most common causes include:
- Power loss: If your computer loses power while you are working on a file or folder, the file system may not be able to close the file properly. This can lead to the error “The file system wasn’t safely closed” the next time you try to access the file or folder.
- File corruption: If a file becomes corrupted, it may not be able to be closed properly. This can also lead to the error “The file system wasn’t safely closed”.
- Software conflict: A software conflict can also cause the “The file system wasn’t safely closed” error. This can happen if two or more programs are trying to access the same file or folder at the same time.
- Hardware failure: A hardware failure, such as a failing hard drive, can also cause the “The file system wasn’t safely closed” error.
What causes the error The file system wasn’t safely closed?
The error “The file system wasn’t safely closed” can be caused by a number of factors, including:
- Power loss: If your computer loses power while you are working on a file or folder, the file system may not be able to close the file properly. This can lead to the error “The file system wasn’t safely closed” the next time you try to access the file or folder.
- File corruption: If a file becomes corrupted, it may not be able to be closed properly. This can also lead to the error “The file system wasn’t safely closed”.
- Software conflict: A software conflict can also cause the “The file system wasn’t safely closed” error. This can happen if two or more programs are trying to access the same file or folder at the same time.
- Hardware failure: A hardware failure, such as a failing hard drive, can also cause the “The file system wasn’t safely closed” error.
Power loss is the most common cause of the “The file system wasn’t safely closed” error. This is because when your computer loses power, it does not have a chance to properly close the files that are open. This can cause the files to become corrupted, which can lead to the error.
File corruption can also cause the “The file system wasn’t safely closed” error. This can happen if a file is damaged or deleted incorrectly. When a file is damaged, it may not be able to be opened or closed properly. When a file is deleted incorrectly, it may not be removed from the file system properly. This can both lead to the error “The file system wasn’t safely closed”.
Software conflict can also cause the “The file system wasn’t safely closed” error. This can happen if two or more programs are trying to access the same file or folder at the same time. When this happens, the programs can interfere with each other, which can lead to the error.
Hardware failure can also cause the “The file system wasn’t safely closed” error. This can happen if a hardware device, such as a hard drive, fails. When a hardware device fails, it can cause the file system to become corrupted, which can lead to the error.
The error “The file system wasn’t safely closed” can be a frustrating problem, but it can usually be fixed. If you are experiencing this error, try the following steps:
- Check for power loss: If your computer has lost power recently, this could be the cause of the error. Try restarting your computer and see if the error goes away.
- Check for file corruption: If you think a file may be corrupted, try repairing or restoring it. You can do this using the Windows File Recovery tool or a third-party file repair tool.
- Check for software conflicts: If you think two or more programs are conflicting, try uninstalling one of them. You
How to fix the error The file system wasn’t safely closed?
The error “The file system wasn’t safely closed” can occur when you try to close a file or folder in Windows. This error can be caused by a variety of factors, including:
- A power outage or system crash
- A corrupted file system
- A software conflict
- A hardware problem
If you receive this error, you may be unable to access the affected file or folder. However, there are a few things you can try to fix the problem.
1. Restart your computer
The first thing you should try is to restart your computer. This can often fix minor errors that are causing the problem.
To restart your computer, click on the Start button and then select **Power** > Restart.
2. Run CHKDSK
CHKDSK is a built-in Windows utility that can scan your hard drive for errors and fix them. To run CHKDSK, open the Command Prompt and type the following command:
chkdsk /f /r
This command will scan your hard drive for errors and fix any that it finds.
3. Update your drivers
Outdated drivers can sometimes cause problems with file access. To update your drivers, open the Device Manager and right-click on the device that is causing the problem. Select Update driver and follow the on-screen instructions.
4. Use a file recovery tool
If the above steps do not fix the problem, you can try using a file recovery tool to restore the affected file or folder. There are a number of different file recovery tools available, so you can choose one that best suits your needs.
5. Reformat your hard drive
If all of the above steps fail, you may need to reformat your hard drive. This will delete all of the data on your hard drive, so make sure to back up your important files before you do this.
To reformat your hard drive, open the Disk Management tool and right-click on the drive that you want to reformat. Select Format and follow the on-screen instructions.
What to do if the error The file system wasn’t safely closed persists
If you have tried all of the above steps and the error persists, you may need to contact technical support for help.
What to do if the error The file system wasn’t safely closed persists
If you have tried all of the steps above and the error “The file system wasn’t safely closed” still persists, you may need to contact technical support for help.
When you contact technical support, be sure to have the following information ready:
- The exact error message that you are receiving
- The steps that you have already taken to try to fix the problem
- The type of computer that you are using (Windows, Mac, etc.)
- The version of the operating system that you are using
- The name of the file or folder that you are trying to access
Technical support can help you troubleshoot the problem and determine the best course of action.
Q: What does it mean when I get the error message “The file system wasn’t safely closed”?
A: This error message means that Windows was unable to close a file or folder properly. This can happen for a variety of reasons, such as a power outage, a system crash, or a software conflict.
Q: What are the symptoms of this error?
A: You may see the following symptoms if you get this error:
- You may be unable to open or save files.
- You may receive error messages when you try to access files or folders.
- Your computer may freeze or crash.
Q: How can I fix this error?
A: There are a few things you can try to fix this error:
- Restart your computer. This may resolve the issue if the error was caused by a temporary glitch.
- Run CHKDSK. CHKDSK is a Windows utility that can scan your hard drive for errors and fix them. To run CHKDSK, open a Command Prompt window and type the following command:
chkdsk /f /r
- Update your drivers. Make sure that your drivers are up to date, especially your hard drive driver. You can update your drivers manually or use a driver update tool.
- Run a malware scan. A malware infection can sometimes cause file system errors. Run a malware scan with your antivirus software to check for and remove any malware.
Q: What if I can’t fix the error myself?
A: If you’re unable to fix the error yourself, you can contact Microsoft support for help. You can also take your computer to a repair shop for assistance.
the file system wasn’t safely closed error can be a frustrating problem, but it can usually be fixed by following the steps outlined in this article. By restarting your computer, running CHKDSK, and disabling Fast Startup, you can often get your computer back up and running without any problems. If these steps don’t work, you may need to contact a professional for help.
Here are some key takeaways to remember:
- The file system wasn’t safely closed error can occur when your computer is shut down or restarted unexpectedly.
- To fix this error, you can try restarting your computer, running CHKDSK, or disabling Fast Startup.
- If these steps don’t work, you may need to contact a professional for help.
Author Profile
-
Hatch, established in 2011 by Marcus Greenwood, has evolved significantly over the years. Marcus, a seasoned developer, brought a rich background in developing both B2B and consumer software for a diverse range of organizations, including hedge funds and web agencies.
Originally, Hatch was designed to seamlessly merge content management with social networking. We observed that social functionalities were often an afterthought in CMS-driven websites and set out to change that. Hatch was built to be inherently social, ensuring a fully integrated experience for users.
Now, Hatch embarks on a new chapter. While our past was rooted in bridging technical gaps and fostering open-source collaboration, our present and future are focused on unraveling mysteries and answering a myriad of questions. We have expanded our horizons to cover an extensive array of topics and inquiries, delving into the unknown and the unexplored.
Latest entries
WD My Passport 1TB USB Error: «The file system wasn’t safely closed on Windows…»
Screenshot of error message is attached.
My WD Passport 1Tb external USB drive will not mount either in Ubuntu or Windows due to this error. Can anyone shed any light on what the problem is and any possible solutions?
What occurred: I plugged my WD Passport 1TB drive into my Xbox 360 via USB. The Xbox 360 notified me that formatting was necessary in order to use the drive on the console. I said, «Nope, no way, I’ll pass. Thanks.» and immediately unplugged the drive and powered off the xbox.
Now, the Passport USB drive will not mount properly on Ubuntu or Windows. The drive has power (drive light is lit and active) , platters are spinning AND the Passport HDD icon appears on the Ubuntu desktop and likewise under My Computer via Windows. However, the drive contents are inaccessible when clicking to access the drive icon. The process of opening will ‘hang’ and freeze up.
Please see the following attached screenshot for the exact error message that pops-up (note that I blacked out my username):
errorMsg.png
I am assuming that in my haste, the drive was corrupted due to improper dismount from the Xbox console??
Google searches suggest that I run chkdsk /f or chkdsk /r on the drive via Windows. Upon running «chkdsk /f h:» (where «h:» is the passport drive letter) under Windows XP via CMD line, the process appears to run with no end in sight. I get literally thousands of lines of «file record segment unreadable» (followed by the drive segment number) and this appears to go on with no real end in sight. I cannot check % of completion b/c the terminal window is flooded with the «file record segment unreadable» messages. I have no way of knowing if there is any real progress unless I set my own arbitrary time limit for chkdsk to run. After 6 hours, I stopped the process. I am willing to try again for longer if necessary.
Further research tells me to run chkdsk /r instead of /f however upon attempting, the terminal windows hangs.
After letting chkdsk run for 6 hours, I restarted and attempted to try chkdsk on a faster Windows 7 VM via VirtualBox. Again, no dice. Windows hangs or tells me that the drive is in RAW format (but indicates NTFS in XP)…etc etc. Windows blah!!!!!
Question: Are there any solutions via linux/Ubuntu that could help with this issue? I am a dedicated Ubuntu user after leaving years or torment by Micro$oft Windows. Seems that M$ still has it out for me!
Penguin to the rescue? Where ya at Tux??
Any tips, feedback or help with this issue is appreciated!
P.S. Here is text copy of the error message that pops-up via Ubuntu when the drive is plugged in and I attempt to access the contents. Please note that I replaced my username with «xxxxxx» in the message.
Error Message:
«Error mounting /dev/sdb1 at /media/xxxxxx/My Passport: Command-line `mount -t «ntfs» -o «uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dm ask=0077,fmask=0177» «/dev/sdb1» «/media/xxxxxx/My Passport»‘ exited with non-zero exit status 13: The disk contains an unclean file system (0, 1).
The file system wasn’t safely closed on Windows. Fixing.
ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Failed to calculate free MFT records: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it’s a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the ‘dmraid’ documentation
for more details.
Failed to sync device /dev/sdb1: Input/output error
Failed to close volume /dev/sdb1: Input/output error»
Last edited by cyborgninja2; April 2nd, 2016 at 03:58 AM.
Re: WD My Passport 1TB USB Error: «The file system wasn’t safely closed on Windows…
Could be the disk is failing. Try checking the drive’s S.M.A.R.T. status with GSmartControl (install in Ubuntu). Look in the Attributes tab for any lines highlighted in red or pink — these are worrisome lines. (Ignore messages like «pre-failure» which are just types of Attributes, not indications of failure.)
FYI, it’s considered unsafe to stop chkdsk in the middle of trying to fix the filesystem. Even if it takes hours. Then again, it could be taking hours because the disk is about to fail.
I don’t know of any better tools in Linux to fix NTFS filesystems than chkdsk — but if the disk is failing it’s kind of irrelevant.
Re: WD My Passport 1TB USB Error: «The file system wasn’t safely closed on Windows…
and immediately unplugged the drive and powered off the xbox.
You should have done it the other way around. Never disconnect an NTFS volume that’s still mounted.
Re: WD My Passport 1TB USB Error: «The file system wasn’t safely closed on Windows…
Originally Posted by Tem�jin
You should have done it the other way around. Never disconnect an NTFS volume that’s still mounted.
+1
Когда резко выиащил диск то появилась такая вот ошибка:
НЕ УДАЛОСЬ ПРИМОНТИРОВАТЬ ELEMENT HDD
Error mounting: mount exited with exit code 13: The disk contains an unclean file system (0, 0).
The file system wasn’t safely closed on Windows. Fixing.
ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Failed to read NTFS $Bitmap: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it’s a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the ‘dmraid’ documentation
for more details.
Failed to sync device /dev/sdb1: Input/output error
Failed to close volume /dev/sdb1: Input/output error
Ну так кабелек то поменять попробуйте. Да и подключать надобно не на морде системника, а к портам на материнской плате (они сзади).
А у меня и нет такого второго кабеля в наличии. И к материнке я не подключу. Я с ноутбука пишу.
Skip to content
Navigation Menu
Provide feedback
Saved searches
Use saved searches to filter your results more quickly
Sign up
Appearance settings
Description
Using usbipd wsl attach produces an error upon mounting in Linux:
The disk contains an unclean file system (0, 1).
The file system wasn’t safely closed on Windows. Fixing.
It seems the hardware is not safely removed under Windows but virtually just «plugged out».
It may be a source for file system errors.
Tested on:
Microsoft Windows [Version 10.0.22000.346]
WSL Ubuntu 5.10.74.3-microsoft-standard-WSL2+
- Печать
Страницы: [1] 2 Все Вниз
Тема: Ubuntu 10.04 не видит раздел нтфс и СД-привод (Прочитано 4575 раз)
0 Пользователей и 1 Гость просматривают эту тему.
hypersash
Всем привет! Поставил Окна после Линукса, ессесно затерся MBR. Через терминал ЛайвСД воостановил ГРУБ. После этого загрузился с уже установленного Линукса (загрузчик заработал), и вот он перестал видеть раздел нтфс на 80Гб с инфой. Вставил в СДишник диск ДВД с музыкой\фильмами\инфой, со стороны Линукса не поступило никакой реакции и диск нигде не видно. Еще не может запуститься Дисковая Утилита. Скачал Gparted, так для него ваще весь хард неразмеченная область…
Вот что выдал fdisk -l
sanya@sanya-laptop:~$ sudo fdisk -l
[sudo] password for sanya:
omitting empty partition (5)
Диск /dev/sda: 120.0 ГБ, 120034123776 байт
255 heads, 63 sectors/track, 14593 cylinders
Units = цилиндры of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x552d552d
Устр-во Загр Начало Конец Блоки Id Система
/dev/sda1 1 2263 18169515 83 Linux
/dev/sda2 * 2263 3545 10305634+ 7 HPFS/NTFS
/dev/sda3 3546 14593 88736737+ 5 Расширенный
/dev/sda4 3909 14593 85827228+ 7 HPFS/NTFS
/dev/sda5 3547 3908 2907733+ 82 Linux своп / Solaris
Я под Линуксом вобщем-то 4 дня сижу, так что желательно порасписать поподробнее. Спасибо.
« Последнее редактирование: 20 Июня 2010, 12:37:52 от energy_power »
hippi90
Руками монтировать пробовали?
Jack Sparrow
Не совсем понятно:
перестал видеть раздел нтфс
До этого Windows с Линуксом стояли, и Линукс видел этот раздел, а потом решено было ПЕРЕустановить Винду?
Если это тот случай, то, вероятно, при переустановке Винды она переформатировала раздел, соответственно, изменился его UUID.
Если это так, то просто узнаем новый UUID раздела с Виндой
sudo blkidи заменяем им тот старый, что был в /etc/fstab
Нейросети тебя не заменят. Тебя заменит человек, который умеет ими пользоваться.
hypersash
Руками монтировать пробовали?
Скажите как или дайте ссыль пожалуйста.
Сначала был просто Линукс и еще раздел нтфс для инфы. Потом от Линукса отпили кусок в 10Гб и поставил туда винду. Воостановил загрузчик. После этого и перестал видеть.
Вот что выдал sudo blkid
sanya@sanya-laptop:~$ sudo blkid
[sudo] password for sanya:
/dev/sda1: UUID="4d1a0a3a-4874-416a-9aa2-a61f4f6ec44f" TYPE="ext4"
/dev/sda2: UUID="1A40E18640E168C9" TYPE="ntfs"
/dev/sda4: UUID="F6E4C703E4C6C559" TYPE="ntfs"
/dev/sda5: TYPE="swap"
Что написано в /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sda1 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=39ab747b-3215-4123-ab8d-69d2acd10262 none swap sw 0 0
Что дальше?
« Последнее редактирование: 20 Июня 2010, 13:20:12 от energy_power »
Jack Sparrow
А что выдает
cat /etc/fstab
Нейросети тебя не заменят. Тебя заменит человек, который умеет ими пользоваться.
hypersash
А что выдает
cat /etc/fstab
sanya@sanya-laptop:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sda1 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=39ab747b-3215-4123-ab8d-69d2acd10262 none swap sw 0 0
Пользователь решил продолжить мысль 20 Июня 2010, 11:30:43:
Кстати, он не видит ни 10ти гиговый виндовый раздел, ни 80ти гиговый с инфой, везде нтфс.
« Последнее редактирование: 20 Июня 2010, 13:31:48 от energy_power »
666joy666
Скачал Gparted, так для него ваще весь хард неразмеченная область…
Windows потерла таблицу разделов, обсуждалось уже много раз, testdisk вам в руки и бубен в зубы:)
« Последнее редактирование: 20 Июня 2010, 13:38:16 от 666joy666 »
hippi90
Попробуйте
sudo mkdir /mnt/sda4Если заругается, то вывод dmesg | tail сюда киньте.
sudo mount -t ntfs-3g /dev/sda4 /mnt/sda4 -o user,nlocale=ru_RU.utf8
hypersash
Под рутом
root@sanya-laptop:/home/sanya# sudo mkdir /mnt/sda4Без рута
root@sanya-laptop:/home/sanya# sudo mount -t ntfs-3g /dev/sda4 /mnt/sda4 -o user,nlocale=ru_RU.utf8
The disk contains an unclean file system (0, 0).
The file system wasn't safely closed on Windows. Fixing.
sanya@sanya-laptop:~$ sudo mkdir /mnt/sda4
mkdir: невозможно создать каталог «/mnt/sda4»: Файл существует
sanya@sanya-laptop:~$ sudo mount -t ntfs-3g /dev/sda4 /mnt/sda4 -o user,nlocale=ru_RU.utf8
fuse: mount failed: Устройство или ресурс занято
Jack Sparrow
Пока писал, уже дали ответ. В Винде сделайте проверку дисков. Тогда они пометятся как чистые.
——
Не заметил, что fstab уже был дан.
Ладно. Судя по fstab что-то не похоже, что Линукс видел эти разделы раньше. Наверное, при установке Линукса не выбирали примонтировать раздел NTFS?
1. Монтировать можно вручную так:
sudo mount -t ntfs /dev/sda2 /mnt(раздел /dev/sda2 примотнируется в каталог /mnt)
2. Автоматически при запуске. Для этого добавить запись в fstab (где-нибудь в конце):
UUID=1A40E18640E168C9 /media/windows_c ntfs defaults,nls=utf8,umask=007,gid=46 0 0
UUID=F6E4C703E4C6C559 /media/windows_d ntfs defaults,nls=utf8,umask=007,gid=46 0 0Здесь UUID взяты из вашего вывода blkid. Только в папке /media нужно предварительно создать подпапки windows_c и windows_d
Нейросети тебя не заменят. Тебя заменит человек, который умеет ими пользоваться.
hypersash
Что-то невдупляю.. fstab как отредактировать? У меня только для чтения.
Папки windows_c и windows_d создал через терминал. sda2 примонтировал, но мне куда важнее примонтировать 80-ти гиговый раздел, он помоему sda4? Пробовал там-же поменять sda2 на sda4, но ничего путного не вышло.
hippi90
sudo nano /etc/fstab
Вам надо загрузиться в винду и проверить диски. Потом попробовать примонтировать, если примонтируется, тогда уже и в fstab вписать.
Jack Sparrow
Наверное, проще gedit
sudo gedit /etc/fstabвставить две строки в конец
UUID=1A40E18640E168C9 /media/windows_c ntfs defaults,nls=utf8,umask=007,gid=46 0 0
UUID=F6E4C703E4C6C559 /media/windows_d ntfs defaults,nls=utf8,umask=007,gid=46 0 0сохранить. Потом в Винде проверить диски на ошибки. Потом можно загружаться в Линуксе. Диски должны появиться.
ЗЫ. Если нужен только один раздел, то можно добавлять только одну соответствующую строчку (в вашем случае вторую).
Нейросети тебя не заменят. Тебя заменит человек, который умеет ими пользоваться.
hypersash
Спасибо, сделал как советовал hippi90. Все примонтировалось и сразу на рабочем стале появляются оба диска. Теперь осталось с СД-приводом разобраться. Никак не хочет видеть. Нужно открыть двд диск с авишными фильмами на нем. Спасибо.
Nestor
Спасибо, сделал как советовал hippi90. Все примонтировалось и сразу на рабочем стале появляются оба диска. Теперь осталось с СД-приводом разобраться. Никак не хочет видеть. Нужно открыть двд диск с авишными фильмами на нем. Спасибо.
Также примонтировать вручную:
$ sudo mkdir /mnt/dvd
$ sudo mount -t iso9660 /dev/cdrom /mnt/dvd
То есть монтируем раздел /dev/cdrom типа iso9660 в точку монтирования /mnt/dvd
Для постояного монтирования правим fstab:
/dev/cdrom /mnt/cdrom iso9660 umask=0,nls=utf-8,user,ro 0 0
Должна быть создана директория /mnt/cdrom, если её нет
Отмонтирование по команде umount /mnt/cdrom
По поводу таблицы разделов — поскольку фаловые системы определяются, то таблица была ИМХО не причём
У меня во всяком (в подобной ситуации) случае они в testdisk виделись как неопределённые
If you have paranoia, it doesn’t mean that they do not hunt for you
- Печать
Страницы: [1] 2 Все Вверх