Page 1 of 3 123 LastLast
Results 1 to 10 of 30

Thread: Error mounting SSD

  1. #1
    Join Date
    Dec 2005
    Beans
    Hidden!
    Distro
    Kubuntu

    Error mounting SSD

    There are 2 SSD's with this laptop, one internal I use to boot to Windows, the other has Kubuntu on it. I can usually use Dolphin to navigate the internal/Windows drive , but now it is giving an error

    An error occurred while accessing '237.9 GiB Internal Drive (nvme0n1p3)', the system responded: The requested operation has failed: Error mounting /dev/nvme0n1p3 at /media/*****/******
    : wrong fs type, bad option, bad superblock on /dev/nvme0n1p3, missing codepage or helper program, or other error
    The mount command shows it as

    /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,io charset=iso8859-1,shortname=mixed,errors=remount-ro)
    I can do a ls from the terminal

    Code:
    $ ls -al /dev/nvme0n1p1
    brw-rw---- 1 root disk 259, 1 Jul 5 10:55 /dev/nvme0n1p1
    and also ..

    $ ls -al /dev/nvme0n1p3
    brw-rw---- 1 root disk 259, 3 Jul 5 10:55 /dev/nvme0n1p3

    I can display both the SSD's in KDE Partion Manager. This journal entry is concerning ..

    Jul 05 11:25:23 ThinkPad-T470s smartd[655]: Device: /dev/nvme0, number of Error Log entries increased from 4799 to 4814
    Last edited by oygle; July 5th, 2024 at 06:40 AM.

  2. #2
    Join Date
    Apr 2007
    Beans
    3,146
    Distro
    Ubuntu

    Re: Error mounting SSD

    Show information about /dev/nvme0n1p3 by providing the output of the following command:
    Code:
    { sudo blkid && mount && cat /etc/fstab ; } | grep nvme0n1p3

  3. #3
    Join Date
    Dec 2005
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Error mounting SSD

    Thanks @vanadium

    Code:
    $ { sudo blkid && mount && cat /etc/fstab ; } | grep nvme0n1p3
    /dev/nvme0n1p3: BLOCK_SIZE="512" UUID="DABA0B69BA0B418D" TYPE="ntfs" PARTUUID="21600ef4-2f6d-4bf9-b98a-6eecd29f09ef"

  4. #4
    Join Date
    Jun 2014
    Beans
    7,828

    Re: Error mounting SSD

    In your initial post, you indicate you are having problems with partition 3 on the device then post information from the mount and ls commands on "partition 1", the EFI partition. Is partition 3 the actual problem partition and is it a data partition? There would be no reason to access the windows system partition from Linux, at least no reason to write to it so hopefully you have not done that. Since you have some version of windows installed, boot into windows and run chkdsk to see if it can repair the problem. It might be that it is just hibernated but probably not as you would have seen a different error.

  5. #5
    Join Date
    Dec 2005
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Error mounting SSD

    Quote Originally Posted by yancek View Post
    In your initial post, you indicate you are having problems with partition 3 on the device then post information from the mount and ls commands on "partition 1", the EFI partition. Is partition 3 the actual problem partition and is it a data partition?
    The entry is Dolphin file Manager was setup automatically, for some reason it addressed partition 3, and gave an error message on partitiion 3.

    Quote Originally Posted by yancek View Post
    There would be no reason to access the windows system partition from Linux, at least no reason to write to it so hopefully you have not done that.
    I have been accessing the windows system files via the network when it was on another computer. Now it is on the same computer, the need is still there, and I have had no errors or problems to date, ..until now.

    Quote Originally Posted by yancek View Post
    Since you have some version of windows installed, boot into windows and run chkdsk to see if it can repair the problem. It might be that it is just hibernated but probably not as you would have seen a different error.
    Yes it seems so ..

    Code:
    sudo ls -al /boot/efi
    total 462
    drwx------ 4 root root 1024 Jan 1 1970 .
    drwxr-xr-x 4 root root 4096 Jun 27 12:16 ..
    drwx------ 5 root root 1024 Apr 27 13:06 EFI
    -rwx------ 1 root root 80896 Jan 1 1980 FSCK0000.REC
    -rwx------ 1 root root 80896 Jan 1 1980 FSCK0001.REC
    -rwx------ 1 root root 46080 Jan 1 1980 FSCK0002.REC
    -rwx------ 1 root root 78848 Jan 1 1980 FSCK0003.REC
    -rwx------ 1 root root 79872 Jan 1 1980 FSCK0004.REC
    -rwx------ 1 root root 46080 Jan 1 1980 FSCK0005.REC
    -rwx------ 1 root root 20480 Jan 1 1980 FSCK0006.REC
    -rwx------ 1 root root 32768 Jan 1 1980 FSCK0007.REC
    drwx------ 2 root root 1024 Jul 28 2022 'System Volume Information'
    So I logged into the Windows SSD, ran chkdsk as admin, it found errors, supposedly fixed them. However the partitiion still cannot be displayed from Kubuntu. Everytime I do an autoremove it references /boot/efi and partition 1, not partition 3. Here is a log from about 6 weeks ago.

    sudo apt autoremove
    [sudo] password for ********:
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    The following packages will be REMOVED:
    linux-headers-6.5.0-9 linux-headers-6.5.0-9-generic linux-image-6.5.0-9-generic linux-modules-6.5.0-9-generic linux-modules-extra-6.5.0-9-generic
    0 to upgrade, 0 to newly install, 5 to remove and 0 not to upgrade.
    After this operation, 273 MB disk space will be freed.
    Do you want to continue? [Y/n] y
    (Reading database ... 261754 files and directories currently installed.)
    Removing linux-headers-6.5.0-9-generic (6.5.0-9.9) ...
    Removing linux-headers-6.5.0-9 (6.5.0-9.9) ...
    Removing linux-image-6.5.0-9-generic (6.5.0-9.9) ...
    /etc/kernel/postrm.d/initramfs-tools:
    update-initramfs: Deleting /boot/initrd.img-6.5.0-9-generic
    /etc/kernel/postrm.d/zz-update-grub:
    Sourcing file `/etc/default/grub'
    Generating grub configuration file ...
    Found linux image: /boot/vmlinuz-6.5.0-35-generic
    Found initrd image: /boot/initrd.img-6.5.0-35-generic
    Found linux image: /boot/vmlinuz-6.5.0-28-generic
    Found initrd image: /boot/initrd.img-6.5.0-28-generic
    Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
    Warning: os-prober will be executed to detect other bootable partitions.
    Its output will be used to detect bootable binaries on them and create new boot entries.
    Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
    Adding boot menu entry for UEFI Firmware Settings ...
    done
    Removing linux-modules-extra-6.5.0-9-generic (6.5.0-9.9) ...
    Removing linux-modules-6.5.0-9-generic (6.5.0-9.9) ...
    This is how KDE Partition Manager views the Windows SSD
    Attached Images Attached Images

  6. #6
    Join Date
    Dec 2005
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Error mounting SSD

    Some more info ..

    Code:
    lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
    loop0 7:0 0 74.2M 1 loop /snap/core22/1380
    loop1 7:1 0 73.9M 1 loop /snap/core22/864
    loop2 7:2 0 268.6M 1 loop /snap/firefox/4451
    loop3 7:3 0 4K 1 loop /snap/bare/5
    loop4 7:4 0 268.7M 1 loop /snap/firefox/4483
    loop5 7:5 0 497M 1 loop /snap/gnome-42-2204/141
    loop6 7:6 0 505.1M 1 loop /snap/gnome-42-2204/176
    loop7 7:7 0 91.7M 1 loop /snap/gtk-common-themes/1535
    loop8 7:8 0 38.7M 1 loop /snap/snapd/21465
    loop9 7:9 0 38.8M 1 loop /snap/snapd/21759
    loop10 7:10 0 127.8M 1 loop /snap/yt-dlp/578
    sda 8:0 0 931.5G 0 disk
    ├─sda1 8:1 0 480M 0 part
    └─sda2 8:2 0 931G 0 part /var/snap/firefox/common/host-hunspell
    /
    sdb 8:16 1 0B 0 disk
    nvme0n1 259:0 0 238.5G 0 disk
    ├─nvme0n1p1 259:1 0 100M 0 part /boot/efi
    ├─nvme0n1p2 259:2 0 16M 0 part
    ├─nvme0n1p3 259:3 0 237.9G 0 part
    └─nvme0n1p4 259:4 0 509M 0 part
    Some related reading at https://askubuntu.com/questions/1502...longside-windo , https://askubuntu.com/questions/1137...n-in-etc-fstab , https://askubuntu.com/questions/1459...to-hibernation

    Code:
    journalctl -b | grep nvme
    Jul 06 13:56:34 ThinkPad-T470s kernel: nvme nvme0: pci function 0000:3c:00.0
    Jul 06 13:56:34 ThinkPad-T470s kernel: nvme nvme0: 4/0/0 default/read/poll queues
    Jul 06 13:56:34 ThinkPad-T470s kernel: nvme0n1: p1 p2 p3 p4
    Jul 06 13:56:34 ThinkPad-T470s (udev-worker)[338]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
    Jul 06 13:56:34 ThinkPad-T470s (udev-worker)[330]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
    Jul 06 13:56:34 ThinkPad-T470s (udev-worker)[338]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
    Jul 06 13:56:34 ThinkPad-T470s (udev-worker)[332]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1.
    Jul 06 13:56:34 ThinkPad-T470s (udev-worker)[323]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
    Jul 06 13:56:34 ThinkPad-T470s systemd-fsck[367]: /dev/nvme0n1p1: 197 files, 32542/98304 clusters
    Jul 06 13:56:36 ThinkPad-T470s smartd[643]: Device: /dev/nvme0, opened
    Jul 06 13:56:36 ThinkPad-T470s smartd[643]: Device: /dev/nvme0, SAMSUNG MZVLW256HEHP-000L7, S/N:S35ENX0K685866, FW:5L7QCXB7, 256 GB
    Jul 06 13:56:36 ThinkPad-T470s smartd[643]: Device: /dev/nvme0, is SMART capable. Adding to "monitor" list.
    Jul 06 13:56:36 ThinkPad-T470s smartd[643]: Device: /dev/nvme0, state read from /var/lib/smartmontools/smartd.SAMSUNG_MZVLW256HEHP_000L7-S35ENX0K685866.nvme.state
    Jul 06 13:56:36 ThinkPad-T470s smartd[643]: Device: /dev/nvme0, number of Error Log entries increased from 4832 to 4837
    Jul 06 13:56:36 ThinkPad-T470s smartd[643]: Device: /dev/nvme0, state written to /var/lib/smartmontools/smartd.SAMSUNG_MZVLW256HEHP_000L7-S35ENX0K685866.nvme.state
    Jul 06 13:57:02 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: It is recommened to use chkdsk.
    Jul 06 13:57:02 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: volume is dirty and "force" flag is not set!
    Jul 06 14:00:56 ThinkPad-T470s plasmashell[2117]: getting temp failed for "/dev/nvme0n1" : Success
    Jul 06 14:00:56 ThinkPad-T470s plasmashell[2117]: getting powered on time failed for "/dev/nvme0n1" : Success
    Jul 06 14:00:56 ThinkPad-T470s plasmashell[2117]: getting power cycles failed for "/dev/nvme0n1" : Success
    Jul 06 14:00:56 ThinkPad-T470s plasmashell[2117]: unknown file system type "" on "/dev/nvme0n1p2"
    Jul 06 14:00:56 ThinkPad-T470s plasmashell[2117]: "Partition ‘/dev/nvme0n1p3’ is not properly aligned (last sector: 499,071,628, modulo: 653)."
    Jul 06 14:01:59 ThinkPad-T470s plasmashell[2117]: "Add operation: Check and repair partition ‘/dev/nvme0n1p3’ (237.86 GiB, ntfs)"
    Jul 06 14:02:31 ThinkPad-T470s plasmashell[2117]: "Undoing operation: Check and repair partition ‘/dev/nvme0n1p3’ (237.86 GiB, ntfs)"
    Jul 06 14:26:36 ThinkPad-T470s smartd[643]: Device: /dev/nvme0, number of Error Log entries increased from 4837 to 4852
    Jul 06 16:50:04 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: It is recommened to use chkdsk.
    Jul 06 16:50:04 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: volume is dirty and "force" flag is not set!
    Jul 06 16:50:12 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: It is recommened to use chkdsk.
    Jul 06 16:50:12 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: volume is dirty and "force" flag is not set!
    Jul 06 16:50:13 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: It is recommened to use chkdsk.
    Jul 06 16:50:13 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: volume is dirty and "force" flag is not set!
    Jul 06 16:50:14 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: It is recommened to use chkdsk.
    Jul 06 16:50:14 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: volume is dirty and "force" flag is not set!
    Jul 06 16:50:33 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: It is recommened to use chkdsk.
    Jul 06 16:50:33 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: volume is dirty and "force" flag is not set!
    Jul 06 18:43:58 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: It is recommened to use chkdsk.
    Jul 06 18:43:58 ThinkPad-T470s kernel: ntfs3: nvme0n1p3: volume is dirty and "force" flag is not set!
    Last edited by oygle; July 6th, 2024 at 10:03 AM.

  7. #7
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Error mounting SSD

    Do not know latest version of chkdsk, but it had multiple parameters.
    Some versions just run check without fixing, others fix some things.

    It used to be you have to run chkdsk several times until you got no errors.

    You do have to make sure fast startup & bitlocker are both off in Windows.
    And really better not to mount the Windows "c:drive" partition, but create a shared NTFS data partition.
    Back with XP I corrupted it multiple times viewing & clicking & moving mouse to fast & it moved folders around.
    Last edited by oldfred; July 6th, 2024 at 02:30 PM.
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  8. #8
    Join Date
    Jun 2014
    Beans
    7,828

    Re: Error mounting SSD

    I have been accessing the windows system files via the network when it was on another computer. Now it is on the same computer,
    Modifying folders/files (images, music files, etc.) on an ntfs filesystem from Linux should work but modifying any system files on a windows OS from Linux is a bad idea.

    When you run the ls -al command on /boot/efi/EFI, you should see an ubuntu directory. If you have windows installed also, you should see a Microsoft directory with EFI files in the respective directories. I don't know what the files you shown under efi with the '.REC' extension are and have never seen that before. Can you read those files?

    The exit code 1 error from the mount command you posted means those commands need to be run as root (sudo) and were not.

    Your journalctl output clearly shows the 3rd partition (ntfs) needs chkdsk run from windows so that would be the obvious next step if you have not done it and if you have, what was the result?

    You should also check the various parameters for chkdsk to see what would be most appropriate in your case.

  9. #9
    Join Date
    Dec 2005
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Error mounting SSD

    Thanks @oldfred

    Quote Originally Posted by oldfred View Post
    Do not know latest version of chkdsk, but it had multiple parameters.
    Some versions just run check without fixing, others fix some things.

    It used to be you have to run chkdsk several times until you got no errors.
    I have run it a few times now, states it "fixes" errors, yet when I display the following, one can see it has 'chkdsk' type files still there.

    Code:
    sudo ls -al  /boot/efi
    total 462
    drwx------ 4 root root 1024 Jan 1 1970 .
    drwxr-xr-x 4 root root 4096 Jun 27 12:16 ..
    drwx------ 5 root root 1024 Apr 27 13:06 EFI
    -rwx------ 1 root root 80896 Jan 1 1980 FSCK0000.REC
    -rwx------ 1 root root 80896 Jan 1 1980 FSCK0001.REC
    -rwx------ 1 root root 46080 Jan 1 1980 FSCK0002.REC
    -rwx------ 1 root root 78848 Jan 1 1980 FSCK0003.REC
    -rwx------ 1 root root 79872 Jan 1 1980 FSCK0004.REC
    -rwx------ 1 root root 46080 Jan 1 1980 FSCK0005.REC
    -rwx------ 1 root root 20480 Jan 1 1980 FSCK0006.REC
    -rwx------ 1 root root 32768 Jan 1 1980 FSCK0007.REC
    drwx------ 2 root root 1024 Jul 28 2022 'System Volume Information'
    but of course /boot/efi is mounted at partition 1, from the mount command

    Quote Originally Posted by oldfred View Post
    You do have to make sure fast startup & bitlocker are both off in Windows.
    Won't that affect Kubuntu, as the one lenovo laptop has an internal SSD (windows 8.1) and an external SSD (Kubuntu) ??

    Quote Originally Posted by oldfred View Post
    And really better not to mount the Windows "c:drive" partition, but create a shared NTFS data partition.
    Back with XP I corrupted it multiple times viewing & clicking & moving mouse to fast & it moved folders around.
    It was a bit of a learning exercise, but have now 'shrunk' drive C, made a drive D, and moved all the data, there. Even gave it a label of "Data". Then booted into Kubuntu, and wow, can now see "Data" in Dolphin. I won't bother trying to click on the entry that is causing problems, all the data is where I want it and accessible, thanks.

  10. #10
    Join Date
    Dec 2005
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Error mounting SSD

    Thanks @yancek

    Quote Originally Posted by yancek View Post
    Modifying folders/files (images, music files, etc.) on an ntfs filesystem from Linux should work but modifying any system files on a windows OS from Linux is a bad idea.
    Yes I agree, I only want access to the data. nothing else.

    Quote Originally Posted by yancek View Post
    When you run the ls -al command on /boot/efi/EFI, you should see an ubuntu directory. If you have windows installed also, you should see a Microsoft directory with EFI files in the respective directories. I don't know what the files you shown under efi with the '.REC' extension are and have never seen that before. Can you read those files?
    This is what I see ..

    Code:
    sudo ls -al  /boot/efi/EFI
    total 5
    drwx------ 5 root root 1024 Apr 27 13:06 .
    drwx------ 4 root root 1024 Jan 1 1970 ..
    drwx------ 2 root root 1024 Apr 27 13:06 Boot
    drwx------ 4 root root 1024 Jul 28 2022 Microsoft
    drwx------ 2 root root 1024 Apr 27 13:06 ubuntu
    Quote Originally Posted by yancek View Post
    The exit code 1 error from the mount command you posted means those commands need to be run as root (sudo) and were not.
    Okay thanks

    Quote Originally Posted by yancek View Post
    Your journalctl output clearly shows the 3rd partition (ntfs) needs chkdsk run from windows so that would be the obvious next step if you have not done it and if you have, what was the result?

    You should also check the various parameters for chkdsk to see what would be most appropriate in your case.
    I did run it and all was okay, but now that I have shrunk drive C , added a D: drive, a chkdsk on Drive C: can only be scheduled. I may try that later.

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •