Setting up Internal Drives?

Monte1022

New Member
Joined
Jun 24, 2020
Messages
26
Reaction score
0
Credits
245
Hello, everyone.

So I finally got around to buying the parts and built myself an Ubuntu machine, running 20.04.

I'm running a 500 GB SSD as my primary drive, and I have three other HDDs (a 3TB, a 6TB, and a 500GB).

I'm still fairly new to all the commands and such, but running fdisk -l gives me a list of what I think are partitions, that look something like this:

Disk /dev/loop0: 800.42 MiB, 839294976 bytes, 1639248 sectors

and there's something like 43 of these.

Ideally, what I would like is for my SSD to show as my "primary" drive (where the OS and apps are installed), and the other drives to appear as "whole" drives (i.e. the 6TB drive appears as 1 drive, not a bunch of partitions), or have all the HDDs (all 9.5TB of them) appear as one drive.

Is this possible? Right now, if I open the "file system" icon from the left menu, I don't see the other drives at all. I'm guessing I need to mount them.

How can I do these things? I'm really new to administering Linux, and I want to use these for storage drives for documents, code files, projects, etc.

Thanks for any advice!
 


hi @Monte1022 last time i used /dev/loop0 it was to mount an img file:

# losetup /dev/loop0 persistence.img

This is what i get using fdisk -l which i will do as root. you will use sudo fdisk -l

Code:
bash-5.0# fdisk -l
Disk /dev/sda: 58.25 GiB, 62537072640 bytes, 122142720 sectors
Disk model: BHT WR202I0064G 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 49BF35C8-4BAA-40F2-85E7-31A326085C5E

Device       Start       End   Sectors  Size Type
/dev/sda1     2048    206847    204800  100M EFI System
/dev/sda2   206848   6313983   6107136  2.9G Linux swap
/dev/sda3  6313984 122140671 115826688 55.2G Linux filesystem

i'm a novice really on everything but Slackware , even then i'm not an expert.
But 800 Mb doesn't make sense as any install .

Now generally its best to post stuff for us to look at , so we can see what we are looking at. You should be able to copy past from a terminal or if not pipe output to a text file such as :

bash-5.0# fdisk -l > info.txt
then if you find it has a padlock on it then,

sudo chmod 777 info.txt

SO first can you clarify you actually "installed" unbuntu to your HD ? my guess is if you did when you installed the other hd's were not attached ?

lets start maybe with fstab i'm sure others will chip in.

whats the output of cat /etc/fstab ? this is mine :

Code:
bash-5.0$ cat /etc/fstab
/dev/sda2        swap             swap        defaults         0   0
/dev/sda3        /                ext4        defaults         1   1
/dev/sda1        /boot/efi        vfat        defaults         1   0
#/dev/cdrom      /mnt/cdrom       auto        noauto,owner,ro,comment=x-gvfs-show 0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
tmpfs            /dev/shm         tmpfs       nosuid,nodev,noexec 0   0


generally internal hard drives get listed in fstab
 
Thanks for your response. Here is the result of fdisk -l

Disk /dev/loop0: 800.42 MiB, 839294976 bytes, 1639248 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 /dev/loop1: 800.47 MiB, 839344128 bytes, 1639344 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 /dev/loop2: 179.4 MiB, 187740160 bytes, 366680 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 /dev/loop3: 54.98 MiB, 57626624 bytes, 112552 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 /dev/loop4: 55.33 MiB, 58007552 bytes, 113296 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 /dev/loop5: 255.58 MiB, 267980800 bytes, 523400 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 /dev/loop6: 49.8 MiB, 52203520 bytes, 101960 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 /dev/loop7: 30.27 MiB, 31735808 bytes, 61984 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 /dev/nvme0n1: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WDS500G2B0C-00PXH0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9C2E3AD9-8772-46C2-A840-2065EC2F2D6B

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 976771071 975720448 465.3G Linux filesystem


Disk /dev/sda: 5.47 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: TOSHIBA HDWR160
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdb: 2.75 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EZRX-00D
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xd6ad236e

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 4294967294 4294965247 2T 83 Linux


Disk /dev/sdc: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5000AAKX-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000e82d4

Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 970631167 970629120 462.9G 83 Linux
/dev/sdc2 970633214 976771071 6137858 2.9G 5 Extended
/dev/sdc5 970633216 976771071 6137856 2.9G 82 Linux swap / Solaris


Disk /dev/loop8: 29.9 MiB, 31334400 bytes, 61200 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 /dev/loop9: 91.56 MiB, 95993856 bytes, 187488 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 /dev/loop10: 146.48 MiB, 153587712 bytes, 299976 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 /dev/loop11: 146.46 MiB, 153567232 bytes, 299936 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 /dev/loop12: 67.58 MiB, 70844416 bytes, 138368 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 /dev/loop13: 97.6 MiB, 101777408 bytes, 198784 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 /dev/loop14: 290.45 MiB, 304545792 bytes, 594816 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 /dev/loop15: 210.12 MiB, 220319744 bytes, 430312 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 /dev/loop16: 62.9 MiB, 65105920 bytes, 127160 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 /dev/loop17: 217.92 MiB, 228478976 bytes, 446248 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 /dev/loop18: 173.76 MiB, 182177792 bytes, 355816 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 /dev/loop19: 161.42 MiB, 169254912 bytes, 330576 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 /dev/loop20: 138.38 MiB, 145096704 bytes, 283392 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 /dev/loop21: 233.49 MiB, 244822016 bytes, 478168 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 /dev/loop22: 4.1 MiB, 4206592 bytes, 8216 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 /dev/loop23: 215.4 MiB, 225480704 bytes, 440392 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 /dev/loop24: 231.4 MiB, 242626560 bytes, 473880 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 /dev/loop25: 9.61 MiB, 10063872 bytes, 19656 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 /dev/loop26: 91.4 MiB, 95825920 bytes, 187160 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 /dev/loop27: 21.1 MiB, 22032384 bytes, 43032 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 /dev/loop28: 9.4 MiB, 9478144 bytes, 18512 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 /dev/loop29: 116.89 MiB, 122544128 bytes, 239344 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 /dev/loop30: 144.1 MiB, 151097344 bytes, 295112 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 /dev/loop32: 147.3 MiB, 154451968 bytes, 301664 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 /dev/loop33: 239.10 MiB, 251637760 bytes, 491480 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 /dev/loop34: 125.87 MiB, 131960832 bytes, 257736 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 /dev/loop35: 140 KiB, 143360 bytes, 280 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 /dev/loop36: 114.85 MiB, 120410112 bytes, 235176 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 /dev/loop37: 1 MiB, 1048576 bytes, 2048 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 /dev/loop38: 290.59 MiB, 304689152 bytes, 595096 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 /dev/loop39: 111.58 MiB, 116989952 bytes, 228496 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 /dev/loop40: 43.16 MiB, 45248512 bytes, 88376 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 /dev/loop41: 7.37 MiB, 7716864 bytes, 15072 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 /dev/loop42: 162.89 MiB, 170778624 bytes, 333552 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 /dev/loop43: 7.37 MiB, 7716864 bytes, 15072 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

And this is what's in fstab

# /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/nvme0n1p2 during installation
UUID=49d31d33-edb3-4b6a-8417-c395c0b6adb7 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=7DAB-2D91 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
 
Another way to view your drives is to open g-parted and look at them that way.

If you don't have any operating systems installed on the other drives you'll probably only see the other drives but nothing listed in the menu.

In the screenshot you can see my nvme drive.
Look in the upper right hand corner of g-parted. There you can select which drive you want to view.

Screenshot from 2020-10-11 23-17-56.png
 
I don't know what the /dev/loop'x' devices are but these are the real disks:

Code:
Disk /dev/sda: 5.47 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: TOSHIBA HDWR160
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdb: 2.75 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EZRX-00D
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xd6ad236e

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 4294967294 4294965247 2T 83 Linux


Disk /dev/sdc: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5000AAKX-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000e82d4

You also have what looks like an NVME installed:

Code:
Disk /dev/nvme0n1: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WDS500G2B0C-00PXH0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9C2E3AD9-8772-46C2-A840-2065EC2F2D6B

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 976771071 975720448 465.3G Linux filesystem

From your gparted output we see that root or '/' is mounted on the NVME drive. This is where your operating system is installed. So dev/{sda/sdb/sdc} you'll need to:

  • make a mount point (see man mount)
  • setup the mount to occur automatically at startup
  • then make filesystems on each device as desired (man mkfs)
keith
 
Gparted is a great tool, but
Code:
lsblk -f
will usually give a better summary of your block devices.
Such as
Code:
john@john-Desktop:~$ lsblk -f
NAME   FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                     
├─sda1 vfat         FEDE-EAB1                             467.3M     2% /boot/efi
├─sda2 ext4         23826d99-a20c-4578-be01-bcfdb11e4a0e   21.6G    27% /
├─sda3 ext4         3f50c05b-b795-43fe-b0cb-93984f7eaf65  162.5G     0% /home/extra
└─sda4 swap         775ceb26-36e8-4d6c-9b45-e0a1ea0d208f                [SWAP]
sdb                                                                     
└─sdb1 ext4         97534121-229e-4d67-921f-fd05ed312100  247.1G    41% /home
 
Here's mine:

lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1
│ ext4 1.0 2495b76b-b0d5-4177-9507-f51a2acac787
└─sda2
swap 1 27af6dc6-5ef4-4275-95bd-ad4721d67ee9
sdb
├─sdb1
│ ext4 1.0 88cc8300-dd9c-47c5-b12a-39658d12b7ee
└─sdb2
swap 1 f156e1ff-df41-44c8-b6d3-85c18a0a001c
nvme0n1

└─nvme0n1p1
ext4 1.0 393dea1b-7e98-4cd1-8a92-58aadf42d3ed 199.3G 8% /

This is my gaming rig with 3 different drives.
Thanks jglen490.
 
It appears that your NVME drive is the only mounted device, and sdb and sdc have been formatted but never mounted. The sda disk has not been acted on. @Monte1022, do you recall what you tried to do during the install?
 
I'm sorry, everyone, for the lengthy delay in my reply here. My monitor for my Linux machine broke, and I've been wrapped up in work/family/life stuff. I'm still experiencing this issue. To address @jglen490, no I don't recall what I did, unfortunately.

How would I mount these drives? Two of the drives have data n them (the 500GB HDD and the 3TB HDD)

So as it stands now, I have almost 10TB of disc space that is inaccessible.
 
I only see /dev/sda from your fdisk -l above.

Are there other devices, when you run fdisk -l ?
 
Ok, I read further down, you have dev/sdb and /dev/sdc

Is anything on them you want to save? Is it OK to re-format?
 
I'm sorry, everyone, for the lengthy delay in my reply here. My monitor for my Linux machine broke, and I've been wrapped up in work/family/life stuff. I'm still experiencing this issue. To address @jglen490, no I don't recall what I did, unfortunately.

How would I mount these drives? Two of the drives have data n them (the 500GB HDD and the 3TB HDD)

So as it stands now, I have almost 10TB of disc space that is inaccessible.
While booted into Ubuntu you should be able to use your file manager to locate and mount the 500 GB and 3TB drive.
That way you can copy the data to your Ubuntu distro or copy it to some other device if you like.
 
Ok, let me go into a little more detail. Maybe this will help.

I have a SSD that I believe is 500GB. I'll have to double check. That's where Ubuntu is installed.

I have an additional 3TB disk and a 500GB disk that already have data on them that I want to preserve. The 6TB disk is a new one that has no "data" on it. All I want to do is mount these disks so that I can access them from the file manager.

From the tips above, I can SEE the disks when I use terminal commands, but I still can't seem to mount them or see any files on them.

What I'd really like to do is mount all three disks (not the SSD, just the other three HDDs) as ONE, but that's probably going to be too complicated.

And for some reason my disk utility (in activities) keeps crashing. Is there a "repair" command for it?
 
That's why I asked if you can format them. Sometimes they are unformatted.
Sometimes, some distro don't recognize all filesystem types.
For example not all Distro's will auto-mount FAT32 and NTFS drives.

If it was me, I would re-create the partition tables, and re-format them.
(Probably as XFS or EXT4). They might auto-mount after this.
If not, it's pretty easy to get the UUID and add them to the fstab.
 
Can we try this route? The 500GB HDD and 3TB HDD have worked on Linux before.

In a console as root. (sudo)
fdisk /dev/sdb
g (this will create a gpt partition)
w (this will write the partition to the disk)

These two commands will put you out of fdisk and back at the prompt.
fdisk /dev/sdb
n (this will create a new partition)
This will ask a few questions. Just press "Enter" to accept the defaults.
w (This will write the new partition to the disk).
q (This will "quit" fdisk).

Now you have a new parition called /dev/sdb1 on /dev/sdb
Now we need to format it.

mkfs.ext4 /dev/sdb1 (This will format the hard-drive).

To test if it will mount... run this command.
mount /dev/sdb1 /mnt
df -h
You should see your sdb drive here under /mnt.

Assuming that worked, let us make this a permanent mount.

(run the following as root)
mkdir /drive2 (You can name this whatever you want, (no spaces) )
This will create a directory.

blkid /dev/sdb1 (This will give you the UUID of the drive)
This command will give out similar to this...
/dev/sda1: PTUUID="2c29425d-791b-4ee0-98d0-49fadb926042" PTTYPE="gpt"

The part you care about is the UUID. Yours will be different (everyone is unique).
But copy this part.
UUID="2c29425d-791b-4ee0-98d0-49fadb926042"
That's the only part you need.

Now edit your /etc/fstab file.
Add this to the the bottom.

UUID=acbe8b8a-456d-4ba3-af75-b5e79368fd06 /drive2 ext4 defaults 0 0

Don't use the UUID I have as an example above. Use your UUID that you got from the blkid command.
Change /drive2 to whatever you named the mount directory above.

Now run...
mount /drive2 (or whatever you named it).

You should see /drive2 now. Even if you reboot, it should remain persistant.

Repeat for /dev/sdc Name the mount point differently. Perhaps something like /drive3.
 
Is that going to delete everything on the drives? I don't want to do that. I usually equate "format" with "erase"...
 
Is that going to delete everything on the drives? I don't want to do that. I usually equate "format" with "erase"...
Yes, it will erase everything. If you don't want to do that... we can try this.

mount /dev/sdb /mnt
 

Members online


Latest posts

Top