Announcement

Collapse
No announcement yet.

Error mounting in dolphin

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [SOLVED] Error mounting in dolphin

    Kubuntu is insatlled and its the only OS installed in this PC, This error (Error mounting /dev/sdb1 at /media/nick/Games: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error) started happening today after restaring my pc, before that everything ran fine i have tried ntfsfix and it says:
    Mounting volume... OK
    Processing of $MFT and $MFTMirr completed successfully.
    Checking the alternate boot sector... OK
    NTFS volume version is 3.1.
    NTFS partition /dev/sdc1 was processed successfully.) But in Dolphin i still get the same error

    Help is
    appreciated.

    Kubuntu Version: 24.04
    Plasma Version: 5.27.11
    Information About my pc: System:
    Host: nicolas-main Kernel: 6.8.0-35-generic arch: x86_64 bits: 64
    compiler: gcc v: 13.2.0 clocksource: tsc
    Desktop: KDE Plasma v: 5.27.11 tk: Qt v: 5.15.13 wm: kwin_x11
    with: krunner vt: 2 dm: SDDM Distro: Kubuntu 24.04 LTS (Noble Numbat)
    base: Ubuntu
    Machine:
    Type: Desktop Mobo: ASRock model: B450 Gaming K4
    serial: <superuser required> uuid: <superuser required>
    UEFI: American Megatrends v: P10.08 date: 01/19/2024
    CPU:
    Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP smt: enabled
    arch: Zen 2 rev: 0 cache:L1: 384 KiB L2: 3 MiB L3: 32 MiB
    Speed (MHz):avg: 2316 high: 3600 min/max: 2200/4426 boost: enabled cores:
    1: 2200 2: 2200 3: 2200 4: 2200 5: 2200 6: 2200 7: 3600 8: 2200 9: 2200
    10: 2200 11: 2200 12: 2200 bogomips: 86402
    Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    Graphics:
    Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
    vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2 pcie:
    speed: 16 GT/s lanes: 16 ports:active: DP-3 empty: DP-1, DP-2, HDMI-A-1,
    Writeback-1 bus-ID: 0c:00.0 chip-ID: 1002:73df class-ID: 0300
    Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6
    compositor: kwin_x11 driver:X:loaded: amdgpu
    unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu
    display-ID: :0 screens: 1
    Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
    s-diag: 777mm (30.58")
    Monitor-1: DP-3 mapped: DisplayPort-2 model: LG (GoldStar) ULTRAGEAR
    serial: 104NTDVAX258 res: 2560x1440 hz: 120 dpi: 93
    size: 697x392mm (27.44x15.43") diag: 800mm (31.5") modes:max: 2560x1440
    min: 640x480
    API: EGL v: 1.5 hw:drv: amd radeonsi platforms:device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless:drv: radeonsi x11:drv: radeonsi
    inactive: gbm,wayland
    API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.5-1ubuntu1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6750 XT (radeonsi
    navi22 LLVM 17.0.6 DRM 3.57 6.8.0-35-generic) device-ID: 1002:73df
    API: Vulkan v: 1.3.275 layers: 7 surfaces: xcb,xlib device: 0
    type: discrete-gpu driver: N/A device-ID: 1002:73df device: 1 type: cpu
    driver: N/A device-ID: 10005:0000
    Audio:
    Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 0c:00.1 chip-ID: 1002:ab28 class-ID: 0403
    Device-2: AMD Starship/Matisse HD Audio vendor: ASRock
    driver: snd_hda_intel v: kernel pcie:speed: 16 GT/s lanes: 16
    bus-ID: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
    Device-3: Razer USA USB Sound Card
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 bus-ID: 3-1:2 chip-ID: 1532:0529 class-ID: 0300 serial: 00000000
    API: ALSA v: k6.8.0-35-generic status: kernel-api
    Server-1: PipeWire v: 1.0.5 status: active with:1: pipewire-pulse
    status: active 2: wireplumber status: active
    Network:
    Device-1: Intel Wi-Fi 5 Wireless-AC 9x6x [Thunder Peak] driver: iwlwifi
    v: kernel pcie:speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2526
    class-ID: 0280
    IF: wlp6s0 state: up mac: e4:60:17:d9:e3:47
    Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel pcie:speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 09:00.0 chip-ID: 10ec:8168 class-ID: 0200
    IF: enp9s0 state: down mac: a8:a1:59:31:d5:de
    Bluetooth:
    Device-1: Intel Wireless-AC 9260 Bluetooth Adapter driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-8:2 chip-ID: 8087:0025
    class-ID: e001
    Report: hciconfig ID: hci0 rfk-id: 0 state: up address: E4:60:179:E3:4B
    bt-v: 5.1 lmp-v: 10 sub-v: 100 hci-v: 10 rev: 100 class-ID: 7c0104
    Drives:
    Local Storage:total: 1.03 TiB used: 62.74 GiB (6.0%)
    ID-1: /dev/nvme0n1 vendor: Kingston model: SA2000M8250G size: 232.89 GiB
    speed: 31.6 Gb/s lanes: 4 tech: SSD serial: 50026B768457D45A
    fw-rev: S5Z42105 temp: 28.9 C scheme: GPT
    ID-2: /dev/sda vendor: Micron model: MTFDDAK128MAM-1J1 size: 119.24 GiB
    speed: 6.0 Gb/s tech: SSD serial: 130109235756 fw-rev: 040H scheme: GPT
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0B-00YS70
    size: 465.76 GiB speed: 6.0 Gb/s tech: SSD serial: 20500X803940 fw-rev: 00WD
    scheme: MBR
    ID-4: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
    speed: 6.0 Gb/s tech: SSD serial: S3YJNB0K258540F fw-rev: 1B6Q scheme: GPT
    Partition:
    ID-1: / size: 227.88 GiB used: 62.73 GiB (27.5%) fs: ext4
    dev: /dev/nvme0n1p2
    ID-2: /boot/efi size: 299.4 MiB used: 7.7 MiB (2.6%) fs: vfat
    dev: /dev/nvme0n1p1
    Swap:
    ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
    Sensors:
    System Temperatures:cpu: 37.8 C mobo: N/A gpu: amdgpu temp: 39.0 C
    mem: 38.0 C
    Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
    Info:
    Memory:total: 16 GiB available: 15.54 GiB used: 3.43 GiB (22.1%)
    Processes: 331 Power:uptime: 9m states: freeze,mem,disk suspend: deep
    wakeups: 0 hibernate: platform Init: systemd v: 255 target: graphical (5)
    default: graphical
    Packages: 2588 pm: dpkg pkgs: 2548 pm: flatpak pkgs: 31 pm: snap pkgs: 9
    Compilers: N/A Shell: Bash v: 5.2.21 running-in: konsole inxi: 3.3.34
    Last edited by oshunluvr; Jun 06, 2024, 08:28 AM.

    #2
    You may need to use a Windows machine to run a proper chkdsk on the drive. ntfsfix does not do much more that clearing the 'dirty' status, iirc, and not much else. There really aren't any good tools for fixing ntfs filesystems, as far as I know.

    Being a Linux-only system, you may want to consider migrating the drive to a Linux friendly one that can be repaired easier.

    Comment


      #3
      My first thought is why are you using arguably the worst file system out there when there are so many better ones to choose from? Left over from windows and just didn't reformat it?

      Regardless, IMO trying to fix it is a waste of time. Mount it, backup any files you want to save, and reformat it using literally any file system except NTFS.

      Please Read Me

      Comment


        #4
        I geuss imma change the file system then, what would be the best one to use?

        Comment


          #5
          I'd use ext4 just to be compatible with Kubuntu. I have moved all my data over to 0.5 TB of SSD's and going from NTFS to ext4 (vice versa) you will have errors with naming of the files. You will have to be patient and just rename them. Sometimes the system transfering (like dolphin or krusader) might offer you a naming option when the error pops up, which I usually pick so I don't go nuts. So I move all my stuff to SSDs and then I heard that spinning hard discs are more reliable over the long haul. Plus they are cheap now. If I had done it on a spinner I'd feel better about keeping the data preserved. Those are just my tho'ts. Take care.

          Comment


            #6
            Reformatting the drive is called "New Partition Table". This is good for clearing out the messy Windows partitions, but of course, all data are lost, be very sure where you are doing it.

            There's a lot of btrfs fans here at kubuntuforums.net. btrfs enables a lot of functions that traditional file systems don't have, but you have to learn a bit. If it's not a OS drive, and you don't need it to be readable by other OSs, just make the whole drive one btrfs.
            Regards, John Little

            Comment


              #7
              ext4 is good and stable. There are several btrfs believers - not me. But, either way with either file system you'll be in MUCH better shape.

              I use fat32 on a USB if I need to transfer files to or from somewhere, since both Linux and Windows understand it. There's not much use for NTFS as an intermediary. Of course for an ESP, fat32 is a necessary thing.
              The next brick house on the left
              Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic



              Comment


                #8
                Ok thanks, im gonna use ext4

                Comment


                  #9
                  Originally posted by jglen490 View Post
                  There are several btrfs believers
                  Lol, more than several
                  A system rollback of one's @root and/or @home to any previous state, including the original install, taking only a few seconds plus a normal reboot is usually all it takes to become a cult member fan, even if one never uses all the other fancy parts of it.
                  But for non-OS drives, it might not be needed as much, though it doesn't hurt anything.

                  Comment


                    #10
                    The ancient EXT4 by default "reserves" (hides) 5% of drive space for system use.This "need" is left over from the 1990s when EXT4 was more current. If you decide to use EXT4 you can free up this space after formatting with: sudo tune2fs -m 0 /dev/sdb1 Obviously, replace sdb1 with whatever partition you put EXT4 on.

                    BTRFS is a significantly advanced modern file system with many built-in advanced features such as:
                    • Containerizing data sets (groups of file and folders) into subvolumes.
                      • This allows separating data such as the installation from home obviating the need for multiple partitions and allowing all subvolumes to share free space.
                    • Subvolume snapshots.
                    • Built-in backup and file system transport (moving to another partition or drive) capability.
                    • Built-in support for multiple devices (more than one drive or partition combined into a single file system)..
                    • Devices can be added or removed (space providing of course) at will
                    • Built-in RAID support of many different (almost all) levels.
                    • All of the above functionality can be accessed while the file system is mounted and in use.
                    Choosing BTRFS is not a question of "belief", rather it's choosing a file system that's advanced, featured, and modern vs. one that's outdated and un-featured.

                    If you're sharing file systems with a Windows install, ExFAT is a good choice for portable devices and is also usable on a fixed drive partition if you dual boot with Windows. I prefer ExFAT for portable devices because EXT4 requires manual permission modifications before a non-root user can access the file system. It was really not intended to be used on portable devices and BTRFS isn't really well suited for them either.

                    The are many other file systems but most are for special or specific use-cases. For example, some distros use XFS by default for home or storage file system because it is generally better at large file support and has multi-device support.

                    Please Read Me

                    Comment


                      #11
                      Like I said, "some" believers

                      I will admit that recovery is a bit easier, but what claydoh described is not a backup solution. On the other hand, other than actual hardware failure, I've never experienced a need to recover my OS.
                      Last edited by jglen490; Jun 07, 2024, 06:25 AM.
                      The next brick house on the left
                      Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic



                      Comment


                        #12
                        Concerning "Choosing BTRFS is not a question of "belief"..." reading these posts has me sold for a new 2TB drive, but there is no BTRFS option in KDE Partition Manager. Is more info available? I will be researching this after my PT X ercises

                        I added this. ran a couple commands in terminal... btrfs
                        'sudo apt update'

                        Install the Btrfs filesystem, execute the following apt command with sudo:

                        'sudo apt install btrfs-progs'

                        I also ran 'sudo apt autoremove' upon the suggestion of terminal...

                        Got this per https://www.linuxfordevices.com/tuto...trfs-on-ubuntu BUT ...I finished w/ the autoremove and went to KDE Partition Manager & btrfs was the first suggestion. I didn't us cfdisk partition manager per article suggestion.
                        Last edited by spiderman; Aug 11, 2024, 05:02 PM.

                        Comment


                          #13
                          Originally posted by spiderman View Post
                          Concerning "Choosing BTRFS is not a question of "belief"..." reading these posts has me sold for a new 2TB drive, but there is no BTRFS option in KDE Partition Manager. Is more info available? I will be researching this after my PT X ercises
                          It's there, you may have to scroll up instead of down in the selection drop-down.

                          Originally posted by jglen490 View Post

                          I will admit that recovery is a bit easier, but what claydoh described is not a backup solution. On the other hand, other than actual hardware failure, I've never experienced a need to recover my OS.​
                          No, it isn't a backup. But it is good for a rollback, say when an update or upgrade goes south, or when you've effed something up but don't have the time to figure out a fix. Or have a quick way to find a particular file you deleted, or an older version. Or restoring a broken, incomplete, missing, or corrupted backup set on an external drive or NAS.

                          A bit extra piece of mind for the most minimal of efforts.

                          Comment


                            #14
                            Problem mounting NTFS external drives is a known bug in 24.04.
                            Solution : blacklist the ntfs3 driver from running.

                            From command line :
                            echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/disable-ntfs3.conf

                            Then reboot.

                            ​[SOURCE : https://bugs.launchpad.net/ubuntu/+s...bug/2062972​ ]

                            Comment

                            Working...
                            X