Drive has no mount point and other drives are read only.

[oshunluvr]

You can't mount a drive, you have to mount the filesystem. In this case, your filesystem is on sdc1 not sdc.

Try mounting /dev/sdc1 instead.

[kdeuser]

Tried that new format but the drive´s not mounting.

[SteveRiley]

You're missing a space in the command. You typed

sudo mount -t jfs /dev/sdc1/mnt/sdc1

when it should be

sudo mount -t jfs /dev/sdc1 /mnt/sdc1

Also, the directory sdc1 needs to already exist in /mnt. You can't mount a file system to a nonexistent directory.

[kdeuser]

Thanks a small error there but still not mounting :



Drives sdb and sda are fine it´s only sdc which does not want to mount.

Just refuses to make a mount point ?

[oshunluvr]

No it's not "refusing" to make a mount point, you've typed it wrong again.

This time you created (or had) a mount point - /mnt/sdc - and then attempted to mount to - /mnt/sdc1 - which doesn't exist because that's not the mount point you created.

Either create the mount point as /mnt/sdc1 as Steve said in his last post, or use one that already exists - /mnt/sdc. For some reason, you've assumed the mount point label (folder name) must match the partition label. The system does not care what you mount or where you mount it, but it can't mount devices that don't have filesystems (/dev/sdc) or mount to locations that don't exist (/mnt/sdc1).

Your computer isn't going to read your mind or guess at what you want. It's going to do (or try to do) EXACTLY what you type. Therefore you must type EXACTLY what you want it to do.

As Steve and I have said; Use /dev/sdc1 as the mounting device because /dev/sdc does not have a filesystem on it and either create /mnt/sdc1 or use /mnt/sdc - doesn't matter which. Either of these commands should work;

sudo mount -t jfs /dev/sdc1 /mnt/sdc

or

sudo mkdir /mnt/sdc1; sudo mount -t jfs /dev/sdc1 /mnt/sdc1

[kdeuser]

Typed in those commands and it´s still not mounting.



Thank you for helping on this.

[Snowhog]

i think you have a different issue going on here.

Show us your /etc/hostname and /etc/hosts files. You don't need to make screen shots as you've been doing. Just highlight the output and copy it with Ctrl+Shift+c. In your reply, click the # button (in the Quick Reply window you are typing in). Put your cursor between the ][ and right-click your mouse and select Paste.

Something isn't right in one of those two files, as indicated by the error you keep getting:

sudo: unable to resolve host ReelBox

[kdeuser]

Output of - etc/hostname :

ReelBox

Output of - etc/hosts :

127.0.0.1 localhost

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

192.168.99.129 hdext

Thanks .

[Snowhog]

Edit your /etc/hosts file (as root). Press Alt+F2. Type: kdesudo kate /etc/hosts and press enter. Enter your password and press enter. When the file is open, add the following line below the first line:

127.0.1.1 RealBox

Make sure there is a space between the 1 and RealBox.

Save and close the file. Close your apps and log out/reboot. Once back on your desktop, open a console and lets see what you already have in the /mnt directory.

[oshunluvr]

Although the hostname thing needs to be fixed - AFAIK, hostname resolution has nothing to do with mounting via fstab.

What's the output of

sudo blkid -c /dev/null -o list |grep sdc1

If the partition has a jfs filesystem on it, it's likely to be unclean due to a bad un-mount.

[kdeuser]

@Snowhog, etc/hosts/ will not allow me to type in the file, keyboard has no function.

@oshunluvr , the output of - sudo blkid -c /dev/null -o list |grep sdc1 :

reel@ReelBox:~$ sudo blkid -c /dev/null -o list |grep sdc1 
sudo: unable to resolve host ReelBox
[sudo] password for reel: 
/dev/sdc1  jfs     Reel Media Drive (not mounted) 41c3909e-78ab-4bf7-b2dc-5d541a6aa8b9
reel@ReelBox:~$

[oshunluvr]

OK, whats the output of:

sudo fsck.jfs -n dev.sdc1

[kdeuser]

Output of - sudo fsck.jfs -n dev.sdc1 :

reel@ReelBox:~$ sudo fsck.jfs -n dev.sdc1
sudo: unable to resolve host ReelBox
[sudo] password for reel: 
fsck.jfs version 1.1.15, 04-Mar-2011
processing started: 1/5/2015 0:46:39

Error: Cannot open device dev.sdc1

Usage:  fsck.jfs [-afnpvV] [-j journal_device] [--omit_journal_replay] [--replay_journal_only] device

Emergency help:
 -a                 Automatic repair.
 -f                 Force check even if file system is marked clean.
 -j journal_device  Specify external journal device.
 -n                 Check read only, make no changes to the file system.
 -p                 Automatic repair.
 -v                 Be verbose.
 -V                 Print version information only.
 --omit_journal_replay    Omit transaction log replay.
 --replay_journal_only    Only replay the transaction log.
reel@ReelBox:~$

[oshunluvr]

Sorry - my fault - typo:

sudo fsck.jfs -n /dev/sdc1

[kdeuser]

Output from - sudo fsck.jfs -n /dev/sdc1 :

reel@ReelBox:~$ sudo fsck.jfs -n /dev/sdc1 
sudo: unable to resolve host ReelBox
[sudo] password for reel: 
fsck.jfs version 1.1.15, 04-Mar-2011
processing started: 1/5/2015 1:22:23
The current device is:  /dev/sdc1
Block size in bytes:  4096
Filesystem size in blocks:  732566637
**Phase 1 - Check Blocks, Files/Directories, and  Directory Entries
ujfs_rw_diskblocks: read 0 of 16384 bytes at offset 450640166912
Unrecoverable error reading M from /dev/sdc1.  CANNOT CONTINUE.
reel@ReelBox:~$