Announcement

Collapse
No announcement yet.

Hard drive information . . . but I don't entirely understand what I'm looking at

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Hard drive information . . . but I don't entirely understand what I'm looking at

    I have a home-built machine that has internal 1Tb and 1.5Tb drives and also has USB drives of 300G and 200G attached. When I go into Dolphin, I'm not seeing the drives I expect. I see the USB drives all right, but there are also two Places in the left-hand panel that are designated as "232.8 GiB Hard Drive." To get into those (but not the USB drives), I have to enter my password. I cannot, however, copy anything to those drives; the "Paste one file" option is greyed out. I'm not sure what happened to my internal hard drives, but they do not seem to be visible. At least one of them is clearly mounted and functioning, because that's what's running Kubuntu.
    So, in my ignorance, I went and collected some information, though I cannot warrant that it's the right information. I ran "df -i" and got the following output:
    Filesystem Inodes IUsed IFree IUse% Mounted on
    /dev/sda1 30523392 262062 30261330 1% /
    none 764372 1016 763356 1% /dev
    none 765499 1 765498 1% /dev/shm
    none 765499 78 765421 1% /var/run
    none 765499 3 765496 1% /var/lock
    none 765499 1 765498 1% /lib/init/rw
    /dev/sda6 39452672 100491 39352181 1% /home
    /dev/sda5 21610496 428 21610068 1% /usr/local

    Then I ran fdisk and got this:
    Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
    255 heads, 63 sectors/track, 182401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x000edf3c

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 60789 488281250 83 Linux
    /dev/sda2 60789 182402 976856065 5 Extended
    /dev/sda5 60789 103824 345679023+ 83 Linux
    /dev/sda6 103824 182402 631176192 83 Linux

    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x000992d9

    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 30394 244139773+ 83 Linux
    /dev/sdb2 30395 121601 732620197 5 Extended
    /dev/sdb5 30395 60788 244139773+ 83 Linux
    /dev/sdb6 60789 72946 97659103+ 82 Linux swap / Solaris
    /dev/sdb7 72947 121601 390821256 b W95 FAT32

    Disk /dev/sdc: 300.1 GB, 300069052416 bytes
    255 heads, 63 sectors/track, 36481 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xc00d83ac

    Device Boot Start End Blocks Id System
    /dev/sdc1 2 36481 293025600 f W95 Ext'd (LBA)
    /dev/sdc5 2 36481 293025568+ 7 HPFS/NTFS

    Disk /dev/sdd: 203.9 GB, 203928109056 bytes
    255 heads, 63 sectors/track, 24792 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x186d8bef

    Device Boot Start End Blocks Id System
    /dev/sdd1 1 24793 199146496 7 HPFS/NTFS

    Finally, I opened fstab and saw the following:
    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s UUID' 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>
    proc /proc proc nodev,noexec,nosuid 0 0
    # / was on /dev/sda1 during installation
    UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 / ext4 errors=remount-ro 0 1
    # /home was on /dev/sda6 during installation
    UUID=0b8dca5a-68f0-4dd2-a079-973e33c2422c /home ext4 defaults 0 2
    # /usr/local was on /dev/sda5 during installation
    UUID=5f0002ff-f46a-4bd7-bab9-dd812dd09437 /usr/local ext4 defaults 0 2
    # swap was on /dev/sdb6 during installation
    UUID=8f917536-06a9-4114-a5ba-e355c18016a4 none swap sw 0 0

    (Remember: I said I saw it, not that I understood it.) I think what I'm dealing with here is my own basic misunderstanding of how partitions, drives and file systems work on Linux. Can someone point me in the right direction? Thanks.

    #2
    Re: Hard drive information . . . but I don't entirely understand what I'm looking at

    To clarify the situation, I would say disconnect the external USB drives -- they may be one source of confusion.

    Then use oshunluvr's excellent blkid command:

    Code:
    blkid -c /dev/null -o list
    and see what you have.

    Comment


      #3
      Re: Hard drive information . . . but I don't entirely understand what I'm looking at

      Here's the output from oshunlvr's code:

      device fs_type label mount point UUID
      --------------------------------------------------------------------
      /dev/sda1 /
      /dev/sda5 /usr/local
      /dev/sda6 /home
      /dev/sdb1 /media/disk
      /dev/sdb5 (not mounted)
      /dev/sdb6 <swap>
      /dev/sdb7 (not mounted)

      So, am I right that the "missing" space is probably on (in?) sdb5 and sdb7, which I need to mount? If so, I think the syntax is "mount -t sbd5" but what should I specify as the directory?

      Comment


        #4
        Re: Hard drive information . . . but I don't entirely understand what I'm looking at

        You would have to make a mount point, for example

        Code:
        sudo mkdir -p /mnt/MYRANDOMSTUFF
        Then you add a line in /etc/fstab to mount it, and you need to use the UUID, not the /dev/sdx confusion. So, you might write a line that looks like this:


        Code:
        UUID=82fffe8d-a8b1-49f7-afce-6ff01bc544bf   /mnt/MYRANDOMSTUFF    ext4    auto,users,rw,exec,noatime 0 2

        Comment


          #5
          Re: Hard drive information . . . but I don't entirely understand what I'm looking at

          Originally posted by Don
          Here's the output from oshunlvr's code:

          device fs_type label mount point UUID
          --------------------------------------------------------------------
          /dev/sda1 /
          /dev/sda5 /usr/local
          /dev/sda6 /home
          /dev/sdb1 /media/disk
          /dev/sdb5 (not mounted)
          /dev/sdb6 <swap>
          /dev/sdb7 (not mounted)

          So, am I right that the "missing" space is probably on (in?) sdb5 and sdb7, which I need to mount? If so, I think the syntax is "mount -t sbd5" but what should I specify as the directory?
          what @dibl sead and hears some more....

          that was with the USB drives unplugged right ?

          onley the drives listed in fstab will be mounted at boot ......all others SHOULD be accessible from dolphin's places panel .

          a comand line mount of a drive would be some thing like this.....first creating the DIR to mount to.

          Code:
          sudo mkdir /mnt/disk1 && sudo mount -t ext3 /dev/sdb5 /mnt/disk1
          sudo mkdir makes the DIR .....&& goes to the next command ........mount -t is type in this exampel we used ext3 if the partition is somthing elce use that.
          /dev/sdb5 is the partition to mount and /mnt/disk1 the DIR(place) we made to mount it to.
          i7 4core HT 8MB L3 2.9GHz
          16GB RAM
          Nvidia GTX 860M 4GB RAM 1152 cuda cores

          Comment


            #6
            Re: Hard drive information . . . but I don't entirely understand what I'm looking at

            The old /dev/sdx device numbering basically ran out of gas with the advent of USB hard drives. They don't connect directly to the hard drive controller, and they cannot be assumed to be present at boot time, when the hard drives are enumerated, so /dev/sdx does not work reliably with USB drives. That's why all modern Linux distributions have moved to default UUID drive identification.

            Comment


              #7
              Re: Hard drive information . . . but I don't entirely understand what I'm looking at

              Based on what I'm seeing, it appears that /dev/sdb1 was mounted automagically by dolphin when you clicked on it. That's why it's mounted in /media.

              How you should set things up really depends on how you want to access and/or use those other partitions. IMO, the hard drive partitions are easiest to access if they're mounted via fstab. The USB drives are usually best done by HAL/UDEV - which means just plug them in when you want them and let the system mount them by clicking on them via the Device Notifier in your Panel.

              Depending on the partitions you usually need only add users and noauto to your fstab options thus allowing you to mount them as a user (by clicking on them in dolphin for example), but not mounting them at boot time.

              Another tip is to label all your partitions. The drive labels can be used for fstab mounting if you wish and they will show up in Dolphin helping you keep track of what's what. You can label an unmounted partition in a terminal using e2label or almost any partition manager.

              Here's an example of an fstab entry using the label mounting and my preferred options;

              Code:
              /dev/disk/by-label/sdd5     /mnt/sdd5    reiserfs   defaults,noatime,nodiratime,notail,noauto,users  0    0



              Please Read Me

              Comment

              Working...
              X