Problem with Hard Drive

What error do you get when youmanually try to mount the drives?

mount /drive_sda

mount /drive_sdb
 


What error do you get when youmanually try to mount the drives?

mount /drive_sda

mount /drive_sdb
edit:sorry forgot the first command

gmel@GBox:~$ mount /drive_sda
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.

gmel@GBox:~$ mount /drive_sdb
mount: /drive_sdb: must be superuser to use mount.
(base) gmel@GBox:~$ sudo mount /drive_sdb
[sudo] password for gmel:
mount: /drive_sdb: /dev/sdb1 already mounted on /drive_sdb.
(base) gmel@GBox:~$
 
If it's already mounted, how can both drives be missing?

cd /drive_sdb

ls
 
If it's already mounted, how can both drives be missing?

cd /drive_sdb

ls
gmel@GBox:~$ cd /drive_sda
(base) gmel@GBox:/drive_sda$ ls
'Bank 1' 'downloaded music' MikeMusic 'System Volume Information'
(base) gmel@GBox:/drive_sda$ cd ..
(base) gmel@GBox:/$ cd /drive_sdb
(base) gmel@GBox:/drive_sdb$ ls
'Latest Osmi' lost+found 'The Board Footage' Transfer
(base) gmel@GBox:/drive_sdb$ cd ..
(base) gmel@GBox:/$
 
this was fantastic
it looks like I didn't lose any of my data either

thank you

these drives don't show in my GUI
how do I fix that?
 
Does anyone have any idea how my drive names got removed/changed?

Someone earlier suggested a surge
and that may have caused it
 
Usually this is a permissions issue.

chown -R gmel:gmel /drive_sdb/*

should fix it.
looks like that took care of the last step

thank you for walking me through this

do you have a resource you recommend where I can learn more terminal prompts?
 
Does anyone have any idea how my drive names got removed/changed?

Someone earlier suggested a surge
and that may have caused it
Device names like /dev/sda and /dev/sdb are assigned at boot time. These can change if a race condition exists. One device may respond faster than another device, but sometimes the second device might respond first. This is why it's a good idea to use UUIDs for each device when referring to a block device. A UUID is a Universally Unique IDentifier. Each UUID on your system must be unique or your kernel can get confused and then bad things can happen.

Signed,

Matthew Campbell
 


Members online


Latest posts

Top