File system frequently becoming read-only and requires reboot with manual FSCK.
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
File system frequently becoming read-only and requires reboot with manual FSCK.
I have a Dell XPS developer laptop that came pre-installed with Ubuntu. When I received the laptop, I replaced the SSD with a 500+GB NVMe drive and installed Mint. For the first 8-10 months of use, I hadn't had any problems.
About a month ago, I encountered this strange problem where my file system became read-only. I only discovered this when I tried to save a document. On reboot I was told to run FSCK manually and did to find some errors that needed correcting. Since this problem occurred I started to see this problem more frequently and now it can be almost every hour.
is my NVMe drive failing? I did a check with the nvme command and all of the numbers looked "normal" to me, but I admit I am not an expert when it comes to this. I hesitate to think the drive is failing only because it isn't very old and I don't use this computer very often. Is there anything I can do to try and hunt for a solution?
Replying in reverse order. My understanding is smartctl does not yet support NVMe drives. Is there another tool I can use to get a good diagnostic?
Because this drive is installed in a laptop, I don't want to be opening it if I don't have to. It wasn't exactly the first time I did it and I only want to do this if I actually need to replace the drive.
Replying in reverse order. My understanding is smartctl does not yet support NVMe drives. Is there another tool I can use to get a good diagnostic?
Because this drive is installed in a laptop, I don't want to be opening it if I don't have to. It wasn't exactly the first time I did it and I only want to do this if I actually need to replace the drive.
It could well be a loose connection causing an intermittent connection failure. You're not going to know that if you don't open the laptop, check the connection, and take out and re-insert the relevant connector. If you're too nervous about doing this yourself then you need to find someone who can do it for you.
If it's NVME, then it's an m.2 connector, and the drive is actually screwed into the connector, so I HUGELY doubt it could be a loose connection (this is one of the reasons for the design of the m.2 slot, it makes it pretty much impossible to have a loose connection if it's screwed in without physical damage).
I would second the checking SMART status.
And like any hardware, there's the occasional piece that simply is bad right out of the box, it's possible you've got a bad controller on your drive.
Last edited by Timothy Miller; 12-29-2017 at 11:02 AM.
Some boot tools, e.g. Hiren’s BootCD, incorporate CrystalDiskInfo.
In general, it's looking as if you may need to get the drive replaced under warranty (it appears to have a 5-year manufacturer's warranty), but I think it is a good idea to at least have a go at reading the drive's SMART data first.
They will tell you what you need to do as far as running diagnostics and where to get them for linux if that is required. They may just give you an rma without further ado. I think it is highly probable that the drive is failing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.