Announcement

Collapse
No announcement yet.

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

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #46
    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

    Please Read Me

    Comment


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

      Code:
      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 :

      Code:
      sudo mount -vsf -t jfs -o ro,nointegrity,errors=remount-ro /dev/sdc1 /mnt/sdc1
      Code:
      sudo fsck.jfs -v -f /dev/sdc1
      Code:
      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 :

      Code:
      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 .
      Last edited by kdeuser; Jan 05, 2015, 04:06 AM.

      Comment


        #48
        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.

        Please Read Me

        Comment


          #49
          Originally posted by oshunluvr View Post
          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.

          Comment


            #50
            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?

            Please Read Me

            Comment


              #51
              BTW, to fix the hosts error (your keyboard doesn't work in Kate) , try this:

              awk 'NR==2{$0="localhost 127.0.1.1 ReelBox\n"$0}1' /etc/hosts > newhosts

              I'd copy and paste into the terminal window to avoid typos. This should make you a new hosts file at the present location called newhosts that has the 127.0.1.1 line in it. Simply do cat newhosts to see if it worked correctly and you should see this:

              Code:
              127.0.0.1 localhost
              127.0.1.1 ReelBox
              
              
              # 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
              Assuming you do and it looks correct, then do this:

              sudo mv /etc/hosts /etc/hosts.old; sudo mv newhosts /etc/hosts

              and you should now have the old file as /etc/hosts.old (just in case) and a new correct /etc/hosts file.

              You should n't have to reboot - it should take effect immediately.

              Please Read Me

              Comment


                #52
                Hi oshunluvr, still unable to write to hosts file :

                awk 'NR==2{$0="localhost 127.0.1.1 ReelBox\n"$0}1' /etc/hosts > newhosts

                This worked , as is and Reelbox is in hosts.

                What didn´t work was :

                sudo mv /etc/hosts /etc/hosts.old; sudo mv newhosts /etc/hosts , the readout below :

                Code:
                reel@ReelBox:~$ sudo mv /etc/hosts /etc/hosts.old; sudo mv newhosts /etc/hosts
                sudo: unable to resolve host ReelBox
                [sudo] password for reel: 
                sudo: unable to resolve host ReelBox
                reel@ReelBox:~$
                I remember before a post ( and unable for the life of me to locate ) that this particular command produced very little data loss.

                The fix was immediate and remember in console saying ,"corrected successfully ", or something on those lines.

                PS : yes , i would prefer to save the files on disk but damn i executed this command and it made the sectors fine again - reloaded a fresh os install and the drive was back in business.
                Last edited by kdeuser; Jan 06, 2015, 12:26 PM.

                Comment


                  #53
                  I don't see any errors regarding the file move in the code you posted - just the host error. Check the contents of /etc/hosts to see if it changed.

                  The difference with your fsck command and mine is ( -a vs. -v -f ) is the -a option means automatic repair if errors are found. The -f option means run the repair service even if not errors are reported (scans the whole filesystem). Either one is fine; -a will be quicker, -f will be more thorough. The -v option just mean "verbose" and prints out more details while run. In either case, don't try and run fsck.jfs with the filesystem mounted.

                  In case anyone cares; in my opinion JFS is rather outdated and ext4 or btrfs are better choices for a modern linux machine. JFS is reliable but journal writes are held for a trigger rather than on a timer, which means an unplanned interrupt (crash, power off, hard reset, etc.) can cause this sort of journal corruption. JFS is known for good and even performance over various operations, but these days a well-tuned ext4 or btrfs filesystem will outdo JFS and be less prone to errors.

                  Please Read Me

                  Comment


                    #54
                    Just checked etc/hosts and it´s not there or i can´t find it.

                    Mant host files i.e. host.conf, hostname , hosts.allow ,hosts.deny , hosts.old but no plain hosts.

                    Comment


                      #55
                      Does newhosts still exist?

                      Please Read Me

                      Comment


                        #56
                        Can´t see newhosts , just the ones i mentioned in my last post.

                        Comment


                          #57
                          It would be in the directory you ran the command from, not in /etc. Try running nano from the terminal and creating a new one:

                          sudo nano /etc/hosts

                          Then paste this into it:

                          Code:
                          127.0.0.1 localhost
                          127.0.1.1 ReelBox
                          
                          # 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
                          then CTRL-X to save and exit.

                          Please Read Me

                          Comment


                            #58
                            I can now see ´hosts´ , and the new code - seems fine.

                            Thanks.

                            Just a damn shame this drive doesn´t mount.

                            Comment


                              #59
                              Did you try to read it after mounting read-only?

                              What about fsck.jfs?

                              Please Read Me

                              Comment


                                #60
                                Tried mounting the drive but errors are constant . I ran a few commands , you can see below :

                                Code:
                                reel@ReelBox:~$ sudo blkid -c /dev/null -o list |grep sdc1 
                                [sudo] password for reel: 
                                /dev/sdc1  jfs     Reel Media Drive (not mounted) 41c3909e-78ab-4bf7-b2dc-5d541a6aa8b9
                                reel@ReelBox:~$ sudo fsck.jfs -n dev.sdc1
                                fsck.jfs version 1.1.15, 04-Mar-2011
                                processing started: 1/6/2015 23:01:16
                                
                                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:~$ sudo fsck.jfs -n /dev/sdc1 
                                fsck.jfs version 1.1.15, 04-Mar-2011
                                processing started: 1/6/2015 23:02:13
                                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:~$ sudo fsck.jfs -a dev.sdc1                                    
                                fsck.jfs version 1.1.15, 04-Mar-2011                                         
                                processing started: 1/6/2015 23:03:23                                        
                                                                                                             
                                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:~$ sudo mkdir /mnt/sdb /mnt/sdc /mnt/sdd
                                mkdir: cannot create directory `/mnt/sdb': File exists
                                mkdir: cannot create directory `/mnt/sdc': File exists
                                mkdir: cannot create directory `/mnt/sdd': File exists
                                reel@ReelBox:~$ sudo mount /dev/sdc /mnt/sdc
                                mount: you must specify the filesystem type
                                reel@ReelBox:~$ sudo mount -t jfs /dev/sdc /mnt/sdc
                                mount: wrong fs type, bad option, bad superblock on /dev/sdc,
                                       missing codepage or helper program, or other error
                                       In some cases useful info is found in syslog - try
                                       dmesg | tail  or so
                                
                                reel@ReelBox:~$
                                Probably have to buy another 3 tb drive , see what can be saved.

                                Comment

                                Users Viewing This Topic

                                Collapse

                                There are 0 users viewing this topic.

                                Working...