Error mounting dev sdb1 at run media

How I can fix the Error mounting /dev/sdb1 at /media/... It works pretty good in the past but I made a clean installed of Ubuntu 14.04 LTS and the Error mounting coming. I try to fix it with with G...

How I can fix the Error mounting /dev/sdb1 at /media/… It works pretty good in the past but I made a clean installed of Ubuntu 14.04 LTS and the Error mounting coming.
I try to fix it with with Gparted, ntfs-3g, pmount, but this programs can’t find the external HDD.
But when I boot put the USB drive with Ubuntu 14.04 on test mode this can find and read my external HDD.
How I can fix it?

asked Feb 16, 2015 at 22:09

Quantum Jumping's user avatar

Quantum JumpingQuantum Jumping

1,1414 gold badges13 silver badges15 bronze badges

open terminal with Ctrl+Alt+T and run

sudo ntfsfix /dev/sdb1 

A.B.'s user avatar

A.B.

87.7k21 gold badges242 silver badges317 bronze badges

answered Nov 11, 2015 at 10:43

sri harika's user avatar

6

Run this command to show disks:

lsblk

Run this command to mount usb:

sudo ntfsfix /dev/sdb

/dev/sdb or /dev/sdb1 or some other path

answered Oct 5, 2018 at 8:12

Taimoor Changaiz's user avatar

1

It might be the case that the naming changes when you try the drive on different things. ( sdb becomes sdX because of how the usbs are enumerated)
Open a terminal and play with:

lsblk
blkid

If you are still unsure, then try

dmesg | more 

and read the system log, at one point you should see something similar to:

150289.144120] scsi 7:0:0:0: Direct-Access     WDC WD32 00BEKT-22KA9T0   01.0 PQ: 0 ANSI: 5
[150289.144951] sd 7:0:0:0: Attached scsi generic sg4 type 0
[150289.145185] sd 7:0:0:0: [sdd] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[150289.145854] sd 7:0:0:0: [sdd] Write Protect is off
[150289.145863] sd 7:0:0:0: [sdd] Mode Sense: 23 00 00 00
[150289.146547] sd 7:0:0:0: [sdd] No Caching mode page found
[150289.146555] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[150289.212988]  sdd: sdd4
[150289.215143] sd 7:0:0:0: [sdd] Attached SCSI disk

If not, then try different usb ports, some usb are full powered, some half powered, some mother board don’t like usb3 devices on usb2 slots..

answered Feb 17, 2015 at 2:50

user283885's user avatar

user283885user283885

4462 silver badges5 bronze badges

16

I got the same error, but in my case, it wasn’t because of a corrupted NTFS, but because Ubuntu didn’t recognize that the disk was formatted as exFAT. I could open the disk with no problem in Windows. Then I checked the format and saw that it was exFAT. To open it in Linux I installed:

$ sudo apt install exfat-fuse exfat-utils

And the disk could open without any issue.

Simon Sudler's user avatar

Simon Sudler

3,5952 gold badges17 silver badges31 bronze badges

answered Sep 13, 2019 at 10:15

realnewton's user avatar

I used this ntfsfix package to check my external drive

sudo ntfsfix /dev/sdb 

But in some case this /dev/sdb can be /dev/sda1 or /dev/sda2

answered May 20, 2022 at 21:08

Bercove's user avatar

BercoveBercove

1811 silver badge4 bronze badges

This happens because of the way Pacman upgrades the kernel. The current kernel (and modules) are removed and replaced with the new ones. It’s like yanking a carpet from beneath someone’s feet. Therefore, if you have not previously loaded the proper modules for an action (mounting a FAT32 USB, connecting to a SAMBA share, using autofs, encrypting a file, et al), upon trying the action, it will spit out errors because the modules for the current kernel were removed during the upgrade. This is a very poor upgrade procedure that has plagued Arch Linux for a long time now. Distros like Ubuntu and Fedora do not remove the current kernel and its modules upon upgrading the system. Sadly, even openSUSE suffers this same problem. (It has a workaround, but it requires editing zypp.conf.)

Here is an example:

Let’s say you are currently running kernel 3.3.4, but you have not plugged in a FAT32 USB stick yet. The vfat module is likely not loaded. Then you run a pacman update, and it upgrades the kernel to 3.3.5. Now upon inserting a FAT32 USB stick, it tries to load the vfat module for the current 3.3.4 kernel, but it is nowhere to be found since pacman has deleted everything related to kernel 3.3.4! This is why you need to reboot your system into the new (3.3.5) kernel in order to mount your USB stick.

With Ubuntu, for example, it keeps the current kernel untouched when you update the system, so that all your modules for the current kernel remain, and thus you do not bump into this problem. Not only are kernel updates less frequent in a distro like Ubuntu, but they do not create this problem anyways.

«Report a bug!» you might say. Well, a bug has been reported almost 3 years ago: https://bugs.archlinux.org/task/16702

phrakture wrote:

This isn’t really about kernel stability. It’s more about the fact that if I upgrade my kernel, I can no longer plug in usb devices until I reboot, which is a tad goofy.

Sound familiar?

Last edited by flan_suse (2012-05-09 15:17:47)

When I tried mounting an external hard drive connected via usb I got the error quoted below. So far I’ve tried using ntfsfix and chkdsk. My operating system is Arch Linux and the drive is NTFS formatted.

Error mounting /dev/sdb1 at /run/media/ssb/HITACHI: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=100,dmask=0077,fmask=0177" "/dev/sdb1" "/run/media/ssb/HITACHI"' exited with non-zero exit status 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Failed to calculate free MFT records: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

Here’s the output of sudo ntfsfix /dev/sdb1:

$ sudo ntfsfix /dev/sdb1
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/sdb1 was processed successfully.

Диск SATA-NTFS начал глючить. Я скинул все на комп и отформатировал его. После начал перекидывать на него фильмы. Скачалось несколько и выдало ошибку —

Error mounting /dev/sdb1 at /media/ura/U: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sdb1" "/media/ura/U"' exited with non-zero exit status 13: $MFTMirr does not match $MFT (record 0).
Failed to mount '/dev/sdb1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

Сейчас просто диск не подключается.
Прошу конкретной помощи.

Забыл написать что при подключении к телевизору через приставку DTV все отлично воспроизводит

Не редко пользователи ОС Ubuntu при подключении USB с файловой системой NTFS накопителя могут наблюдать ошибку: «Error mounting /dev/sdb1» или «Failed to mount ‘/dev/sdb1’: Input/output error».

Каджый файл в системе NTFS имеет соответсвующую запись в MFT (Master File Table / Основная Файловая Таблица). NTFS резервирует первые 16 записей MFT для хранения специальной информации. Первая запись описывает непосредственно сам MFT, за ней идёт описание резервной MFT mirror записи. Если первая запись в MFT будет повреждена, то NTFS будет читать вторую запись, чтобы найти MFT mirror, первая запись которой идентична первой записи в MFT. Месторасположение MFT и MFT mirror прописано в boot sector диска.
Источник: NTFS.com

После некорректного извлечения USB-диска, перебоя в питании и по другим причинам может повредиться MFT и первая запись MFT mirror не будет совпадать с первой записью MFT.

Решить проблему поможет утилита ntfsfix:
sudo ntfsfix /dev/sdb1
* /dev/sdb1 — нужно указать тот раздел, который упоминается в тексте ошибки.

Если утилита ntfsfix не доступна, её можно установить с пакетом ntfs-3g:
sudo apt-get install ntfs-3g

После использования ntfsfix нужные для инициализации данные на устройстве будут восстановлены как и доступ к USB-устройству.

  • Форум русскоязычного сообщества Ubuntu »
  • Архив »
  • Архив »
  • Архив тем до 2018г »
  • не монтируется диск
  • Печать

Страницы: [1]   Вниз

Тема: не монтируется диск  (Прочитано 1808 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
mityai78

Не могу потключить диск.Выдаёт Ошибку.

Asus x99s,Intel® Core™ i7-5820K CPU @ 3.30GHz × 12,GeForce GTX1050Ti,32GB RAM,Kubuntu,Ubuntu 21.04-х64 Iron Maiden


Оффлайн
ALiEN175

не все скопировали. Что после failed: ?

ASUS P5K-C :: Intel Xeon E5450 @ 3.00GHz :: 8 GB DDR2 :: Radeon R7 260X :: XFCE
ACER 5750G :: Intel Core i5-2450M @ 2.50GHz :: 6 GB DDR3 :: GeForce GT 630M :: XFCE


Оффлайн
symon.2014

Заодно покажите

sudo fdisk -l


Оффлайн
EvangelionDeath

mityai78, а что там после failed ? Какая ОС? Что там на диске?

« Последнее редактирование: 10 Декабря 2017, 15:09:49 от EvangelionDeath »

HP Pro 840 G3: Intel i5-6300U, 32GB DDR4 2133MHz, Intel 520, Intel Pro 2500 180GB/Ubuntu 22.04
Dell Latitude 5590: Intel i5-8350U, 16GB DDR4 2400MHz, Intel 620, Samsung 1TB/Ubuntu 22.04


Оффлайн
mityai78

Заодно покажите
sudo fdisk -l


Пользователь добавил сообщение 10 Декабря 2017, 15:06:51:


не все скопировали. Что после failed: ?


Пользователь добавил сообщение 10 Декабря 2017, 15:09:11:


Не могу потключить диск.Выдаёт Ошибку.

ubuntu 16.04.3

« Последнее редактирование: 10 Декабря 2017, 15:09:11 от mityai78 »

Asus x99s,Intel® Core™ i7-5820K CPU @ 3.30GHz × 12,GeForce GTX1050Ti,32GB RAM,Kubuntu,Ubuntu 21.04-х64 Iron Maiden


Оффлайн
EvangelionDeath

mityai78, смотрите мое сообщение под спойлером)
ну и все же придется обновить e2fsprogs

Да, и покажите

e2fsck -V

« Последнее редактирование: 10 Декабря 2017, 15:11:08 от EvangelionDeath »

HP Pro 840 G3: Intel i5-6300U, 32GB DDR4 2133MHz, Intel 520, Intel Pro 2500 180GB/Ubuntu 22.04
Dell Latitude 5590: Intel i5-8350U, 16GB DDR4 2400MHz, Intel 620, Samsung 1TB/Ubuntu 22.04


Оффлайн
ALiEN175

mityai78, использовали ext2fsd под Windows? Больше не используйте.

Просто выполните проверку диска.

ASUS P5K-C :: Intel Xeon E5450 @ 3.00GHz :: 8 GB DDR2 :: Radeon R7 260X :: XFCE
ACER 5750G :: Intel Core i5-2450M @ 2.50GHz :: 6 GB DDR3 :: GeForce GT 630M :: XFCE


Оффлайн
mityai78

mityai78, использовали ext2fsd под Windows? Больше не используйте.

Просто выполните проверку диска.

Запускал windows с флэшки.


Пользователь добавил сообщение 10 Декабря 2017, 15:16:53:


mityai78, смотрите мое сообщение под спойлером)
ну и все же придется обновить e2fsprogs

Да, и покажите

e2fsck -V

~$ e2fsck -V
e2fsck 1.42.13 (17-May-2015)
   Using EXT2FS Library version 1.42.13, 17-May-2015


Пользователь добавил сообщение 10 Декабря 2017, 15:28:15:


mityai78, использовали ext2fsd под Windows? Больше не используйте.

Просто выполните проверку диска.

Подскажи команды для проверки.

« Последнее редактирование: 10 Декабря 2017, 15:28:15 от mityai78 »

Asus x99s,Intel® Core™ i7-5820K CPU @ 3.30GHz × 12,GeForce GTX1050Ti,32GB RAM,Kubuntu,Ubuntu 21.04-х64 Iron Maiden


Оффлайн
EvangelionDeath

mityai78, Вы так под спойлер и не заглянули)

sudo fsck /dev/sdb1
sudo fsck /dev/sdb2

HP Pro 840 G3: Intel i5-6300U, 32GB DDR4 2133MHz, Intel 520, Intel Pro 2500 180GB/Ubuntu 22.04
Dell Latitude 5590: Intel i5-8350U, 16GB DDR4 2400MHz, Intel 620, Samsung 1TB/Ubuntu 22.04


Оффлайн
mityai78

mityai78, Вы так под спойлер и не заглянули)
sudo fsck /dev/sdb1
sudo fsck /dev/sdb2

Asus x99s,Intel® Core™ i7-5820K CPU @ 3.30GHz × 12,GeForce GTX1050Ti,32GB RAM,Kubuntu,Ubuntu 21.04-х64 Iron Maiden


Оффлайн
EvangelionDeath

mityai78, ну так там же и под спойлером сказано было, что наверное придется обновить и e2fsprogs (metadata_csum как бы есть с ядра 3.39 вроди, а вот реализовано оно в e2fsprogs только в 1.43)

wget https://kent.dl.sourceforge.net/project/e2fsprogs/e2fsprogs/v1.43.7/e2fsprogs-1.43.7.tar.gz
tar xzf e2fsprogs-1.43.7.tar.gz
cd e2fsprogs-1.43.7
sudo apt-get update
sudo apt-get install libc6-dev
./configure
make
cd e2fsck
sudo ./e2fsck /dev/sdb1
sudo ./e2fsck /dev/sdb2
e2fsck 1.43 идет в комплекте с 17.04 и выше

« Последнее редактирование: 10 Декабря 2017, 16:16:26 от EvangelionDeath »

HP Pro 840 G3: Intel i5-6300U, 32GB DDR4 2133MHz, Intel 520, Intel Pro 2500 180GB/Ubuntu 22.04
Dell Latitude 5590: Intel i5-8350U, 16GB DDR4 2400MHz, Intel 620, Samsung 1TB/Ubuntu 22.04


  • Печать

Страницы: [1]   Вверх

  • Форум русскоязычного сообщества Ubuntu »
  • Архив »
  • Архив »
  • Архив тем до 2018г »
  • не монтируется диск

SMF 2.0.19 |
SMF © 2011, Simple Machines | Карта форума

Страница сгенерирована за 0.044 секунд. Запросов: 23.

  • Home
  • Forum
  • The Ubuntu Forum Community
  • Ubuntu Official Flavours Support
  • General Help
  • [SOLVED] Error Mounting Message /dev/sdb at /media…

  1. Error Mounting Message /dev/sdb at /media…

    Ubuntu 17.10

    Hello everyone, thanks in advance for any help.

    The system opens fine, but when I click on the hard drive 1TB location I get a window message:

    Can’t access location
    Error mounting /dev/sdb at /media/this-is-my-user/1TB: Command-line `mount -t «ext4» -o «uhelper=udisks2,nodev,nosuid» «/dev/sdb» «/media/this-is-my-username/1TB»‘ exited with non-zero status 32: mount: /media/this-is-my-user/1TB: can’t read superblock on /dev/sdb

    I can’t copy paste the message so I gess all this double (triple) quotes are right.

    System is brand new, but after copying data from an external drive to the TeraByte (TB) I guess something went wrong and after booting I could not get the TB partition any more.

    I would very much appreciate some help.
    Thanks very much.


  2. Re: Error Mounting Message /dev/sdb at /media…

    allosaurus66; Hummmm …

    Well, we know we have to run some kind of file system check/repair:

    mount: /media/this-is-my-user/1TB: can’t read superblock on /dev/sdb

    so let’s see if we can find out what we are working with.
    Post back — Between Code Tags — the output of terminal commands:

    Code:

    sudo parted -l
    cat /etc/fstab

    code tag tutorial:
    http://ubuntuforums.org/showthread.p…8#post12776168

    Depending what shows ->

    is what we do next


  3. Re: Error Mounting Message /dev/sdb at /media…

    It should be /dev/sdb1 (or sdb2, etc). I don’t know why the GUI would try to mount it like that. Maybe output of the commands Bashing-om suggested will give us a clue.


  4. Re: Error Mounting Message /dev/sdb at /media…

    Many thanks for your interest Bashing-om,

    the command mount, with my proper user name:

    Code:

    mount: /media/this-is-my-user/1TB: can't read superblock on /dev/sdb

    gives me an arrow like:
    >


    for which I am too newbie to continue.

    After


    I get:

    Code:

    Modelo: ATA KINGSTON SA400S3 (scsi)
    Disco /dev/sda: 240GB
    Tama�o de sector (l�gico/f�sico): 512B/512B
    Tabla de particiones: gpt
    Disk Flags: 
    
    Numero  Inicio  Fin    Tama�o  Sistema de archivos  Nombre                Banderas
     1      1049kB  538MB  537MB   fat32                EFI System Partition  arranque, esp
     2      538MB   240GB  240GB   ext4
    
    
    Modelo: ATA ST1000DM010-2EP1 (scsi)
    Disco /dev/sdb: 1000GB
    Tama�o de sector (l�gico/f�sico): 512B/4096B
    Tabla de particiones: loop
    Disk Flags: 
    
    Numero  Inicio  Fin     Tama�o  Sistema de archivos  Banderas
     1      0,00B   1000GB  1000GB  ext4

    Also the
    gives me this:

    Code:

    # /etc/fstab: static file system information.
    #
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    # / was on /dev/sda2 during installation
    UUID=5d633fae-92ff-48d8-a17f-624ff459fd48 /               ext4    errors=remount-ro 0       1
    # /boot/efi was on /dev/sda1 during installation
    UUID=8651-E876  /boot/efi       vfat    umask=0077      0       1
    /swapfile


  5. Re: Error Mounting Message /dev/sdb at /media…

    allosaurus66; Welp —

    Not totally unexpected results —

    Before we proceed with the file system check and the attempted repair .. are you sure you are happy to devote ONE TB to a single partition ?

    See then what results:
    https://help.ubuntu.com/community/Fi…roubleshooting <- Basic filesystem checks and repairs

    #-> From liveUSB/DVD <- so everything is unmounted,swap off if necessary,

    #e2fsck is used to check the ext2/ext3/ext4 family of file systems. -p tries fixes where response not required

    Code:

    sudo e2fsck -C0 -p -f -v /dev/sdb1

    #if errors; which I do expect ! -y auto answers yes for fixes needing response see: man e2fsck

    Code:

    sudo e2fsck -f -y -v /dev/sdb1

    fsck http://www.thegeekstuff.com/2012/08/…mand-examples/

    Here if it errors out, post that output ! As it:
    Remains a possibility/probability that we will have to lend a hand manually and replace the superblock from backups.

    ain’t no step for a stepper


  6. Re: Error Mounting Message /dev/sdb at /media…

    Thx,
    Before I ran the checks, would you have a a TB in more than one partition?


  7. Re: Error Mounting Message /dev/sdb at /media…

    Shouldn’t you be trying to mount /dev/sdb1, not the device /dev/sdb.


  8. Re: Error Mounting Message /dev/sdb at /media…

    I think you formatted drive, and did not even create sdb1 partition.

    Code:

    Modelo: ATA ST1000DM010-2EP1 (scsi)
    Disco /dev/sdb: 1000GB
    Tama�o de sector (l�gico/f�sico): 512B/4096B
    Tabla de particiones: loop

    Should be gpt or dos/msdos/MBR type partitioning.


  9. Re: Error Mounting Message /dev/sdb at /media…

    I explained wrong from the beginning. Sorry my tech language. I have 2 hard drives one is 250 GB the other is 1TB. I said partition wrongly.

    Last edited by allosaurus66; March 12th, 2018 at 09:48 PM.


  10. Re: Error Mounting Message /dev/sdb at /media…

    allosaurus66; Hey — hey

    Your ‘parted -l’ output:

    Tabla de particiones: loop

    where we expect something like my output:

    sysop@x1604:/$ sudo parted -l
    Model: ATA Samsung SSD 850 (scsi)
    Disk /dev/sda: 250GB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos
    Disk Flags:

    Number Start End Size Type File system Flags
    1 1049kB 149GB 149GB primary ext4 boot
    2 149GB 165GB 15.7GB extended
    5 149GB 154GB 4719MB logical linux-swap(v1)

    We propose that you do not have any partitions on that 1TB drive . While one can do that ,, it IS NOT a good practice, and will lead to serious addressing issues . How about at this point partitioning that drive in a useful format ?

    just my thought on the natter


Tags for this Thread

Bookmarks

Bookmarks


Posting Permissions

Понравилась статья? Поделить с друзьями:
  • Error mounting dev sdb1 at media флешка
  • Error mounting dev sdb1 at media unknown filesystem type ntfs
  • Error mounting dev sdb1 at media unknown filesystem type exfat
  • Error mounting dev sdb1 at media ubuntu
  • Error mounting dev sda5