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

[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:~$

[oshunluvr]

As you might suspect, that's not good. At this point, you're likely to lose some or all your data as you proceed. If you want to try and save anything, try mounting it read only to see if you can at least copy some stuff off of it.

sudo mount -vsf -t jfs -o ro,nointegrity,errors=remount-ro /dev/sdc1 /mnt/sdc1

I assume you've updated your system so you have the latest version of jfsutils. You should probably run fsck with repairs ( -n just tests ).

sudo fsck.jfs -v -f /dev/sdc1

[kdeuser]

According to the table in post #43 could the drive be auto repaired with :

sudo fsck.jfs [B]-a[/B] dev.sdc1

Have n´t tried the above yet , waiting to see if this can be done.

The readings from :

sudo mount -vsf -t jfs -o ro,nointegrity,errors=remount-ro /dev/sdc1 /mnt/sdc1

sudo fsck.jfs -v -f /dev/sdc1

reel@ReelBox:~$ sudo mount -vsf -t jfs -o ro,nointegrity,errors=remount-ro /dev/sdc1 /mnt/sdc1
sudo: unable to resolve host ReelBox
[sudo] password for reel: 
/dev/sdc1 on /mnt/sdc1 type jfs (ro,nointegrity,errors=remount-ro)
reel@ReelBox:~$ sudo fsck.jfs -v -f /dev/sdc1
sudo: unable to resolve host ReelBox
fsck.jfs version 1.1.15, 04-Mar-2011
processing started: 1/5/2015 9:14:46
The current device is:  /dev/sdc1
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
Primary superblock is valid.
The type of file system for the device is JFS.
Block size in bytes:  4096                                                   
Filesystem size in blocks:  732566637                                        
**Phase 0 - Replay Journal Log                                               
LOGREDO:  Log record for Sync Point at:    0x09223c4                         
LOGREDO:  Beginning to update the Inode Allocation Map.                      
LOGREDO:  Done updating the Inode Allocation Map.                            
LOGREDO:  Beginning to update the Block Map.                                 
ujfs_rw_diskblocks: read 0 of 4096 bytes at offset 12619776                  
LOGREDO:   Read Block Map data extents failed.                               
LOGREDO:  Write Block Map control page failed in UpdateMaps().               
LOGREDO:  Unable to update map(s).                                           
logredo failed (rc=-271).  fsck continuing.                                  
**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.              
Fatal error (-10015,30) accessing the filesystem (1,450640166912,16384,0).   
processing terminated:  1/5/2015 9:15:22  with return code: -10015  exit code: 8.                                                                         
reel@ReelBox:~$

I take it this drive is toast then, pending that repair command from post #43.

Just re-reading post #13 , says that :

Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      267350  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.
reel@ReelBox:~$

Could this be a game changer here .

[oshunluvr]

Well, you mounted it read-only it looks like, but then you ran the file check. You can't do that successfully.

If you want to read the partition and copy the files off of it - mount it, then copy.

If you want to attempt a fix - UNmount it, then run fsck.

The physical sector boundary error can be ignored.

[kdeuser]

Well, you mounted it read-only it looks like, but then you ran the file check. You can't do that successfully.

If you want to read the partition and copy the files off of it - mount it, then copy.

If you want to attempt a fix - UNmount it, then run fsck.

The physical sector boundary error can be ignored.

Last time there was a command and i can´t remember it and it solved the sector error which enabled the drive to mount.

With all these commands flying around i am abit lost, so forgive me if i don´t know what your saying here.

Would be better if you could write what you would wish me to execute i.e. as if i were a pc .

Sorry about this and thanks.

[oshunluvr]

The problem is I'm unsure which way you want to go:

Do you want to make a backup before proceeding?
Do you want to try and copy data off the drive or just try and repair it?