I also had this problem of it working for a year, then I update it and it stops working. Then I roll back the kernel and it won't work again
Enviado via ProtonMail móvel -------- Mensagem Original -------- Ativo 7 de mar de 2020 10:17, Ramon Fontes escreveu: > I have a Dell Inspiron 14 5000 Series-5480. The most strange thing is > that I bought my laptop about 1 year ago and I've installed Ubuntu > 18.04.1 with kernel 4.15.0-65-xxx (default installation) and everything > worked as expected. However, the same problem happened with any other > kernel version (including 4.17.0-041700-generic). > > Then, after having some problems with my system I've installed Ubuntu > 18.04.4. The kernel version installed with the system was 5.3 and after > observing the same problem with the disk I've tried to install 4.15.0-65 and > the problem has not been solved (I don't remember exactly which kernel > version I had in the first time (e.g. what was the xxx)). Finally, I've found > that 4.17.0-041700-generic works and I don't know why. It didn't work with > Ubuntu 18.04.1 and it works with 18.04.4. This is really strange and I need > to use most recent kernel versions, because I need to use some features I've > implemented for v5.5-rc1. > > [1] > https://github.com/torvalds/linux/commit/b5764696ac409523414f70421c13b7e7a9309454#diff-21081ef83e1374560c2e244926168e49 > [2] > https://github.com/torvalds/linux/commit/7dfd8ac327301f302b03072066c66eb32578e940#diff-21081ef83e1374560c2e244926168e49 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1746340 > > Title: > Samsung SSD corruption (fsck needed) > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Ubuntu 4.13.0-21.24-generic 4.13.13 > > I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu > 17.04, which gave me this error after 2 weeks of usage. After that, I > installed 16.04 and used it for MONTHS without any problems, until it > produced the same error this week. I think it has to do with the ubuntu > updates, because I did one recently and one today, just before this problem. > Could be a coincidence though. > > I notice the error when I try to save something on disk and it says me > that the disk is in read-only mode: > > lz@lz:/var/log$ touch something > touch: cannot touch 'something': Read-only file system > > lz@lz:/var/log$ cat syslog > Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): > ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming > directory block 0 > > lz@lz:/var/log$ dmesg > [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.377374] Aborting journal on device nvme0n1p2-8. > [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only > [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" > operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" > capability=12 capname="net_admin" > > Rebooting the ubuntu will give me a black terminal where I can run > fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of > orphaned inodes. The majority of time it boots back to the Ubuntu > working good, but some times it boots to a broken ubuntu (no images, > lots of things broken). I have to reinstall ubuntu then. > > Every time I reinstall my Ubuntu, I have to try lots of times until it > installs without an Input/Output error. When it installs, I can use it > for some hours without having the problem, but if I run the software > updates, it ALWAYS crashes and enters in read-only mode, specifically > in the part that is installing kernel updates. > > I noticed that Ubuntu installs updates automatically when they're for > security reasons. Could this be the reason my Ubuntu worked for months > without the problem, but then an update was applied and it broke? > > I thought that this bug was happening: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried > different nvme_core.default_ps_max_latency_us= combinations, all them > gave errors. I just changed to 0 and I had no error while using ubuntu > (however I didn't test for a long time) but I still had the error > after trying to update my ubuntu. > > My Samsung 512gb SSD is: > > SAMSUNG MZVLW512HMJP-00000, FW REV: CXY7501Q > > on a Razer Blade Stealth. > > I also asked this on ask ubuntu, without success: > https://askubuntu.com/questions/998471/razer-blade-stealth-disk- > corruption-fsck-needed-probably-samsung-ssd-bug-afte > > Please help me, as I need this computer to work on lots of things :c > --- > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC0: lz 1088 F.... pulseaudio > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 17.10 > InstallationDate: Installed on 2018-01-30 (0 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) > MachineType: Razer Blade Stealth > Package: linux (not installed) > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed > root=UUID=0ca062da-7e8f-425a-88b1-1f784fb40346 ro quiet splash > button.lid_init_state=open nvme_core.default_ps_max_latency_us=0 > ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 > RelatedPackageVersions: > linux-restricted-modules-4.13.0-21-generic N/A > linux-backports-modules-4.13.0-21-generic N/A > linux-firmware 1.169.1 > Tags: wayland-session artful > Uname: Linux 4.13.0-21-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 01/12/2017 > dmi.bios.vendor: Razer > dmi.bios.version: 6.00 > dmi.board.name: Razer > dmi.board.vendor: Razer > dmi.chassis.type: 9 > dmi.chassis.vendor: Razer > dmi.modalias: > dmi:bvnRazer:bvr6.00:bd01/12/2017:svnRazer:pnBladeStealth:pvr2.04:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: > dmi.product.family: 1A586752 > dmi.product.name: Blade Stealth > dmi.product.version: 2.04 > dmi.sys.vendor: Razer > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs