USB HDD ext4 changes to read-only - what is the problem? - works on other system Announcing...

Multi tool use
Multi tool use

How fail-safe is nr as stop bytes?

If Windows 7 doesn't support WSL, then what does Linux subsystem option mean?

How can I reduce the gap between left and right of cdot with a macro?

Can anything be seen from the center of the Boötes void? How dark would it be?

AppleTVs create a chatty alternate WiFi network

Project Euler #1 in C++

Dating a Former Employee

Why do we bend a book to keep it straight?

A term for a woman complaining about things/begging in a cute/childish way

What's the meaning of "fortified infraction restraint"?

How to play a character with a disability or mental disorder without being offensive?

How do living politicians protect their readily obtainable signatures from misuse?

Selecting user stories during sprint planning

Trademark violation for app?

What is the appropriate index architecture when forced to implement IsDeleted (soft deletes)?

How does light 'choose' between wave and particle behaviour?

What does it mean that physics no longer uses mechanical models to describe phenomena?

What do you call the main part of a joke?

What order were files/directories outputted in dir?

Converted a Scalar function to a TVF function for parallel execution-Still running in Serial mode

Is it fair for a professor to grade us on the possession of past papers?

How to write this math term? with cases it isn't working

Why is the AVR GCC compiler using a full `CALL` even though I have set the `-mshort-calls` flag?

Amount of permutations on an NxNxN Rubik's Cube



USB HDD ext4 changes to read-only - what is the problem? - works on other system



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionUnable to change permissions of file system rootMount USB on Read-Only filesystemUSB flash drive is read-only under Gnome on Debianfsck.ext4 can't repair block far behind end of the file systemDifferent mount output with and without initramfsEtcd executable gets permission denied as rootMount ext4 read-onlyRemounting read-only without changing other optionsUSB HDD automount problem in Debian Stretchmount ext4 disk: cannot mount /dev/sdc read-only





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















I have attached a Seagate external hard drive (FreeAgent 750GB) to Open Media Vault on raspberry pi. As soon as any write operation is attempted the drive is remounted read only. The machine is raspberryPi v.1 B+ (r0OMV 4.1.13+). I can however attach the same drive to my (manjaro 4.3.6-1-MANJARO) laptop and write to it without any problems.



Any thoughts are appreciated. Given that this is a disk that works OK on other systems I would not want to simply buy a new disk, because it might have the same problems with raspberryPi and OMV. I can repeat the below steps I have done and I get exact same results again. Just to say - this disk functioned OK for a week or so days on the same raspberryPi machine and still can function well with my laptop. The disk is 7 years old. My troubleshooting steps so far have been:



1) Unmount and do fsck:



root@r0OMV:~#  e2fsck /dev/sda1
e2fsck 1.42.5 (29-Jul-2012)
ForteBKP: recovering journal
ForteBKP contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
ForteBKP: 11/45793280 files (0.0% non-contiguous), 2924481/183143385 blocks


immediately after I can mount it:



mount -a


then mount shows:



/dev/sda1 on /media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)


if I try to mkdir I get error:



mkdir: cannot create directory `/media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c/touch': Read-only file system


and mount shows:



/dev/sda1 on /media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c type ext4 (ro,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)


as this happens syslog output is:



Mar  5 12:08:48 r0OMV kernel: [49725.089841] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
Mar 5 12:08:50 r0OMV kernel: [49727.055478] blk_update_request: critical target error, dev sda, sector 0
Mar 5 12:08:55 r0OMV kernel: [49732.679403] blk_update_request: critical target error, dev sda, sector 730073112
Mar 5 12:08:55 r0OMV kernel: [49732.679520] Aborting journal on device sda1-8.
Mar 5 12:08:56 r0OMV kernel: [49733.120506] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
Mar 5 12:08:56 r0OMV kernel: [49733.134090] EXT4-fs (sda1): Remounting filesystem read-only


2) Other steps taken:
I have looked into hdparm and smartctl



root@r0OMV:~# hdparm -I /dev/sda1
/dev/sda1:
ATA device, with non-removable media
Model Number: ST3750640AS
Serial Number: 5QD40Q51
Firmware Revision: 3.AFM
Standards:
Supported: 7 6 5 4
Likely used: 7
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
... the rest of output seems normal and I cut it for the sake of brevity

root@r0OMV:~# hdparm -r0 /dev/sda1
/dev/sda1:
setting readonly to 0 (off)
readonly = 0 (off)

root@r0OMV:~# hdparm -W /dev/sda1
/dev/sda1:
write-caching = 0 (off)


but this has produced no results.



With smartctl after long test I find that the result is



smartctl -H /dev/sda 
smartctl 5.41 2011-06-09 r3365 [armv6l-linux-4.1.13+] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Please note the following marginal Attributes:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
190 Airflow_Temperature_Cel 0x0022 051 034 045 Old_age Always In_the_past 49 (92 106 63 32)


The rest of the parameters are withing normal limits when I check with -a flag I see that the tests I have done recently seem OK.



SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Aborted by host 80% 15285 -
# 2 Extended offline Aborted by host 90% 15285 -
# 3 Extended offline Aborted by host 80% 15285 -
# 4 Short offline Completed without error 00% 15285 -
# 5 Extended offline Aborted by host 70% 15276 -
# 6 Extended offline Completed without error 00% 15157









share|improve this question































    1















    I have attached a Seagate external hard drive (FreeAgent 750GB) to Open Media Vault on raspberry pi. As soon as any write operation is attempted the drive is remounted read only. The machine is raspberryPi v.1 B+ (r0OMV 4.1.13+). I can however attach the same drive to my (manjaro 4.3.6-1-MANJARO) laptop and write to it without any problems.



    Any thoughts are appreciated. Given that this is a disk that works OK on other systems I would not want to simply buy a new disk, because it might have the same problems with raspberryPi and OMV. I can repeat the below steps I have done and I get exact same results again. Just to say - this disk functioned OK for a week or so days on the same raspberryPi machine and still can function well with my laptop. The disk is 7 years old. My troubleshooting steps so far have been:



    1) Unmount and do fsck:



    root@r0OMV:~#  e2fsck /dev/sda1
    e2fsck 1.42.5 (29-Jul-2012)
    ForteBKP: recovering journal
    ForteBKP contains a file system with errors, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    ForteBKP: 11/45793280 files (0.0% non-contiguous), 2924481/183143385 blocks


    immediately after I can mount it:



    mount -a


    then mount shows:



    /dev/sda1 on /media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)


    if I try to mkdir I get error:



    mkdir: cannot create directory `/media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c/touch': Read-only file system


    and mount shows:



    /dev/sda1 on /media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c type ext4 (ro,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)


    as this happens syslog output is:



    Mar  5 12:08:48 r0OMV kernel: [49725.089841] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
    Mar 5 12:08:50 r0OMV kernel: [49727.055478] blk_update_request: critical target error, dev sda, sector 0
    Mar 5 12:08:55 r0OMV kernel: [49732.679403] blk_update_request: critical target error, dev sda, sector 730073112
    Mar 5 12:08:55 r0OMV kernel: [49732.679520] Aborting journal on device sda1-8.
    Mar 5 12:08:56 r0OMV kernel: [49733.120506] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
    Mar 5 12:08:56 r0OMV kernel: [49733.134090] EXT4-fs (sda1): Remounting filesystem read-only


    2) Other steps taken:
    I have looked into hdparm and smartctl



    root@r0OMV:~# hdparm -I /dev/sda1
    /dev/sda1:
    ATA device, with non-removable media
    Model Number: ST3750640AS
    Serial Number: 5QD40Q51
    Firmware Revision: 3.AFM
    Standards:
    Supported: 7 6 5 4
    Likely used: 7
    Configuration:
    Logical max current
    cylinders 16383 16383
    heads 16 16
    sectors/track 63 63
    ... the rest of output seems normal and I cut it for the sake of brevity

    root@r0OMV:~# hdparm -r0 /dev/sda1
    /dev/sda1:
    setting readonly to 0 (off)
    readonly = 0 (off)

    root@r0OMV:~# hdparm -W /dev/sda1
    /dev/sda1:
    write-caching = 0 (off)


    but this has produced no results.



    With smartctl after long test I find that the result is



    smartctl -H /dev/sda 
    smartctl 5.41 2011-06-09 r3365 [armv6l-linux-4.1.13+] (local build)
    Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    Please note the following marginal Attributes:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    190 Airflow_Temperature_Cel 0x0022 051 034 045 Old_age Always In_the_past 49 (92 106 63 32)


    The rest of the parameters are withing normal limits when I check with -a flag I see that the tests I have done recently seem OK.



    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Extended offline Aborted by host 80% 15285 -
    # 2 Extended offline Aborted by host 90% 15285 -
    # 3 Extended offline Aborted by host 80% 15285 -
    # 4 Short offline Completed without error 00% 15285 -
    # 5 Extended offline Aborted by host 70% 15276 -
    # 6 Extended offline Completed without error 00% 15157









    share|improve this question



























      1












      1








      1








      I have attached a Seagate external hard drive (FreeAgent 750GB) to Open Media Vault on raspberry pi. As soon as any write operation is attempted the drive is remounted read only. The machine is raspberryPi v.1 B+ (r0OMV 4.1.13+). I can however attach the same drive to my (manjaro 4.3.6-1-MANJARO) laptop and write to it without any problems.



      Any thoughts are appreciated. Given that this is a disk that works OK on other systems I would not want to simply buy a new disk, because it might have the same problems with raspberryPi and OMV. I can repeat the below steps I have done and I get exact same results again. Just to say - this disk functioned OK for a week or so days on the same raspberryPi machine and still can function well with my laptop. The disk is 7 years old. My troubleshooting steps so far have been:



      1) Unmount and do fsck:



      root@r0OMV:~#  e2fsck /dev/sda1
      e2fsck 1.42.5 (29-Jul-2012)
      ForteBKP: recovering journal
      ForteBKP contains a file system with errors, check forced.
      Pass 1: Checking inodes, blocks, and sizes
      Pass 2: Checking directory structure
      Pass 3: Checking directory connectivity
      Pass 4: Checking reference counts
      Pass 5: Checking group summary information
      ForteBKP: 11/45793280 files (0.0% non-contiguous), 2924481/183143385 blocks


      immediately after I can mount it:



      mount -a


      then mount shows:



      /dev/sda1 on /media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)


      if I try to mkdir I get error:



      mkdir: cannot create directory `/media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c/touch': Read-only file system


      and mount shows:



      /dev/sda1 on /media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c type ext4 (ro,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)


      as this happens syslog output is:



      Mar  5 12:08:48 r0OMV kernel: [49725.089841] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
      Mar 5 12:08:50 r0OMV kernel: [49727.055478] blk_update_request: critical target error, dev sda, sector 0
      Mar 5 12:08:55 r0OMV kernel: [49732.679403] blk_update_request: critical target error, dev sda, sector 730073112
      Mar 5 12:08:55 r0OMV kernel: [49732.679520] Aborting journal on device sda1-8.
      Mar 5 12:08:56 r0OMV kernel: [49733.120506] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
      Mar 5 12:08:56 r0OMV kernel: [49733.134090] EXT4-fs (sda1): Remounting filesystem read-only


      2) Other steps taken:
      I have looked into hdparm and smartctl



      root@r0OMV:~# hdparm -I /dev/sda1
      /dev/sda1:
      ATA device, with non-removable media
      Model Number: ST3750640AS
      Serial Number: 5QD40Q51
      Firmware Revision: 3.AFM
      Standards:
      Supported: 7 6 5 4
      Likely used: 7
      Configuration:
      Logical max current
      cylinders 16383 16383
      heads 16 16
      sectors/track 63 63
      ... the rest of output seems normal and I cut it for the sake of brevity

      root@r0OMV:~# hdparm -r0 /dev/sda1
      /dev/sda1:
      setting readonly to 0 (off)
      readonly = 0 (off)

      root@r0OMV:~# hdparm -W /dev/sda1
      /dev/sda1:
      write-caching = 0 (off)


      but this has produced no results.



      With smartctl after long test I find that the result is



      smartctl -H /dev/sda 
      smartctl 5.41 2011-06-09 r3365 [armv6l-linux-4.1.13+] (local build)
      Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

      === START OF READ SMART DATA SECTION ===
      SMART overall-health self-assessment test result: PASSED
      Please note the following marginal Attributes:
      ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
      190 Airflow_Temperature_Cel 0x0022 051 034 045 Old_age Always In_the_past 49 (92 106 63 32)


      The rest of the parameters are withing normal limits when I check with -a flag I see that the tests I have done recently seem OK.



      SMART Self-test log structure revision number 1
      Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
      # 1 Extended offline Aborted by host 80% 15285 -
      # 2 Extended offline Aborted by host 90% 15285 -
      # 3 Extended offline Aborted by host 80% 15285 -
      # 4 Short offline Completed without error 00% 15285 -
      # 5 Extended offline Aborted by host 70% 15276 -
      # 6 Extended offline Completed without error 00% 15157









      share|improve this question
















      I have attached a Seagate external hard drive (FreeAgent 750GB) to Open Media Vault on raspberry pi. As soon as any write operation is attempted the drive is remounted read only. The machine is raspberryPi v.1 B+ (r0OMV 4.1.13+). I can however attach the same drive to my (manjaro 4.3.6-1-MANJARO) laptop and write to it without any problems.



      Any thoughts are appreciated. Given that this is a disk that works OK on other systems I would not want to simply buy a new disk, because it might have the same problems with raspberryPi and OMV. I can repeat the below steps I have done and I get exact same results again. Just to say - this disk functioned OK for a week or so days on the same raspberryPi machine and still can function well with my laptop. The disk is 7 years old. My troubleshooting steps so far have been:



      1) Unmount and do fsck:



      root@r0OMV:~#  e2fsck /dev/sda1
      e2fsck 1.42.5 (29-Jul-2012)
      ForteBKP: recovering journal
      ForteBKP contains a file system with errors, check forced.
      Pass 1: Checking inodes, blocks, and sizes
      Pass 2: Checking directory structure
      Pass 3: Checking directory connectivity
      Pass 4: Checking reference counts
      Pass 5: Checking group summary information
      ForteBKP: 11/45793280 files (0.0% non-contiguous), 2924481/183143385 blocks


      immediately after I can mount it:



      mount -a


      then mount shows:



      /dev/sda1 on /media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)


      if I try to mkdir I get error:



      mkdir: cannot create directory `/media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c/touch': Read-only file system


      and mount shows:



      /dev/sda1 on /media/49fb4a0f-c826-4a7c-877a-76c98dba5b2c type ext4 (ro,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev)


      as this happens syslog output is:



      Mar  5 12:08:48 r0OMV kernel: [49725.089841] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
      Mar 5 12:08:50 r0OMV kernel: [49727.055478] blk_update_request: critical target error, dev sda, sector 0
      Mar 5 12:08:55 r0OMV kernel: [49732.679403] blk_update_request: critical target error, dev sda, sector 730073112
      Mar 5 12:08:55 r0OMV kernel: [49732.679520] Aborting journal on device sda1-8.
      Mar 5 12:08:56 r0OMV kernel: [49733.120506] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
      Mar 5 12:08:56 r0OMV kernel: [49733.134090] EXT4-fs (sda1): Remounting filesystem read-only


      2) Other steps taken:
      I have looked into hdparm and smartctl



      root@r0OMV:~# hdparm -I /dev/sda1
      /dev/sda1:
      ATA device, with non-removable media
      Model Number: ST3750640AS
      Serial Number: 5QD40Q51
      Firmware Revision: 3.AFM
      Standards:
      Supported: 7 6 5 4
      Likely used: 7
      Configuration:
      Logical max current
      cylinders 16383 16383
      heads 16 16
      sectors/track 63 63
      ... the rest of output seems normal and I cut it for the sake of brevity

      root@r0OMV:~# hdparm -r0 /dev/sda1
      /dev/sda1:
      setting readonly to 0 (off)
      readonly = 0 (off)

      root@r0OMV:~# hdparm -W /dev/sda1
      /dev/sda1:
      write-caching = 0 (off)


      but this has produced no results.



      With smartctl after long test I find that the result is



      smartctl -H /dev/sda 
      smartctl 5.41 2011-06-09 r3365 [armv6l-linux-4.1.13+] (local build)
      Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

      === START OF READ SMART DATA SECTION ===
      SMART overall-health self-assessment test result: PASSED
      Please note the following marginal Attributes:
      ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
      190 Airflow_Temperature_Cel 0x0022 051 034 045 Old_age Always In_the_past 49 (92 106 63 32)


      The rest of the parameters are withing normal limits when I check with -a flag I see that the tests I have done recently seem OK.



      SMART Self-test log structure revision number 1
      Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
      # 1 Extended offline Aborted by host 80% 15285 -
      # 2 Extended offline Aborted by host 90% 15285 -
      # 3 Extended offline Aborted by host 80% 15285 -
      # 4 Short offline Completed without error 00% 15285 -
      # 5 Extended offline Aborted by host 70% 15276 -
      # 6 Extended offline Completed without error 00% 15157






      debian mount raspberry-pi






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 6 hours ago









      Rui F Ribeiro

      42.2k1484142




      42.2k1484142










      asked Mar 5 '16 at 12:59









      r0bertsr0berts

      4001215




      4001215






















          1 Answer
          1






          active

          oldest

          votes


















          1














          I have a USB adapter that is following a similar behavior.
          As weird as it sounds mounting ext3 as ext2 (means not journaling) allows the disk to work. Perhaps thats an option.






          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f267798%2fusb-hdd-ext4-changes-to-read-only-what-is-the-problem-works-on-other-system%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            I have a USB adapter that is following a similar behavior.
            As weird as it sounds mounting ext3 as ext2 (means not journaling) allows the disk to work. Perhaps thats an option.






            share|improve this answer




























              1














              I have a USB adapter that is following a similar behavior.
              As weird as it sounds mounting ext3 as ext2 (means not journaling) allows the disk to work. Perhaps thats an option.






              share|improve this answer


























                1












                1








                1







                I have a USB adapter that is following a similar behavior.
                As weird as it sounds mounting ext3 as ext2 (means not journaling) allows the disk to work. Perhaps thats an option.






                share|improve this answer













                I have a USB adapter that is following a similar behavior.
                As weird as it sounds mounting ext3 as ext2 (means not journaling) allows the disk to work. Perhaps thats an option.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 13 '17 at 1:09









                user2512766user2512766

                111




                111






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f267798%2fusb-hdd-ext4-changes-to-read-only-what-is-the-problem-works-on-other-system%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    j5z2ds,s3uL AjGySz0uaroZnpYdlroOo
                    MGtc76abRRmCb,16,yX9CoLxuUtee74QM4J,LVQvPq3O,wvlGguN0Lg VpNPHvosy7ztZhvXKq,s dI 6AbD,R5WBxTBelUC

                    Popular posts from this blog

                    Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                    Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                    Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...