Linux mint Raid Help

[Gooliez]

Linux Help please ( first time using linux )

i am making a steam cache server using "Lancache" but stuck on raid issues

 

 

i have Linux Mint installed on 250gb drive

4 x 1TB drives

 

This part added as it may be relevant to issue ----

Quote

 

when i run GPARTED, it comes up with an error "Invalid argument during seek for read on /dev/sdd"

now this error ONLY came up when i have the 4 drives raided (raid 0)

so i thought maybe a faulty drive so i unraided them and ran Gparted again, the error doesnt show, the drives create partition etc all perfectly.

Raided them up again, Gparted, Error doesnt show. Weird, ok guess i fixed something

 

----

ok, so now that the error isnt showing up now

When Gparted is loaded, i click in the top right and it shows the Physical 5 drives listed PLUS a 1.64TB drive ( which i imagine is the raid ?) . i thought that if i had raided them, it would only show 2 drives. 1 x 250gb and 1 x 4TB ?

as you can see from the pics it automatically allocated 931.51gb to the partition ( i didnt adjust, this is straight after the raid setup)

what have a dum dum done that's making this not work properly

 

edit: so i can partition the 1.64gb drive into a 931gb drive, any larger and it says i "cant allocate outside the physical drive"
 

also added this info that a guy said on facebook, but he hasnt responded, so thought this will be helpful to you guys

if theres any more info you need, please give the commands to type, so that i can get the information to you quicker

 

thanks for your help
 

Quote

 

sudo lshw -class disk -class storage

*-raid

description: RAID bus controller

product: SB7x0/SB8x0/SB9x0 SATA Controller [RAID5 mode]

vendor: Advanced Micro Devices, Inc. [AMD/ATI]

physical id: 11

bus info: pci@0000:00:11.0

logical name: scsi0

logical name: scsi1

logical name: scsi2

logical name: scsi3

logical name: scsi4

logical name: scsi5

version: 40

width: 32 bits

clock: 66MHz

capabilities: raid bus_master cap_list emulated

configuration: driver=ahci latency=32

resources: irq:19 ioport:ff00(size=8) ioport:fe00(size=4) ioport:fd00(size=8) ioport:fc00(size=4) ioport:fb00(size=16) memory:fdfff000-fdfff3ff

*-disk:0

description: ATA Disk

product: ST3250410AS

physical id: 0

bus info: scsi@0:0.0.0

logical name: /dev/sda

version: A

serial: 6RYFRNEB

size: 232GiB (250GB)

capabilities: partitioned partitioned:dos

configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=f168a2aa

*-disk:1

description: ATA Disk

product: GB1000EAFJL

physical id: 1

bus info: scsi@1:0.0.0

logical name: /dev/sdb

version: HPGC

serial: 9QJ2TM5E

size: 931GiB (1TB)

capabilities: partitioned partitioned:dos

configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=e634d0eb

*-disk:2

description: ATA Disk

product: GB1000EAFJL

physical id: 2

bus info: scsi@2:0.0.0

logical name: /dev/sdc

version: HPGC

serial: 9QJ2Q4V4

size: 931GiB (1TB)

capabilities: partitioned partitioned:dos

configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=e320208f

*-disk:3

description: ATA Disk

product: GB1000EAFJL

physical id: 3

bus info: scsi@3:0.0.0

logical name: /dev/sdd

version: HPGC

serial: 9QJ2THRL

size: 931GiB (1TB)

capabilities: partitioned partitioned:dos

configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=105c374b

*-disk:4

description: ATA Disk

product: GB1000EAFJL

physical id: 4

bus info: scsi@4:0.0.0

logical name: /dev/sde

version: HPGC

serial: 9QJ2TJ0A

size: 931GiB (1TB)

configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512

*-cdrom

description: DVD-RAM writer

product: DVD-RW DVR-216

vendor: PIONEER

physical id: 5

bus info: scsi@5:0.0.0

logical name: /dev/cdrom

logical name: /dev/cdrw

logical name: /dev/dvd

logical name: /dev/dvdrw

logical name: /dev/sr0

version: 1.03

capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram

configuration: ansiversion=5 status=nodisc

 

 

Quote

lan@Lan:~$ sudo hdparm -i /dev/sda

[sudo] password for lan:

/dev/sda:

Model=ST3250410AS, FwRev=4.AAA, SerialNo=6RYFRNEB

Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }

RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4

BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=off

CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=488395055

IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}

PIO modes: pio0 pio1 pio2 pio3 pio4

DMA modes: mdma0 mdma1 mdma2

UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6

AdvancedPM=no WriteCache=enabled

Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7

* signifies the current active mode

-------------------------------------------

lan@Lan:~$ sudo hdparm -i /dev/sdb

/dev/sdb:

Model=GB1000EAFJL, FwRev=HPGC, SerialNo=9QJ2TM5E

Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }

RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4

BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off

CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1953525168

IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}

PIO modes: pio0 pio1 pio2 pio3 pio4

DMA modes: mdma0 mdma1 mdma2

UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6

AdvancedPM=no WriteCache=enabled

Drive conforms to: unknown: ATA/ATAPI-4,5,6,7

* signifies the current active mode

-------------------------------------------

lan@Lan:~$ sudo hdparm -i /dev/sdc

/dev/sdc:

Model=GB1000EAFJL, FwRev=HPGC, SerialNo=9QJ2Q4V4

Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }

RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4

BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off

CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1953525168

IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}

PIO modes: pio0 pio1 pio2 pio3 pio4

DMA modes: mdma0 mdma1 mdma2

UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6

AdvancedPM=no WriteCache=enabled

Drive conforms to: unknown: ATA/ATAPI-4,5,6,7

* signifies the current active mode

-------------------------------------------

lan@Lan:~$ sudo hdparm -i /dev/sdd

/dev/sdd:

Model=GB1000EAFJL, FwRev=HPGC, SerialNo=9QJ2THRL

Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }

RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4

BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off

CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1953525168

IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}

PIO modes: pio0 pio1 pio2 pio3 pio4

DMA modes: mdma0 mdma1 mdma2

UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6

AdvancedPM=no WriteCache=enabled

Drive conforms to: unknown: ATA/ATAPI-4,5,6,7

* signifies the current active mode

-------------------------------------------

lan@Lan:~$ sudo hdparm -i /dev/sde

/dev/sde:

Model=GB1000EAFJL, FwRev=HPGC, SerialNo=9QJ2TJ0A

Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }

RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4

BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off

CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1953525168

IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}

PIO modes: pio0 pio1 pio2 pio3 pio4

DMA modes: mdma0 mdma1 mdma2

UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6

AdvancedPM=no WriteCache=enabled

Drive conforms to: unknown: ATA/ATAPI-4,5,6,7

 

 

 

 

[Jarsky]

If you want to see what actual drives are behind the /dev/mapper/pdc_ddajjhji then I recommend running the command

sudo lsblk

 

You might also try running using dmsetup, such as the below command:

sudo dmsetup -v table /dev/mapper/pdc_ddajjhji

This will tell you what sectors are allocated to which drive/partiion. Which you can match against the info from the previous lsblk command. 

 

 

IMO though, destroy the LD (Logical Disk) from your RAID configuration utility, and use the disks independently and just create a Linux MD Raid. 

Linux Mint I believe has the MDADM Utility by default: https://raid.wiki.kernel.org/index.php/A_guide_to_mdadm

[Electronics Wizardy]

don't use the raid on the motherboard, just turn it all off, using software raid on linux will be much better.

 

Id just fireup a mdadm raid array and your good here.

[Nick7]

Motherboard 'RAID' is actually semi-SW RAID known as fakeraid, so not actually proper HW raid.

To see that RAID field under Linux you need 'dmraid', and the RAID device will be under '/dev/mapper/...'.

However, I would highly suggest you use either mdadm to create RAID field or just use ZFS which has other benefits too.

 

[Gooliez]

awesome info guys, i've been struggling with this bloody raid for a couple of days now.

so i've installed MDADM

ran this command

Quote

sudo mdadm --create --verbose /dev/md0 --level=0 --raid-devices 4 /dev/sdb /dev/sdc /dev/sdd /dev/sde

then ran Gparted to see, there is now a new drive called /dev/md0 (3.64TiB)
so that seems to have worked, however in the guide i read it said "it will take some time to do" 
so i did a check with this command and got the response.

Quote

lan@Lan:~/Desktop$ sudo cat /proc/mdstat

 

Personalities : [raid0]
md0 : active raid0 sde[3] sdd[2] sdc[1] sdb[0]
      3906521088 blocks super 1.2 512k chunks

says active raid... does this mean it's complete and the drive is ready to mount ?
by the time typed the second command was around 30 seconds. " take some time to do" seems like an hour or so to me ?

 

cheers

[Jarsky]

2 hours ago, Gooliez said:

then ran Gparted to see, there is now a new drive called /dev/md0 (3.64TiB)
so that seems to have worked, however in the guide i read it said "it will take some time to do" 

so i did a check with this command and got the response.

says active raid... does this mean it's complete and the drive is ready to mount ?
by the time typed the second command was around 30 seconds. " take some time to do" seems like an hour or so to me ?

 

cheers

 

Awesome work.

 

When MD is first setup it needs to go through an initialization like most other RAIDs. 

Because you setup a RAID 0 there is no intial resync as there is no parity/mirroring, which is why it finishes straight away. 

 

You should really consider if you want to have a RAID 0 though. 

I understand it's "just a cache" but if a drive fails/drops out, you lose the entire RAID, so your cache has to re-download everything. 

Typically a RAID5 is more your go to configuration for something like this, to avoid complete data loss. 

[Gooliez]

I did think about raid 5, however the information really isn't that important to me to be stored long time. 

 

This is a basic process to save time and data download 1 night every couple of months ( for a lan ).  My net sits at around 4mb speeds. So around 8 people download 150mb update each stresses my net to its limits

[Gooliez]

Ok, Next Issue.

After creating the RAID, i loaded up Gparted, the i've Allocated the Partition, formatted it to EXT4. it's now Named /dev/md127 (3.64TiB)

so it's there, but i cant mount it in Gparted, the mount section isnt highlighting, and cant be chosen.  therefore i cant see it in the Devices section as an additional hard drive. How do i get it to show up there ? as individual drives, it would allow me to mount them, not as this raid though

Have also removed the Partition then - Device - Create Partition Table, Table type as MSDOS, which goes fine, then when i Create new Partition, then confirm action says "An Error Occurred while applying the operations"
saved the error, this was at the bottom.
 

Create Primary Partition #1 (ext4, 3.64 TiB) on /dev/md127  00:00:00    ( ERROR )
	create empty partition  00:00:00    ( ERROR )      libparted messages    ( ERROR )      partition length of 7813040128 sectors exceeds the msdos-partition-table-imposed maximum of 4294967295

[Nick7]

Guess you want to always have this partition mounted.

 

Do all this through CLI:

# mkfs.ext4 /dev/md127

# blkid

 

.. this command will type some stuff, look for line with '/dev/md127', and example how it could look like

/dev/md127: UUID="a424956c-a7af-42ed-826d-7869693436a6" TYPE="ext4" PARTUUID="9ed18be0-05"

 

Note the 'UUID' part.

 

Edit /etc/fstab file, and add following line (change UUID according to what you get):

UUID=a424956c-a7af-42ed-826d-7869693436a6 /mnt               ext4   defaults    0   1

 

Also change '/mnt' to where you want to mount it. Make sure that directory exists.

 

Try with running OS to mount it:

# mount -a

 

Now it'll auto-mount on each boot.

 

Keep in mind if you mess up /etc/fstab OS will halt boot and you will need to fix it in single user mode.

[Gooliez]

Thanks Nick, i really appreciate your help your giving.

 

managed to get it mounting on boot. after a LOT of diddling, clearly still learning how to get around linux
 

for anyone learning from this thread, i had to install "Gedit" to edit the fstab file. it wasnt saving it with normal edit for some reason..

 

Anyway. its now mounting, however dont have permissions, i've tried "ALT-F2" and "GKSUDO NEMO" that i found on a youtube video https://youtu.be/AeR8Rk5LwWU?t=801

however it's saying "failed to execute child process gksudo" even though on the video, he's using mint and he said nemo is the filemanager that mint is using.
i've googled and googled, but cant seem to find what i'm looking for to edit the file he's talking about. I downloaded the absolute latest mint "Ulyana Cinnamon 64" if that helps 

 

 

EDIT: so apparately they've taken out the GK part of the command, however i type "sudo nemo" and its like the command goes through, but no password request comes up or file manager shows

EDIT 2: if i type just NEMO, it loads up the file manager (just not in elevated)

[Jarsky]

1 hour ago, Gooliez said:

Thanks Nick, i really appreciate your help your giving.

 

managed to get it mounting on boot. after a LOT of diddling, clearly still learning how to get around linux

Some of what you may experience is particular to Linux Mint and the desktop environment you're using which makes things a bit more specific when working in the UI. 

 

1 hour ago, Gooliez said:

Anyway. its now mounting, however dont have permissions, i've tried "ALT-F2" and "GKSUDO NEMO" that i found on a youtube video https://youtu.be/AeR8Rk5LwWU?t=801

however it's saying "failed to execute child process gksudo" even though on the video, he's using mint and he said nemo is the filemanager that mint is using.
i've googled and googled, but cant seem to find what i'm looking for to edit the file he's talking about. I downloaded the absolute latest mint "Ulyana Cinnamon 64" if that helps 

 

 

EDIT: so apparately they've taken out the GK part of the command, however i type "sudo nemo" and its like the command goes through, but no password request comes up or file manager shows

 

since there's no gksudo it seem they've removed GTK+ . I'm not familiar with Linux Mint, but it seems the command should be

nemo admin://

 

It sounds like you just have a permission issue though, so honestly I would just edit it through terminal. You can simply open terminal and run

sudo chmod 777 -R /mnt

where /mnt is the path that you mounted it using fstab. That will give access to the volume for all users on the system. 

 

 

[Gooliez]

that's probably why i'm having so many issues, i had ubuntu 18.04 installed before hand, but was having issues, so the guy in the video was using mint, so i gave that a go. (so i could follow commands exactly) however the commands and being able to adjust the permissions worked perfectly in ubuntu.

 

so the nemo admin:// command went through, it took me to ///admin, but still doesnt  give me an option to adjust the drive permissions

 

so iwent down the command path.

i just want to confirm something here, as i feel as if i've done it wrong

 

so with my FSTAB file, i've added the UUID, changed the mount point to  /mnt/cache ( as shown below )

however when i click properties on the mounted drive it says my location is /MEDIA/LAN/

(name of the computer is lan btw)
shouldnt that location be /Cache ?

 

anyway. The "Cache" folder is showing up on the desktop AND in the file manager, so i've clearly mounted it properly

but ran "sudo chmod 777 -R /mnt/cache"  which didnt ask for a password ?  went through. still no access.

 

seeing as both didnt work. in your opinion, would i be best to just go back through all this again using Ubuntu ?

 

once again, really appreciate the help guys, i'm sure it's frustrating for such simple commands, but linux has just thrown me.

 

Quote

# /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/sda5 during installation
UUID=62173280-b5d2-4e7f-8412-85941add9b94 /               ext4    errors=remount-ro 0       1
UUID=7065dcc1-e4b6-4b24-821b-9385052b1327 /mnt/cache             ext4   defaults    0   1
# /boot/efi was on /dev/sda1 during installation
UUID=02F3-B1A7  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0

 

[Jarsky]

1 hour ago, Gooliez said:

so with my FSTAB file, i've added the UUID, changed the mount point to  /mnt/cache ( as shown below )

however when i click properties on the mounted drive it says my location is /MEDIA/LAN/

(name of the computer is lan btw)
shouldnt that location be /Cache ?

 

anyway. The "Cache" folder is showing up on the desktop AND in the file manager, so i've clearly mounted it properly

but ran "sudo chmod 777 -R /mnt/cache"  which didnt ask for a password ?  went through. still no access.

 

That's really odd, because /media is the mount point for removable media, so should only apply to things like external HDD's and USB keys, not to fixed disk / raid. 

Have you tried rebooting or running sudo umount -a && sudo mount -a to remount the share? 

 

Can you run ls -la /mnt/cache and post the output?

Can you also try putting a file in that folder (e.g touch /mnt/cache/test.txt) and then see if it shows in your "cache" folder 

[Gooliez]

yup, restarted tonnes of times

 

Quote

lan@Lan:~$ sudo umount -a
umount: /run/user/1000: target is busy.
umount: /sys/fs/cgroup/unified: target is busy.
umount: /sys/fs/cgroup: target is busy.
umount: /dev/shm: target is busy.
umount: /: target is busy.
umount: /run: target is busy.
umount: /dev: target is busy.

 

lan@Lan:~$ sudo mount -a
mount: /mnt/cache: can't find UUID=7065dcc1-e4b6-4b24-821b-9385052b1327.
lan@Lan:~$

lan@Lan:~$ ls -la /mnt/cache
total 8
drwxrwxrwx 2 root root 4096 Oct 21 13:21 .
drwxr-xr-x 3 root root 4096 Oct 21 13:21 ..
lan@Lan:~$

 

 

[Gooliez]

So..... i just right clicked on the desktop, there was a "Open as root"  option. i clicked it, as was able to swap and adjust the permissions on the "Cache" drive.

 

also, when i run gparted i get this

 

Quote

lan@Lan:~/Desktop$ gparted
Unit boot.mount does not exist, proceeding anyway.
Unit tmp.mount does not exist, proceeding anyway.
GParted 1.0.0
configuration --enable-libparted-dmraid --enable-online-resize
libparted 3.3

 

[Jarsky]

2 minutes ago, Gooliez said:

So..... i just right clicked on the desktop, there was a "Open as root"  option. i clicked it, as was able to swap and adjust the permissions on the "Cache" drive.

Well thats positive, so at least it's working. 

5 minutes ago, Gooliez said:

lan@Lan:~$ sudo mount -a
mount: /mnt/cache: can't find UUID=7065dcc1-e4b6-4b24-821b-9385052b1327

This is your issue here. Even though you created /mnt/cache; that UUID is invalid, which means its not mounted to that mount point, hence why changing permissions there had no effect on your raid. 

 

You should edit your /etc/fstab and remove the entry you made in there for /mnt/cache. 

 

If you want further help on this we'll need the outputs for the below to give you accurate instructions

sudo blkid -c /dev/null -o list
cat /etc/fstab

Otherwise if you're happy with it working as is then I recommend marking Nick7's answer 

 

[Gooliez]

yeah i'll need more help please, pretty sure i only have 4 hairs left on my head since working on this.. lol

 

if it was the incorrect one, how is it able to mount "Nothing" then, i've tried all the others and still doesnt work

 

Quote

lan@Lan:~/Desktop$ sudo blkid -c /dev/null -o list
device     fs_type label    mount point    UUID
-------------------------------------------------------------------------------
/dev/sda   linux_raid_member Lan:0 (in use) 83b5a6a6-47b8-6e2a-6be4-cda5b91d4eaf
/dev/sdb1  vfat             /boot/efi      02F3-B1A7
/dev/sdb5  ext4             /              62173280-b5d2-4e7f-8412-85941add9b94
/dev/sde   linux_raid_member Lan:0 (in use) 83b5a6a6-47b8-6e2a-6be4-cda5b91d4eaf
/dev/sdc   linux_raid_member Lan:0 (in use) 83b5a6a6-47b8-6e2a-6be4-cda5b91d4eaf
/dev/sdd   linux_raid_member Lan:0 (in use) 83b5a6a6-47b8-6e2a-6be4-cda5b91d4eaf
/dev/md0p1 ext4    cache    (not mounted)  e2b3039e-d1e6-4bf9-b179-e26157403205
lan@Lan:~/Desktop$ cat /etc/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/sda5 during installation
UUID=62173280-b5d2-4e7f-8412-85941add9b94 /               ext4    errors=remount-ro 0       1
UUID=7065dcc1-e4b6-4b24-821b-9385052b1327 /mnt/cache             ext4   defaults    0   1
# /boot/efi was on /dev/sda1 during installation
UUID=02F3-B1A7  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
lan@Lan:~/Desktop$

 

[Gooliez]

so when i remove the UUID string from FSTAB then mounting the drive it keeps automatically allocating it to  /media/lan/cache

it shows up in the "Devices" section of the file manager

 

Taken from sudo blkid -c /dev/null -o list

/dev/md0p1                        ext4         cache         /media/lan/cache                      e2b3039e-d1e6-4bf9-b179-e26157403205

 

in Gparted, the raid drive reffers to /dev/md0p1

if i add that UUID to fstab like nick7 listed, ( after unmounting and mounting ) the device doesnt show up any more in the devices section

 

how do i mount it so it will STAY in the devices section ( if it's meant to be there),  putting anything in the mount position removes it from the devices list

[Jarsky]

so this is your actual raid:

/dev/md0p1 ext4    cache    (not mounted)  e2b3039e-d1e6-4bf9-b179-e26157403205

 

so your FSTAB entry should look like this:

 

UUID=e2b3039e-d1e6-4bf9-b179-e26157403205 /mnt/cache             ext4   defaults    0   2

 

then once you've done that run sudo mount -a 

[Gooliez]

ok, so without string and the drive showing up in the DEVICES section, i created a Text File. Abcdefg.txt

 

I copied and pasted your string, placed in fstab, mounted, rebooted.

CACHE isnt showing up in a Devices section like it was previously ? is that correct ?  ( picture shown, labelled Screenshot )

i then went to the filesystem/mgt/cache and the abcdefg.txt file is in there.  is that correct ?

 

 

3rd picture labelled 2.png, was after i removed the string you wrote, it's showing up as "Cache" in the Devices section again, the abcdefg file is there also.

fstab is how i've placed the string you've listed me

Quote

 

# /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/sda5 during installation
UUID=62173280-b5d2-4e7f-8412-85941add9b94 /               ext4    errors=remount-ro 0       1

UUID=e2b3039e-d1e6-4bf9-b179-e26157403205 /mnt/cache             ext4   defaults    0   2
# /boot/efi was on /dev/sda1 during installation
UUID=02F3-B1A7  /boot/efi       vfat    umask=0077      0       1
/swapfile    

 

 

 

[Jarsky]

25 minutes ago, Gooliez said:

ok, so without string and the drive showing up in the DEVICES section, i created a Text File. Abcdefg.txt

 

I copied and pasted your string, placed in fstab, mounted, rebooted.

CACHE isnt showing up in a Devices section like it was previously ? is that correct ?  ( picture shown, labelled Screenshot )

i then went to the filesystem/mgt/cache and the abcdefg.txt file is in there.  is that correct ?

 

3rd picture labelled 2.png, was after i removed the string you wrote, it's showing up as "Cache" in the Devices section again, the abcdefg file is there also.

fstab is how i've placed the string you've listed me

 

Yup that is correct behavior, because "Devices" is your temporary storage (e.g usb key, external hard drive, optical drive, etc...) which is mounted under /media

Also if you type df -h, you should now see your 3.7TB mount for /mnt/cache.

 

If you want a shortcut, you should be able to navigate to /mnt and right click on the cache folder and 'Send to...' to create a shortcut.

 

 

[Gooliez]

yup its listed.

 Thankyou so much for all your help, it's really a steep learning curve when you've had nothing to do with linux at all.