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

[oshunluvr]

I made a typo in that command - I posted that above, Try this:

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

[kdeuser]

Readout of sudo fsck.jfs -a -v /dev/sdc1 below :

reel@ReelBox:~$ sudo fsck.jfs -a -v /dev/sdc1
[sudo] password for reel: 
fsck.jfs version 1.1.15, 04-Mar-2011
processing started: 1/7/2015 0:00:58
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/7/2015 0:01:34  with return code: -10015  exit code: 8.
reel@ReelBox:~$

Still getting the fatal error.

[oshunluvr]

Try:

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


If you get no errors, then do:

ls /mnt/sdc1

[kdeuser]

No errors which is good and the print below.

reel@ReelBox:~$ sudo mount -vsf -t jfs -o ro,nointegrity,errors=remount-ro /dev/sdc1 /mnt/sdc1
[sudo] password for reel: 
/dev/sdc1 on /mnt/sdc1 type jfs (ro,nointegrity,errors=remount-ro)
reel@ReelBox:~$ ls /mnt/sdc1
reel@ReelBox:~$

Can a miracle have just happened here.

[oshunluvr]

Doesn't look like anything is there. If it was readable, you would have had output from ls.

If your files were valuable, I've had luck with UFS Explorer to recover files from damaged filesystems. You can download it for free and test to see if it can read your files, but to do any real recovery you have to buy it.

Once you done whatever it is you want to try and do to recover - you should test the disc to see if the drive is still OK. Just because your filesystem got messed up doesn't not necessarily mean the drive is bad. Assuming the drive checks out, it's time for a reformat and start over.

[oshunluvr]

Wait = try this:

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

then this again;

ls /mnt/sdc1

[kdeuser]

There seems to be a breath of life , small but it´s there.

reel@ReelBox:~$ sudo mount -vs -t jfs -o ro,nointegrity,errors=remount-ro /dev/sdc1 /mnt/sdc1
[sudo] password for reel: 
/dev/sdc1 on /mnt/sdc1 type jfs (ro,nointegrity,errors=remount-ro)
reel@ReelBox:~$ ls /mnt/sdc1
music  opt  pictures  recordings  video
reel@ReelBox:~$

[kdeuser]

I can´t believe it , your a wizard.

Might be premature but the drive has fired up and i can see files.

Update : I can confirm the drive is alive and firing on all cylinders.

Was the solution just to run :

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

ls /mnt/sdc1

Print of fstab below :



Could this drive be made into read/write ? or is this too much to ask.

One last thing and this is puzzling me , still can´t write to Kate text file.

[oshunluvr]

I doubt it will mount read-write and I wouldn't trust it at this point. I would copy everything off that you can and re-format (and check the drive itself). Likely a few files are damaged but hopefully, most will work. When you copy them off, usually damaged files will have a zero size.

[oshunluvr]

Re. Kate start a new thread. I doubt that's a related issue.

[kdeuser]

@oshunluvr, my gratitude to you sir, a late Christmas present.

Thanks again.

[kdeuser]

I may have been over enthusiastic but this morning on switching on the pc all drives refused to load.

This is usually not a problem as i go to the mediacenter part and via remote control mount the drives. Of course the drive in quesstion doesn´t mount - it should and was.

Back to the pc part and in terminal enter those magic commands and says already mounted.

Ok, i´ll cut to the chase here ; question - have to enter :

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

Everytime for the drive to mount and on entering :

ls /mnt/sdc1

It cancels the former out, so i just omit the latter and bingo - but :

Is there / would there be a way of making this mount permenant , or is this a temporary fix until a new drive appears ?

Thanks .

[kdeuser]

@oshunluvr, may have been over enthusiastic but this morning on switching on the pc all drives refused to load.

This is usually not a problem as i go to the mediacenter part and via remote control mount the drives. Of course the drive in quesstion doesn´t mount - it should and was.

Back to the pc part and in terminal enter those magic commands and says already mounted.

Ok, i´ll cut to the chase here ; question - have to enter :

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

Everytime for the drive to mount and on entering :

ls /mnt/sdc1

It cancels the former out, so i just omit the latter and bingo - but :

Is there / would there be a way of making this mount permenant , or is this a temporary fix until a new drive appears ?

Thanks .

[kdeuser]

My apologies on the double post .

[oshunluvr]

To make the mounting permanent, edit /etc/fstab and enter:

/dev/sdc1 /mnt/sdc1 jfs ro,nointegrity,errors=remount-ro 0 0

but if a simple "ls" is causing it to unmount you're not going to be able to do much. Is there anything in dmesg output regarding the drive?