Debian - microSD lost async page write The 2019 Stack Overflow Developer Survey Results Are InHow can I low-level format flash memory in Linux?Debian Wheezy youtube video missing on pagexorg: lost screen resolution after Debian/Jessie upgradeDifference between 'sync' and 'async' mount optionsHow can I auto-mount my MicroSD?dd'ing SDD, decreasing write speedARM Debian: how to transfer system from MicroSD to internal flash?SSD as write target during readsWRITE SAME manually zeroDebian Disk Manager ProblemLost wifi connection debian 8 (rtl8821ae wifi driver)

The phrase "to the numbers born"?

Is it okay to consider publishing in my first year of PhD?

If I score a critical hit on an 18 or higher, what are my chances of getting a critical hit if I roll 3d20?

What is the meaning of Triage in Cybersec world?

Star Trek - X-shaped Item on Regula/Orbital Office Starbases

What's the name of these plastic connectors

Did Scotland spend $250,000 for the slogan "Welcome to Scotland"?

Why don't hard Brexiteers insist on a hard border to prevent illegal immigration after Brexit?

Are there any other methods to apply to solving simultaneous equations?

Can a flute soloist sit?

What do these terms in Caesar's Gallic wars mean?

Why couldn't they take pictures of a closer black hole?

How to obtain a position of last non-zero element

Mathematics of imaging the black hole

What is the most efficient way to store a numeric range?

What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?

What is preventing me from simply constructing a hash that's lower than the current target?

What does Linus Torvalds mean when he says that Git "never ever" tracks a file?

Why was M87 targeted for the Event Horizon Telescope instead of Sagittarius A*?

How come people say “Would of”?

Match Roman Numerals

Relationship between Gromov-Witten and Taubes' Gromov invariant

How can I add encounters in the Lost Mine of Phandelver campaign without giving PCs too much XP?

APIPA and LAN Broadcast Domain



Debian - microSD lost async page write



The 2019 Stack Overflow Developer Survey Results Are InHow can I low-level format flash memory in Linux?Debian Wheezy youtube video missing on pagexorg: lost screen resolution after Debian/Jessie upgradeDifference between 'sync' and 'async' mount optionsHow can I auto-mount my MicroSD?dd'ing SDD, decreasing write speedARM Debian: how to transfer system from MicroSD to internal flash?SSD as write target during readsWRITE SAME manually zeroDebian Disk Manager ProblemLost wifi connection debian 8 (rtl8821ae wifi driver)



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








1















I face some issue with microSD on a Lenovo S130-14IGM. My laptop is running lastest Debian 9.
I have a microSD with an ext4 partition located on /dev/mmcblk1p3 which behave strangely.



When I try to copy /home to it, it's surprisingly fast (it's normal microSD, not an extreme or pro model) :



use@server:~$ df -hP /home
/dev/mmcblk0p3 11G 226M 11G 3% /home

use@server:~$ time sudo cp -a /home/ /mnt/backup/home.bak
real 0m2,249s
user 0m0,109s
sys 0m0,944s


Then when I try to deleted it, I does not work.



use@server:~$ time sudo rm -rf /mnt/backup/home.bak


The command line prompt stay stuck. After a Ctrl+C, it tells me that the device is read protected.
I cannot remount it in read and write. When I reboot I face this kinds of errors :



[ 6.375297] mmc1: cannot verify signal voltage switch
[ 7.825684] print_req_error: I/O error, dev mmcblk1, sector 88151744
[ 7.825795] Buffer I/O error on dev mmcblk1p3, logical block 532952, lost async page write
[ 7.825927] Buffer I/O error on dev mmcblk1p3, logical block 532953, lost async page write
[ 7.826035] Buffer I/O error on dev mmcblk1p3, logical block 532954, lost async page write
[ 7.826142] Buffer I/O error on dev mmcblk1p3, logical block 532955, lost async page write
[ 7.826248] Buffer I/O error on dev mmcblk1p3, logical block 532956, lost async page write
[ 7.826353] Buffer I/O error on dev mmcblk1p3, logical block 532957, lost async page write
[ 7.826458] Buffer I/O error on dev mmcblk1p3, logical block 532958, lost async page write
[ 7.826563] Buffer I/O error on dev mmcblk1p3, logical block 532959, lost async page write
[ 7.826672] Buffer I/O error on dev mmcblk1p3, logical block 532960, lost async page write
[ 7.826779] Buffer I/O error on dev mmcblk1p3, logical block 532961, lost async page write
[ 11.283705] EXT4-fs (mmcblk1p3): mounted filesystem with ordered data mode. Opts: (null)


I tried with different microSD, always the same problem.
Is this a physical problem ? Or and OS related problem ?



EDIT : more information :



[ 101.259951] mmc1: cannot verify signal voltage switch
[ 102.762217] print_req_error: I/O error, dev mmcblk1, sector 96471296
[ 102.762232] Buffer I/O error on dev mmcblk1p3, logical block 1572896, lost async page write
[...]
[ 102.762283] Buffer I/O error on dev mmcblk1p3, logical block 1572904, lost async page write
[ 102.762287] Buffer I/O error on dev mmcblk1p3, logical block 1572905, lost async page write
[ 102.826584] JBD2: recovery failed
[ 102.826595] EXT4-fs (mmcblk1p3): error loading journal
[ 107.788103] mmc1: card 1234 removed
[ 114.171661] mmc1: cannot verify signal voltage switch
[ 114.295837] mmc1: new ultra high speed SDR104 SDXC card at address 1234
[ 114.297762] mmcblk1: mmc1:1234 SA64G 57.7 GiB
[ 114.298854] mmcblk1: p1 p2 p3
[ 118.234255] mmc1: cannot verify signal voltage switch
[ 119.713075] print_req_error: I/O error, dev mmcblk1, sector 96471296
[ 119.713091] buffer_io_error: 118 callbacks suppressed
[ 119.713095] Buffer I/O error on dev mmcblk1p3, logical block 1572896, lost async page write
[ 119.713120] Buffer I/O error on dev mmcblk1p3, logical block 1572897, lost async page write
[...]
[ 119.713167] Buffer I/O error on dev mmcblk1p3, logical block 1572905, lost async page write
[ 119.772674] JBD2: recovery failed
[ 119.772685] EXT4-fs (mmcblk1p3): error loading journal
[ 125.129966] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[ 261.588698] mmc1: cannot verify signal voltage switch
[ 263.092258] print_req_error: I/O error, dev mmcblk1, sector 42240000
[...]
[ 263.402597] print_req_error: I/O error, dev mmcblk1, sector 42243072
[ 263.402610] EXT4-fs warning (device mmcblk1p2): ext4_end_bio:323: I/O error 10 writing to inode 917598 (offset 0 size 8388608 starting block 5280512)
[...]
[ 401.751429] mmc1: cannot verify signal voltage switch
[ 403.197791] print_req_error: I/O error, dev mmcblk1, sector 71374080
[ 543.585526] EXT4-fs warning: 25 callbacks suppressed

$ lspci | grep -i card
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)


I tried this kernel driver without success : https://github.com/Zibri/Realtek-rts5229-linux-driver










share|improve this question






























    1















    I face some issue with microSD on a Lenovo S130-14IGM. My laptop is running lastest Debian 9.
    I have a microSD with an ext4 partition located on /dev/mmcblk1p3 which behave strangely.



    When I try to copy /home to it, it's surprisingly fast (it's normal microSD, not an extreme or pro model) :



    use@server:~$ df -hP /home
    /dev/mmcblk0p3 11G 226M 11G 3% /home

    use@server:~$ time sudo cp -a /home/ /mnt/backup/home.bak
    real 0m2,249s
    user 0m0,109s
    sys 0m0,944s


    Then when I try to deleted it, I does not work.



    use@server:~$ time sudo rm -rf /mnt/backup/home.bak


    The command line prompt stay stuck. After a Ctrl+C, it tells me that the device is read protected.
    I cannot remount it in read and write. When I reboot I face this kinds of errors :



    [ 6.375297] mmc1: cannot verify signal voltage switch
    [ 7.825684] print_req_error: I/O error, dev mmcblk1, sector 88151744
    [ 7.825795] Buffer I/O error on dev mmcblk1p3, logical block 532952, lost async page write
    [ 7.825927] Buffer I/O error on dev mmcblk1p3, logical block 532953, lost async page write
    [ 7.826035] Buffer I/O error on dev mmcblk1p3, logical block 532954, lost async page write
    [ 7.826142] Buffer I/O error on dev mmcblk1p3, logical block 532955, lost async page write
    [ 7.826248] Buffer I/O error on dev mmcblk1p3, logical block 532956, lost async page write
    [ 7.826353] Buffer I/O error on dev mmcblk1p3, logical block 532957, lost async page write
    [ 7.826458] Buffer I/O error on dev mmcblk1p3, logical block 532958, lost async page write
    [ 7.826563] Buffer I/O error on dev mmcblk1p3, logical block 532959, lost async page write
    [ 7.826672] Buffer I/O error on dev mmcblk1p3, logical block 532960, lost async page write
    [ 7.826779] Buffer I/O error on dev mmcblk1p3, logical block 532961, lost async page write
    [ 11.283705] EXT4-fs (mmcblk1p3): mounted filesystem with ordered data mode. Opts: (null)


    I tried with different microSD, always the same problem.
    Is this a physical problem ? Or and OS related problem ?



    EDIT : more information :



    [ 101.259951] mmc1: cannot verify signal voltage switch
    [ 102.762217] print_req_error: I/O error, dev mmcblk1, sector 96471296
    [ 102.762232] Buffer I/O error on dev mmcblk1p3, logical block 1572896, lost async page write
    [...]
    [ 102.762283] Buffer I/O error on dev mmcblk1p3, logical block 1572904, lost async page write
    [ 102.762287] Buffer I/O error on dev mmcblk1p3, logical block 1572905, lost async page write
    [ 102.826584] JBD2: recovery failed
    [ 102.826595] EXT4-fs (mmcblk1p3): error loading journal
    [ 107.788103] mmc1: card 1234 removed
    [ 114.171661] mmc1: cannot verify signal voltage switch
    [ 114.295837] mmc1: new ultra high speed SDR104 SDXC card at address 1234
    [ 114.297762] mmcblk1: mmc1:1234 SA64G 57.7 GiB
    [ 114.298854] mmcblk1: p1 p2 p3
    [ 118.234255] mmc1: cannot verify signal voltage switch
    [ 119.713075] print_req_error: I/O error, dev mmcblk1, sector 96471296
    [ 119.713091] buffer_io_error: 118 callbacks suppressed
    [ 119.713095] Buffer I/O error on dev mmcblk1p3, logical block 1572896, lost async page write
    [ 119.713120] Buffer I/O error on dev mmcblk1p3, logical block 1572897, lost async page write
    [...]
    [ 119.713167] Buffer I/O error on dev mmcblk1p3, logical block 1572905, lost async page write
    [ 119.772674] JBD2: recovery failed
    [ 119.772685] EXT4-fs (mmcblk1p3): error loading journal
    [ 125.129966] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
    [ 261.588698] mmc1: cannot verify signal voltage switch
    [ 263.092258] print_req_error: I/O error, dev mmcblk1, sector 42240000
    [...]
    [ 263.402597] print_req_error: I/O error, dev mmcblk1, sector 42243072
    [ 263.402610] EXT4-fs warning (device mmcblk1p2): ext4_end_bio:323: I/O error 10 writing to inode 917598 (offset 0 size 8388608 starting block 5280512)
    [...]
    [ 401.751429] mmc1: cannot verify signal voltage switch
    [ 403.197791] print_req_error: I/O error, dev mmcblk1, sector 71374080
    [ 543.585526] EXT4-fs warning: 25 callbacks suppressed

    $ lspci | grep -i card
    02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)


    I tried this kernel driver without success : https://github.com/Zibri/Realtek-rts5229-linux-driver










    share|improve this question


























      1












      1








      1








      I face some issue with microSD on a Lenovo S130-14IGM. My laptop is running lastest Debian 9.
      I have a microSD with an ext4 partition located on /dev/mmcblk1p3 which behave strangely.



      When I try to copy /home to it, it's surprisingly fast (it's normal microSD, not an extreme or pro model) :



      use@server:~$ df -hP /home
      /dev/mmcblk0p3 11G 226M 11G 3% /home

      use@server:~$ time sudo cp -a /home/ /mnt/backup/home.bak
      real 0m2,249s
      user 0m0,109s
      sys 0m0,944s


      Then when I try to deleted it, I does not work.



      use@server:~$ time sudo rm -rf /mnt/backup/home.bak


      The command line prompt stay stuck. After a Ctrl+C, it tells me that the device is read protected.
      I cannot remount it in read and write. When I reboot I face this kinds of errors :



      [ 6.375297] mmc1: cannot verify signal voltage switch
      [ 7.825684] print_req_error: I/O error, dev mmcblk1, sector 88151744
      [ 7.825795] Buffer I/O error on dev mmcblk1p3, logical block 532952, lost async page write
      [ 7.825927] Buffer I/O error on dev mmcblk1p3, logical block 532953, lost async page write
      [ 7.826035] Buffer I/O error on dev mmcblk1p3, logical block 532954, lost async page write
      [ 7.826142] Buffer I/O error on dev mmcblk1p3, logical block 532955, lost async page write
      [ 7.826248] Buffer I/O error on dev mmcblk1p3, logical block 532956, lost async page write
      [ 7.826353] Buffer I/O error on dev mmcblk1p3, logical block 532957, lost async page write
      [ 7.826458] Buffer I/O error on dev mmcblk1p3, logical block 532958, lost async page write
      [ 7.826563] Buffer I/O error on dev mmcblk1p3, logical block 532959, lost async page write
      [ 7.826672] Buffer I/O error on dev mmcblk1p3, logical block 532960, lost async page write
      [ 7.826779] Buffer I/O error on dev mmcblk1p3, logical block 532961, lost async page write
      [ 11.283705] EXT4-fs (mmcblk1p3): mounted filesystem with ordered data mode. Opts: (null)


      I tried with different microSD, always the same problem.
      Is this a physical problem ? Or and OS related problem ?



      EDIT : more information :



      [ 101.259951] mmc1: cannot verify signal voltage switch
      [ 102.762217] print_req_error: I/O error, dev mmcblk1, sector 96471296
      [ 102.762232] Buffer I/O error on dev mmcblk1p3, logical block 1572896, lost async page write
      [...]
      [ 102.762283] Buffer I/O error on dev mmcblk1p3, logical block 1572904, lost async page write
      [ 102.762287] Buffer I/O error on dev mmcblk1p3, logical block 1572905, lost async page write
      [ 102.826584] JBD2: recovery failed
      [ 102.826595] EXT4-fs (mmcblk1p3): error loading journal
      [ 107.788103] mmc1: card 1234 removed
      [ 114.171661] mmc1: cannot verify signal voltage switch
      [ 114.295837] mmc1: new ultra high speed SDR104 SDXC card at address 1234
      [ 114.297762] mmcblk1: mmc1:1234 SA64G 57.7 GiB
      [ 114.298854] mmcblk1: p1 p2 p3
      [ 118.234255] mmc1: cannot verify signal voltage switch
      [ 119.713075] print_req_error: I/O error, dev mmcblk1, sector 96471296
      [ 119.713091] buffer_io_error: 118 callbacks suppressed
      [ 119.713095] Buffer I/O error on dev mmcblk1p3, logical block 1572896, lost async page write
      [ 119.713120] Buffer I/O error on dev mmcblk1p3, logical block 1572897, lost async page write
      [...]
      [ 119.713167] Buffer I/O error on dev mmcblk1p3, logical block 1572905, lost async page write
      [ 119.772674] JBD2: recovery failed
      [ 119.772685] EXT4-fs (mmcblk1p3): error loading journal
      [ 125.129966] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
      [ 261.588698] mmc1: cannot verify signal voltage switch
      [ 263.092258] print_req_error: I/O error, dev mmcblk1, sector 42240000
      [...]
      [ 263.402597] print_req_error: I/O error, dev mmcblk1, sector 42243072
      [ 263.402610] EXT4-fs warning (device mmcblk1p2): ext4_end_bio:323: I/O error 10 writing to inode 917598 (offset 0 size 8388608 starting block 5280512)
      [...]
      [ 401.751429] mmc1: cannot verify signal voltage switch
      [ 403.197791] print_req_error: I/O error, dev mmcblk1, sector 71374080
      [ 543.585526] EXT4-fs warning: 25 callbacks suppressed

      $ lspci | grep -i card
      02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)


      I tried this kernel driver without success : https://github.com/Zibri/Realtek-rts5229-linux-driver










      share|improve this question
















      I face some issue with microSD on a Lenovo S130-14IGM. My laptop is running lastest Debian 9.
      I have a microSD with an ext4 partition located on /dev/mmcblk1p3 which behave strangely.



      When I try to copy /home to it, it's surprisingly fast (it's normal microSD, not an extreme or pro model) :



      use@server:~$ df -hP /home
      /dev/mmcblk0p3 11G 226M 11G 3% /home

      use@server:~$ time sudo cp -a /home/ /mnt/backup/home.bak
      real 0m2,249s
      user 0m0,109s
      sys 0m0,944s


      Then when I try to deleted it, I does not work.



      use@server:~$ time sudo rm -rf /mnt/backup/home.bak


      The command line prompt stay stuck. After a Ctrl+C, it tells me that the device is read protected.
      I cannot remount it in read and write. When I reboot I face this kinds of errors :



      [ 6.375297] mmc1: cannot verify signal voltage switch
      [ 7.825684] print_req_error: I/O error, dev mmcblk1, sector 88151744
      [ 7.825795] Buffer I/O error on dev mmcblk1p3, logical block 532952, lost async page write
      [ 7.825927] Buffer I/O error on dev mmcblk1p3, logical block 532953, lost async page write
      [ 7.826035] Buffer I/O error on dev mmcblk1p3, logical block 532954, lost async page write
      [ 7.826142] Buffer I/O error on dev mmcblk1p3, logical block 532955, lost async page write
      [ 7.826248] Buffer I/O error on dev mmcblk1p3, logical block 532956, lost async page write
      [ 7.826353] Buffer I/O error on dev mmcblk1p3, logical block 532957, lost async page write
      [ 7.826458] Buffer I/O error on dev mmcblk1p3, logical block 532958, lost async page write
      [ 7.826563] Buffer I/O error on dev mmcblk1p3, logical block 532959, lost async page write
      [ 7.826672] Buffer I/O error on dev mmcblk1p3, logical block 532960, lost async page write
      [ 7.826779] Buffer I/O error on dev mmcblk1p3, logical block 532961, lost async page write
      [ 11.283705] EXT4-fs (mmcblk1p3): mounted filesystem with ordered data mode. Opts: (null)


      I tried with different microSD, always the same problem.
      Is this a physical problem ? Or and OS related problem ?



      EDIT : more information :



      [ 101.259951] mmc1: cannot verify signal voltage switch
      [ 102.762217] print_req_error: I/O error, dev mmcblk1, sector 96471296
      [ 102.762232] Buffer I/O error on dev mmcblk1p3, logical block 1572896, lost async page write
      [...]
      [ 102.762283] Buffer I/O error on dev mmcblk1p3, logical block 1572904, lost async page write
      [ 102.762287] Buffer I/O error on dev mmcblk1p3, logical block 1572905, lost async page write
      [ 102.826584] JBD2: recovery failed
      [ 102.826595] EXT4-fs (mmcblk1p3): error loading journal
      [ 107.788103] mmc1: card 1234 removed
      [ 114.171661] mmc1: cannot verify signal voltage switch
      [ 114.295837] mmc1: new ultra high speed SDR104 SDXC card at address 1234
      [ 114.297762] mmcblk1: mmc1:1234 SA64G 57.7 GiB
      [ 114.298854] mmcblk1: p1 p2 p3
      [ 118.234255] mmc1: cannot verify signal voltage switch
      [ 119.713075] print_req_error: I/O error, dev mmcblk1, sector 96471296
      [ 119.713091] buffer_io_error: 118 callbacks suppressed
      [ 119.713095] Buffer I/O error on dev mmcblk1p3, logical block 1572896, lost async page write
      [ 119.713120] Buffer I/O error on dev mmcblk1p3, logical block 1572897, lost async page write
      [...]
      [ 119.713167] Buffer I/O error on dev mmcblk1p3, logical block 1572905, lost async page write
      [ 119.772674] JBD2: recovery failed
      [ 119.772685] EXT4-fs (mmcblk1p3): error loading journal
      [ 125.129966] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
      [ 261.588698] mmc1: cannot verify signal voltage switch
      [ 263.092258] print_req_error: I/O error, dev mmcblk1, sector 42240000
      [...]
      [ 263.402597] print_req_error: I/O error, dev mmcblk1, sector 42243072
      [ 263.402610] EXT4-fs warning (device mmcblk1p2): ext4_end_bio:323: I/O error 10 writing to inode 917598 (offset 0 size 8388608 starting block 5280512)
      [...]
      [ 401.751429] mmc1: cannot verify signal voltage switch
      [ 403.197791] print_req_error: I/O error, dev mmcblk1, sector 71374080
      [ 543.585526] EXT4-fs warning: 25 callbacks suppressed

      $ lspci | grep -i card
      02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)


      I tried this kernel driver without success : https://github.com/Zibri/Realtek-rts5229-linux-driver







      debian disk ssd






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited yesterday







      BDR

















      asked Apr 8 at 9:54









      BDRBDR

      1115




      1115




















          2 Answers
          2






          active

          oldest

          votes


















          2














          Assuming /mnt/backup/home.bak is a folder with write access, this sounds like a physical problem, or corrupted partition table. You should run fsck. For backup partition ddrescue is recommended.






          share|improve this answer










          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.




















          • Thanks for your help ! Yes, /dev/mmcblk1p3 is mounted with default option (in rw). I have partitioned several times the microSD with different start block without success. It's not a real backup partition, I'll use it as it but not until this problem is solved. Is there any other test I can do ?

            – BDR
            Apr 8 at 12:14












          • i guess this microSD is just end of life (wear-out). try badblocks or check unix.stackexchange.com/questions/30182 electronics.stackexchange.com/questions/27619

            – alecxs
            Apr 8 at 12:26











          • I have tried this with 3 or 4 differents SD card (which run perfectly in DSLR, etc) always the same result. I'll try the things you mention.

            – BDR
            2 days ago











          • have you thought about the card reader may cause this fault?

            – alecxs
            2 days ago


















          0














          After research i found out that it may OS related. Do you have SDHC or SDXC cards? There may some incompatiblity with Card Reader. The first error message mmc1: cannot verify signal voltage switch is kernel related. Someone has reported this as bug for Fedora 28. But is unclear to me if it is really a bug or hardware incompatiblity. Do you have the possibility to test the Card Reader with Windows?






          share|improve this answer








          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.




















          • I added some information. I tried to install Windows 10 but failed with error : no device drivers were found

            – BDR
            yesterday











          • Ok forget windows. Can you try to compile this driver? github.com/astyonax/patched-RTS5227-5229

            – alecxs
            13 hours ago











          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%2f511194%2fdebian-microsd-lost-async-page-write%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          Assuming /mnt/backup/home.bak is a folder with write access, this sounds like a physical problem, or corrupted partition table. You should run fsck. For backup partition ddrescue is recommended.






          share|improve this answer










          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.




















          • Thanks for your help ! Yes, /dev/mmcblk1p3 is mounted with default option (in rw). I have partitioned several times the microSD with different start block without success. It's not a real backup partition, I'll use it as it but not until this problem is solved. Is there any other test I can do ?

            – BDR
            Apr 8 at 12:14












          • i guess this microSD is just end of life (wear-out). try badblocks or check unix.stackexchange.com/questions/30182 electronics.stackexchange.com/questions/27619

            – alecxs
            Apr 8 at 12:26











          • I have tried this with 3 or 4 differents SD card (which run perfectly in DSLR, etc) always the same result. I'll try the things you mention.

            – BDR
            2 days ago











          • have you thought about the card reader may cause this fault?

            – alecxs
            2 days ago















          2














          Assuming /mnt/backup/home.bak is a folder with write access, this sounds like a physical problem, or corrupted partition table. You should run fsck. For backup partition ddrescue is recommended.






          share|improve this answer










          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.




















          • Thanks for your help ! Yes, /dev/mmcblk1p3 is mounted with default option (in rw). I have partitioned several times the microSD with different start block without success. It's not a real backup partition, I'll use it as it but not until this problem is solved. Is there any other test I can do ?

            – BDR
            Apr 8 at 12:14












          • i guess this microSD is just end of life (wear-out). try badblocks or check unix.stackexchange.com/questions/30182 electronics.stackexchange.com/questions/27619

            – alecxs
            Apr 8 at 12:26











          • I have tried this with 3 or 4 differents SD card (which run perfectly in DSLR, etc) always the same result. I'll try the things you mention.

            – BDR
            2 days ago











          • have you thought about the card reader may cause this fault?

            – alecxs
            2 days ago













          2












          2








          2







          Assuming /mnt/backup/home.bak is a folder with write access, this sounds like a physical problem, or corrupted partition table. You should run fsck. For backup partition ddrescue is recommended.






          share|improve this answer










          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.










          Assuming /mnt/backup/home.bak is a folder with write access, this sounds like a physical problem, or corrupted partition table. You should run fsck. For backup partition ddrescue is recommended.







          share|improve this answer










          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          share|improve this answer



          share|improve this answer








          edited Apr 8 at 21:32





















          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          answered Apr 8 at 11:58









          alecxsalecxs

          463




          463




          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





          New contributor





          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.






          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.












          • Thanks for your help ! Yes, /dev/mmcblk1p3 is mounted with default option (in rw). I have partitioned several times the microSD with different start block without success. It's not a real backup partition, I'll use it as it but not until this problem is solved. Is there any other test I can do ?

            – BDR
            Apr 8 at 12:14












          • i guess this microSD is just end of life (wear-out). try badblocks or check unix.stackexchange.com/questions/30182 electronics.stackexchange.com/questions/27619

            – alecxs
            Apr 8 at 12:26











          • I have tried this with 3 or 4 differents SD card (which run perfectly in DSLR, etc) always the same result. I'll try the things you mention.

            – BDR
            2 days ago











          • have you thought about the card reader may cause this fault?

            – alecxs
            2 days ago

















          • Thanks for your help ! Yes, /dev/mmcblk1p3 is mounted with default option (in rw). I have partitioned several times the microSD with different start block without success. It's not a real backup partition, I'll use it as it but not until this problem is solved. Is there any other test I can do ?

            – BDR
            Apr 8 at 12:14












          • i guess this microSD is just end of life (wear-out). try badblocks or check unix.stackexchange.com/questions/30182 electronics.stackexchange.com/questions/27619

            – alecxs
            Apr 8 at 12:26











          • I have tried this with 3 or 4 differents SD card (which run perfectly in DSLR, etc) always the same result. I'll try the things you mention.

            – BDR
            2 days ago











          • have you thought about the card reader may cause this fault?

            – alecxs
            2 days ago
















          Thanks for your help ! Yes, /dev/mmcblk1p3 is mounted with default option (in rw). I have partitioned several times the microSD with different start block without success. It's not a real backup partition, I'll use it as it but not until this problem is solved. Is there any other test I can do ?

          – BDR
          Apr 8 at 12:14






          Thanks for your help ! Yes, /dev/mmcblk1p3 is mounted with default option (in rw). I have partitioned several times the microSD with different start block without success. It's not a real backup partition, I'll use it as it but not until this problem is solved. Is there any other test I can do ?

          – BDR
          Apr 8 at 12:14














          i guess this microSD is just end of life (wear-out). try badblocks or check unix.stackexchange.com/questions/30182 electronics.stackexchange.com/questions/27619

          – alecxs
          Apr 8 at 12:26





          i guess this microSD is just end of life (wear-out). try badblocks or check unix.stackexchange.com/questions/30182 electronics.stackexchange.com/questions/27619

          – alecxs
          Apr 8 at 12:26













          I have tried this with 3 or 4 differents SD card (which run perfectly in DSLR, etc) always the same result. I'll try the things you mention.

          – BDR
          2 days ago





          I have tried this with 3 or 4 differents SD card (which run perfectly in DSLR, etc) always the same result. I'll try the things you mention.

          – BDR
          2 days ago













          have you thought about the card reader may cause this fault?

          – alecxs
          2 days ago





          have you thought about the card reader may cause this fault?

          – alecxs
          2 days ago













          0














          After research i found out that it may OS related. Do you have SDHC or SDXC cards? There may some incompatiblity with Card Reader. The first error message mmc1: cannot verify signal voltage switch is kernel related. Someone has reported this as bug for Fedora 28. But is unclear to me if it is really a bug or hardware incompatiblity. Do you have the possibility to test the Card Reader with Windows?






          share|improve this answer








          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.




















          • I added some information. I tried to install Windows 10 but failed with error : no device drivers were found

            – BDR
            yesterday











          • Ok forget windows. Can you try to compile this driver? github.com/astyonax/patched-RTS5227-5229

            – alecxs
            13 hours ago















          0














          After research i found out that it may OS related. Do you have SDHC or SDXC cards? There may some incompatiblity with Card Reader. The first error message mmc1: cannot verify signal voltage switch is kernel related. Someone has reported this as bug for Fedora 28. But is unclear to me if it is really a bug or hardware incompatiblity. Do you have the possibility to test the Card Reader with Windows?






          share|improve this answer








          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.




















          • I added some information. I tried to install Windows 10 but failed with error : no device drivers were found

            – BDR
            yesterday











          • Ok forget windows. Can you try to compile this driver? github.com/astyonax/patched-RTS5227-5229

            – alecxs
            13 hours ago













          0












          0








          0







          After research i found out that it may OS related. Do you have SDHC or SDXC cards? There may some incompatiblity with Card Reader. The first error message mmc1: cannot verify signal voltage switch is kernel related. Someone has reported this as bug for Fedora 28. But is unclear to me if it is really a bug or hardware incompatiblity. Do you have the possibility to test the Card Reader with Windows?






          share|improve this answer








          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.










          After research i found out that it may OS related. Do you have SDHC or SDXC cards? There may some incompatiblity with Card Reader. The first error message mmc1: cannot verify signal voltage switch is kernel related. Someone has reported this as bug for Fedora 28. But is unclear to me if it is really a bug or hardware incompatiblity. Do you have the possibility to test the Card Reader with Windows?







          share|improve this answer








          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          share|improve this answer



          share|improve this answer






          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          answered yesterday









          alecxsalecxs

          463




          463




          New contributor




          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





          New contributor





          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.






          alecxs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.












          • I added some information. I tried to install Windows 10 but failed with error : no device drivers were found

            – BDR
            yesterday











          • Ok forget windows. Can you try to compile this driver? github.com/astyonax/patched-RTS5227-5229

            – alecxs
            13 hours ago

















          • I added some information. I tried to install Windows 10 but failed with error : no device drivers were found

            – BDR
            yesterday











          • Ok forget windows. Can you try to compile this driver? github.com/astyonax/patched-RTS5227-5229

            – alecxs
            13 hours ago
















          I added some information. I tried to install Windows 10 but failed with error : no device drivers were found

          – BDR
          yesterday





          I added some information. I tried to install Windows 10 but failed with error : no device drivers were found

          – BDR
          yesterday













          Ok forget windows. Can you try to compile this driver? github.com/astyonax/patched-RTS5227-5229

          – alecxs
          13 hours ago





          Ok forget windows. Can you try to compile this driver? github.com/astyonax/patched-RTS5227-5229

          – alecxs
          13 hours ago

















          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%2f511194%2fdebian-microsd-lost-async-page-write%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







          Popular posts from this blog

          getting Checkpoint VPN SSL Network Extender working in the command lineHow to connect to CheckPoint VPN on Ubuntu 18.04LTS?Will the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayVPN SSL Network Extender in FirefoxLinux Checkpoint SNX tool configuration issuesCheck Point - Connect under Linux - snx + OTPSNX VPN Ububuntu 18.XXUsing Checkpoint VPN SSL Network Extender CLI with certificateVPN with network manager (nm-applet) is not workingWill the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayImport VPN config files to NetworkManager from command lineTrouble connecting to VPN using network-manager, while command line worksStart a VPN connection with PPTP protocol on command linestarting a docker service daemon breaks the vpn networkCan't connect to vpn with Network-managerVPN SSL Network Extender in FirefoxUsing Checkpoint VPN SSL Network Extender CLI with certificate

          Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition

          Marilyn Monroe Ny fiainany manokana | Jereo koa | Meny fitetezanafanitarana azy.