usb HD not reckognized by fdisk

[edwinleboss]

Hello,
Following a messy manipulation of mine (I was loading photos on the external hard drive of a friend with my old laptop under debian, and it seemed to me beuger (I had big videos), so I unplugged while writing (aie ?)), I can't access the content of my disk with my computer (debian too)

Here is a panel of logs that could enlighten you, for info my debian is running on a 1TB SSD and I have a ~300GB HDD :
(in root)

The external HDD is on bus 3 device 002

(base) root@monpc:/# lsusb
Bus 004 Device 002: ID 8087:8001 Intel Corp. Integrated Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 18a5:0429 Verbatim, Ltd Mobile Drive
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 18f8:1485 [Maxxter] USB OPTICAL MOUSE
Bus 002 Device 002: ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard
Bus 002 Device 004: ID 1397:0509 BEHRINGER International GmbH UMC404HD 192k
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
(base) root@monpc:/#

But it doesn't show here :

(base) root@monpc:~# fdisk -l
Disque /dev/sda : 298,09 GiB, 320072933376 octets, 625142448 secteurs
Modèle de disque : WDC WD3200AAJS-0
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0x7bf30af4

Périphérique Amorçage Début       Fin  Secteurs Taille Id Type
/dev/sda1              2048 625141759 625139712 298,1G  7 HPFS/NTFS/exFAT


Disque /dev/sdb : 931,51 GiB, 1000204886016 octets, 1953525168 secteurs
Modèle de disque : CT1000MX500SSD1
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0x0bb32819

Périphérique Amorçage      Début        Fin   Secteurs Taille Id Type
/dev/sdb1    *              2048 1951522815 1951520768 930,6G 83 Linux
/dev/sdb2             1951524862 1953523711    1998850   976M  5 Étendue
/dev/sdb5             1951524864 1953523711    1998848   976M 82 partition d'échange Linux

La partition 2 ne commence pas sur une frontière de cylindre physique.


Disque /dev/loop0 : 116,69 MiB, 122359808 octets, 238984 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets


Disque /dev/loop1 : 116,7 MiB, 122363904 octets, 238992 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
(base) root@monpc:~#

nor here

(base) root@monpc:~# blkid
/dev/sda1: LABEL="Stockage-An" BLOCK_SIZE="512" UUID="5E559407390ADBE8" TYPE="ntfs" PARTUUID="7bf30af4-01"
/dev/sdb1: UUID="0720ec47-d86f-484a-b4bc-554ff9809530" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0bb32819-01"
/dev/sdb5: UUID="e60f611b-0826-4278-8f8c-19ae67196f0f" TYPE="swap" PARTUUID="0bb32819-05"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
(base) root@monpc:~#

and this could help you : disconnected, waited 30s, reconnected, 30s, then

(base) root@monpc:/# dmesg  | tail -20
[  222.718577] usb 3-2: New USB device found, idVendor=18a5, idProduct=0429, bcdDevice= 5.10
[  222.718580] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  222.718581] usb 3-2: Product: Mobile Drive
[  222.718582] usb 3-2: Manufacturer: VIA Labs, Inc.
[  222.718583] usb 3-2: SerialNumber: WL8709547
[  222.737594] usb-storage 3-2:1.0: USB Mass Storage device detected
[  222.738367] scsi host6: usb-storage 3-2:1.0
[  222.738490] usbcore: registered new interface driver usb-storage
[  222.741546] usbcore: registered new interface driver uas
[  244.644161] usb 3-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 4582.246990] usb 3-2: USB disconnect, device number 2
[ 4634.153316] usb 3-2: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 4634.176072] usb 3-2: New USB device found, idVendor=18a5, idProduct=0429, bcdDevice= 5.10
[ 4634.176079] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4634.176083] usb 3-2: Product: Mobile Drive
[ 4634.176086] usb 3-2: Manufacturer: VIA Labs, Inc.
[ 4634.176088] usb 3-2: SerialNumber: WL8709547
[ 4634.177745] usb-storage 3-2:1.0: USB Mass Storage device detected
[ 4634.178369] scsi host6: usb-storage 3-2:1.0
[ 4655.834188] usb 3-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
(base) root@monpc:/#

Thanks for help

 

[osprey]

edwinleboss wrote:

Following a messy manipulation of mine (I was loading photos on the external hard drive of a friend with my old laptop under debian, and it seemed to me beuger (I had big videos), so I unplugged while writing (aie ?)), I can't access the content of my disk with my computer (debian too)

This is a bit unclear to me. I don't know what "beuger" or "aie" mean, and I don't know which disk is being referred to that you cannot access ... is it one of the two disks of "monpc" or the Verbatim Mobile Drive which appears to be a 1 terabyte disk?

The dmesg output shows that the operating system sees the first instance of the Verbatim Mobile Drive as device number 2. It's disconnected, but when it's reconnected, it's seen as device number 3, therefore, not as the same device by the operating system despite it being the same physical device. Since it appears that device number 2 was not unmounted by the umount command, or synchronised transfers with the sync command, that the filesystem in the Verbatim Mobile Drive will likely be disturbed in some way, perhaps corrupted.

One can try and mend linux filesystems with the fsck command which is often successful. That command needs to be run on an unmounted filesystem, for example, from a live disk or rescue disk. There are other ways.

 

[bob466]

You should always remove the Flash Drive/External HDD safely because pulling the USB Device out may cause corruption of the files or file structure / table.

I know one way to fix this...Re-format the Drive but you'll loose everything on it...doesn't look good...you could try ospreys suggestion...good luck.

 

[Deleted member 108694]

aie is french means ouch - I think it is this drive they cannot access
Bus 003 Device 002: ID 18a5:0429 Verbatim, Ltd Mobile Drive
From what I see they unplugged it while it was still writing files and now cannot access it
I agree running fsck is probably your best bet

sudo fsck /dev/sda3

NOTE: where it says sda3 you may have to change that to wherever your drive is actually located