Forum

Full Version: which device is my USB HDD?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
bought a new Samsung M3 1tb usb HDD.
connected to the Pi. Powered up, everithing OK. The disk was recognized, mounted and samba shared automatically. I can write read and delete. Great.

I wanted to format the drive to ext4, for better peformance. I stopped samba, ok.
But I couldn't find which devide the drive is. Here is what I get:

fidsk:
Terminal
root@xbian:/dev# fdisk -l

Disk /dev/mmcblk0: 3947 MB, 3947888640 bytes
4 heads, 16 sectors/track, 120480 cylinders, total 7710720 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000f06a6

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 2048 71679 34816 c W95 FAT32 (LBA)
/dev/mmcblk0p2 71680 7710719 3819520 83 Linux

mount:
Terminal
root@xbian:/dev# mount -l
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=47789,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
tmpfs on /run type tmpfs (rw,nosuid,noatime)
/dev/mmcblk0p2 on / type btrfs (rw,noatime,thread_pool=1,compress=lzo,ssd,space_cache,autodefrag) [xbian-root-btrfs]
none on /sys/kernel/debug type debugfs (rw,relatime)
none on /sys/kernel/security type securityfs (rw,relatime)
none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
none on /run/shm type tmpfs (rw,nosuid,nodev,relatime)
none on /run/user type tmpfs (rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755)
/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,​errors=remount-ro)
/dev/mmcblk0p2 on /home type btrfs (rw,noatime,thread_pool=1,compress=lzo,ssd,space_cache,autodefrag) [xbian-root-btrfs]

df:
Terminal
root@xbian:/dev# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 3.7G 2.2G 1.3G 65% /
udev 10M 4.0K 10M 1% /dev
tmpfs 189M 172K 189M 1% /run
/dev/mmcblk0p2 3.7G 2.2G 1.3G 65% /
none 5.0M 0 5.0M 0% /run/lock
none 189M 0 189M 0% /run/shm
none 100M 0 100M 0% /run/user
/dev/mmcblk0p1 34M 13M 22M 37% /boot
/dev/mmcblk0p2 3.7G 2.2G 1.3G 65% /home

I see the drive mounted in:
/media/SAMSUNG-D680D17280D15997 (or /media/usb0).
It's alive. I can use it. But I can't find which device it is.
Any help? How it is supposed to format the disk?

Thanks
currently with the outputs you posted it is none. could it be it was removed just before you did the df, mount and fdisk outputs?

anyhow, once again available under /media/SAMSUNG-D680D17280D15997, just run this command:
Code:
findmnt -o source -T /media/SAMSUNG-D680D17280D15997

it will show you just the block device name you are looking for.
Hi mk01,

No, the outputs I posted are what I get with the disk alive.
In addition I stopped xbmc after the first post. same commands, same result.

and no luck with the command you give me. here what I get:

Terminal
root@xbian:/media# findmnt -o source -T /media/SAMSUNG-D680D17280D15997
root@xbian:/media# findmnt
TARGET SOURCE FSTYPE OPTIONS
/ /dev/mmcblk0p2[/root/@] btrfs rw,noatime,thread_pool=1,compress=lzo,ssd,space_cache,autodefrag
ââ/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime
â ââ/sys/kernel/debug debugfs rw,relatime
â ââ/sys/kernel/security securityfs rw,relatime
ââ/proc proc proc rw,nosuid,nodev,noexec,relatime
ââ/dev udev devtmpfs rw,relatime,size=10240k,nr_inodes=47789,mode=755
â ââ/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620
ââ/run tmpfs tmpfs rw,nosuid,noatime
â ââ/run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k
â ââ/run/shm tmpfs rw,nosuid,nodev,relatime
â ââ/run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755
ââ/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,e​rrors=remount-ro
ââ/home /dev/mmcblk0p2[/home/@] btrfs rw,noatime,thread_pool=1,compress=lzo,ssd,space_cache,autodefrag

last question: how can I get the size of the disk (/media/usb0)? I would like to check what the system sees.

regards,
diego

(8th Sep, 2013 06:34 AM)mk01 Wrote: [ -> ]currently with the outputs you posted it is none. could it be it was removed just before you did the df, mount and fdisk outputs?

anyhow, once again available under /media/SAMSUNG-D680D17280D15997, just run this command:
Code:
findmnt -o source -T /media/SAMSUNG-D680D17280D15997

it will show you just the block device name you are looking for.

one more:
what is supposed to be in /dev/bus/usb/001? I see three "files" there: 001, 002 and 003.
if there is no /media/SAMSUNG-D680D17280D15997 in the list of "findmnt" without parameters, then the device is not mounted.

if there is no additional device in the list of "fdisk -l" (beside /dev/mmcblk0), then system detected no additional disks.

can you post "dmesg" output to a pastebin.com or somewhere for review?
I think this is a bus powered drive, so I hope it is not connected directly to the RPi. Bus powered drives must always be via a powered hub and not the RPi.

So I wonder if "it" failed after the initial mount.
I finally reinstalled xbian to de SD and now it seems to work.

In addition to what I posted here I found some really strange behaviour trough putty, and a kind of ghost mounted HDD on the /dev/mmcblk0p2 space. This leave no space on the SD partitions. Now I'm starting from zero, but with the drive already formatted to ext4.

And I can tell that is that I really don't think it has to do with the power supply. I use a big linear regulated (7805) PS that feeds the Pi on the GPIO power pins directly. I'm reading the voltage with a tester and it remains stable.

Here what I had on /media before reflash:
SAMSUNG-D680D17280D15997 ---> mistery
SamsungHDD-09d3dad4-9e14-400f-93d9-b6eaa8955392 --> the HDD name after ext4 formatting
usb0 --> alias of SAMSUNG-D680D17280D15997

I also found that SAMSUNG-D680D17280D15997 uses the space of /dev/mmcblk0p2. /dev/mmcblk0p2 is what remains of the SD card. It get full after some write tests supposed to be to the HDD. I deleted SAMSUNG-D680D17280D15997 which seemed to be a folder. Got some space on /dev/mmcblk0p2 gained and link /media/usb0 broken. but after reboot SAMSUNG-D680D17280D15997 and usb0 reappeared, with de SD full.

thanks and regard,
Diego

PS: must I modify the subject with "solved" o something?
run "sudo blkid" and post output.
(11th Sep, 2013 07:56 AM)mk01 Wrote: [ -> ]run "sudo blkid" and post output.
Terminal

root@xbian:/media/usb0# blkid
/dev/mmcblk0p1: SEC_TYPE="msdos" UUID="8B12-9112" TYPE="vfat"
/dev/mmcblk0p2: LABEL="xbian-root-btrfs" UUID="827af4f9-4fcd-4994-bd5a-cab9fba3047c" UUID_SUB="4f549a87-f9dc-4b26-8575-a66f8b85ea5c" TYPE="btrfs"
/dev/zram0: UUID="8194afd5-fbbd-49a2-8637-db7d07be892f" TYPE="swap"
/dev/sda1: LABEL="SamsungHDD" UUID="09d3dad4-9e14-400f-93d9-b6eaa8955392" TYPE="ext4"
/dev/loop0: UUID="86b14831-ec1e-44e2-bfd7-e2b80bc96a1f" TYPE="swap"
root@xbian:/media/usb0#

can you do a

Code:
sudo rmdir /media/SAMSUNG-D680D17280D15997
sudo rm -f /media/usb0
Reference URL's