Hard drive mounting woes
Hello everyone!
I needed to transfer 1TB (SATA; MBR; EXFAT) drive to a 2TB drive (SATA; GPT; EXFAT). I connected both via USB 2.0 to my laptop running Debian Wheezy. ETA: few days. I decided I will speed things up by building a Debian 8.1 box and hooking up both drives with SATA instead of USB 2.0. I installed the drives. Installed exfat-fuse and exfat-utils. Mounting the 1TB drive was a breeze. But then mounting the 2TB proved to be a two day failing endevour: Code:
root@vox:/home/o# sfdisk -l here is the output from GParted on my Debian 8.1 box: http://s11.postimg.org/y8w7i1rv7/Scr...3_22_37_15.png Code:
root@vox:/home/o# mount -t exfat /dev/sdc1 /home/o/2tb/ Code:
root@vox:/home/o# mount -t exfat /dev/sdc2 /home/o/2tb/ What's going on? To be sure, I disconnect the drive and put it back into the usb enclosure and connect it back to my laptop: Voila! It even automounts! Code:
root@laptop:# sfdisk -l http://s17.postimg.org/s0nkae3pr/Scr...3_22_27_26.png |
Did you run an "ls" on /dev/ to see if sdc# was there?
I've only run into something like this once, it was with a RAID, but the symptoms were similar: fdisk reports a partition that doesn't exist in /dev/. Here is my thread on the issue, nobody responded but I managed to fix it on my own: http://www.linuxquestions.org/questi...ng-4175444903/ Cliffnotes: "partprobe /dev/md126" (or in your case "partprobe /dev/sdc") was able to restore a corrupt GPT table and created the /dev/md126p# (/dev/sdc# in your case) partitions so that I could mount them and go about my business. |
Quote:
Thanks suicidaleggroll! "ls" shows only sdc! Mystery is starting to unravel! I tried "partprobe /dev/sdc" and then "ls" and it is still the same. Also please note how simply the drive mounts on my laptop... I'm just flored at the mystery. |
According to the snapshot you posted the drive is /dev/sdc and does not contain any filesystem. You cannot mount it without a filesystem on it.
lsblk will show you a tree like of the drives that your system sees, mounted and unmounted. cat /proc/partitions will also show you what the kernel sees for devices. |
Quote:
Here is the output on the "vox" (Debian 8.1 box): Code:
root@vox:# lsblk Code:
root@vox:# cat /proc/partitions here is the output of the same commands on the laptop: Code:
root@laptop:# lsblk Code:
root@laptop:# cat /proc/partitions |
Quote:
Your system is not seeing any partitions on that drive. As far as it is concerned, it does not have a partition. |
Quote:
As you see here, it was already established above that the partitions arent recognized. Now how to fix this issue? |
Quote:
|
Quote:
Brilliant suggestion! I assume you can tell me how to get SATA speeds with USB 2.0? :scratch: (The original goal, as stated, is to increase the transfer speed from USB 2.0 speeds to SATA speeds.) |
What distro (version) are you running on the laptop (is it older) ?.
Has the problem disk been used on Win10 ?. |
Quote:
Also I wanted to confirm that the drive in question automounts on "vox" via external USB enclosure (just as it automounts on the laptop). This issue specifically arrises when the drive is connected in "vox" via SATA cable. |
The reason I asked is that Win10 (preview) appears to mangle gpt disks - it force mounts as MBR but leaves (and ignores) the gpt header (might only occur on re-install).
Confuses the hell out of the Linux tools. Not sure if Win8{.1} does likewise as I never allowed it in the house. Older versions of the Linux tools may not be so particular about the gpt header. |
Thanks syg00! I figured Windows 10 did something weird to the MBR.
|
Quote:
|
Quote:
|
All times are GMT -5. The time now is 05:06 AM. |