Samsung NVME randomly goes down during activity

I am sorry… it is not really clear where you are now.

  1. live session with chroot
  2. booted local installation


1 Like

file system then ect then im stairing at whole lotta folders that look like and named in fasions that even the dummy in me is going be carefull.

ok well… dummy instruction:

  1. Boot a Manjaro Installation Disk (hope I don’t have to explain that)
  2. When booted, then first repair the filesystem (must not be mounted):
sudo fsck.ext4 -f -y /dev/nvme1n1p2
  1. Then chroot into that with the helper script:
sudo manjaro-chroot -a
  1. Now do what @Zesko wrote:

Open the file with nano:

nano /etc/default/grub

Edit it accordingly and save it and close it.

Then update grub.

exit the session.

When ever i bring out my usb for to fix my problems, it has always been without repair because i could never figure out how to get to let alone run the repair, without doing a full system reinstall. SO can you elaborate on that?

I am sorry, but what exactly is not understandable? Give me something to deal with. I will not explain pretty basic stuff. Maybe someone else can do that.

You did already a repair as I see above… so what is the question?

that repair above was not through a boot stick, that was straight from terminal. and not from grub ether… SOOOOO now you have me more confused? So do i need a bootstick or not?

The drive we are working on does not have manjaro/os on it is the samsung, the wd has manjaro on it.

ok… as I see you run that:

That is:

and I really hope you unmounted it before checking it. That works that way… But:

Is the system partition (root directory). That means, it can only be checked outside, so a live session, or it does it always on boot time to solve small problems. Huge problems have to be repaired outside of the local installation.

I mentioned this because of the journal log and to ensure that the filesystem is not broken.

1n1p2 is not the problem, sooo why are we checking its filesystem?

my head hurts… I need a break, you probably do too, before you reach across the internet and wrap your fingers around my neck.

Then skip that step if you know more… It is just safety measure. That’s all.

Then please do so and take a break. No hurry… Go for a walk and clear your mind. Sometimes things can be overwhelming. it is understandable.

then check the one that needs to be checked …

anyway, once that is done

without the complication of chroot - just use your running system
it is still running, is it?

  • open terminal
  • issue command:
    sudo nano /etc/default/grub
    (that will open the file you need to edit in … an editor (nano)
  • find the 5th line down, which should read:
    GRUB_CMDLINE_LINUX_DEFAULT="quiet udev.log_priority=3"

and append to it, inside the quotes:
nvme_core.default_ps_max_latency_us=0 pcie_aspm=off

so that it then looks like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet udev.log_priority=3 nvme_core.default_ps_max_latency_us=0 pcie_aspm=off"

that is still only one line

  • save the file

  • run:
    sudo update-grub

and then reboot

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.