Can I prevent an IDENTIFY PACKET DEVICE command to a specific device at boot?












5















This is related to a previous question related to installation that is now resolved. I'm opening a new question, because I still need to get my DVD drive working.



Problem:



Failed boot when my ASUS DRW-24B1/ST DVD drive is attached to my asmedia ASM1061.



Symptom:



ata8.00: exception Emask 0x52 Sact 0x0 SErr 0xffffffff action 0xe frozen
ata8: SError: { blah blah }
ata8.00: failed command: IDENTIFY PACKET DEVICE
ata8.00: cmd blah blah
res blah blah (ATA bus error)
ata8.00: status: { DRDY }
ata8: hard resetting link


Background:



The ASM1061 is a PCIe to SATA bridge providing 2 x 6Gb/s ports and is supposed to be fully compliant to SATA specs.



I just discovered in the fine print of my ASUS P8Z77-V pro motherboard that "These SATA ports are for data hard drivers only. ATAPI devices are not supported."



However, I have already installed Windows 7 using this drive and I can run the Ubuntu 12.04 installer from it as well. The only time I have a problem is during Ubuntu boot when it tries an IDENTIFY PACKET DEVICE which seems to be an ATAPI command.



I can't simply switch this device to another SATA port because they are already allocated to other devices. (My chipset's 2 x 6Gb/s are connected to my boot SSD and a fast HDD while the 4 x 3Gb/s ports are running a RAID 5 array.) If this can't be fixed or worked around, I suppose I'll have to go buy SATA add-in card. Blech.



Thoughts:



If indeed this is a device specific issue (that it doesn't support ATAPI discovery) then I can't expect - is it udev? - to work with it. But, it seems that Windows and even the Ubuntu installer work just fine. So why does udev have a problem?



At the end of the day, it would be nice to have the DVD working under Ubuntu, but I can live without it. But, as this is a dual-boot machine, I can't physically disconnect it because I want it to work with Windows. (And physically disconnecting it every time I want to boot Ubuntu is NOT an option. ;-)



Questions:




  1. Should this be considered a bug? My feelings are that if it works with other OS that it should probably work with Ubuntu as well.


  2. How can I work around this problem? I have a limited knowledge of linux internals, but it seems I should be able to somehow tell udev (or whatever is doing the discovery) to ignore that device. Is there a way?











share|improve this question

























  • Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI. The solution is to edit the /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line. Thanks to Olli Helin for his answer to my previous post for this answer!

    – Brian Spisak
    Dec 24 '12 at 18:07











  • some related link I collected: - bugzilla.redhat.com/show_bug.cgi?id=906532 - bugs.debian.org/cgi-bin/bugreport.cgi?bug=701201 - linuxquestions.org/questions/… - forum.ubuntuusers.de/topic/… - forums.debian.net/viewtopic.php?p=605475 - forums.tweaktown.com/asrock/…

    – kolAflash
    5 hours ago
















5















This is related to a previous question related to installation that is now resolved. I'm opening a new question, because I still need to get my DVD drive working.



Problem:



Failed boot when my ASUS DRW-24B1/ST DVD drive is attached to my asmedia ASM1061.



Symptom:



ata8.00: exception Emask 0x52 Sact 0x0 SErr 0xffffffff action 0xe frozen
ata8: SError: { blah blah }
ata8.00: failed command: IDENTIFY PACKET DEVICE
ata8.00: cmd blah blah
res blah blah (ATA bus error)
ata8.00: status: { DRDY }
ata8: hard resetting link


Background:



The ASM1061 is a PCIe to SATA bridge providing 2 x 6Gb/s ports and is supposed to be fully compliant to SATA specs.



I just discovered in the fine print of my ASUS P8Z77-V pro motherboard that "These SATA ports are for data hard drivers only. ATAPI devices are not supported."



However, I have already installed Windows 7 using this drive and I can run the Ubuntu 12.04 installer from it as well. The only time I have a problem is during Ubuntu boot when it tries an IDENTIFY PACKET DEVICE which seems to be an ATAPI command.



I can't simply switch this device to another SATA port because they are already allocated to other devices. (My chipset's 2 x 6Gb/s are connected to my boot SSD and a fast HDD while the 4 x 3Gb/s ports are running a RAID 5 array.) If this can't be fixed or worked around, I suppose I'll have to go buy SATA add-in card. Blech.



Thoughts:



If indeed this is a device specific issue (that it doesn't support ATAPI discovery) then I can't expect - is it udev? - to work with it. But, it seems that Windows and even the Ubuntu installer work just fine. So why does udev have a problem?



At the end of the day, it would be nice to have the DVD working under Ubuntu, but I can live without it. But, as this is a dual-boot machine, I can't physically disconnect it because I want it to work with Windows. (And physically disconnecting it every time I want to boot Ubuntu is NOT an option. ;-)



Questions:




  1. Should this be considered a bug? My feelings are that if it works with other OS that it should probably work with Ubuntu as well.


  2. How can I work around this problem? I have a limited knowledge of linux internals, but it seems I should be able to somehow tell udev (or whatever is doing the discovery) to ignore that device. Is there a way?











share|improve this question

























  • Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI. The solution is to edit the /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line. Thanks to Olli Helin for his answer to my previous post for this answer!

    – Brian Spisak
    Dec 24 '12 at 18:07











  • some related link I collected: - bugzilla.redhat.com/show_bug.cgi?id=906532 - bugs.debian.org/cgi-bin/bugreport.cgi?bug=701201 - linuxquestions.org/questions/… - forum.ubuntuusers.de/topic/… - forums.debian.net/viewtopic.php?p=605475 - forums.tweaktown.com/asrock/…

    – kolAflash
    5 hours ago














5












5








5








This is related to a previous question related to installation that is now resolved. I'm opening a new question, because I still need to get my DVD drive working.



Problem:



Failed boot when my ASUS DRW-24B1/ST DVD drive is attached to my asmedia ASM1061.



Symptom:



ata8.00: exception Emask 0x52 Sact 0x0 SErr 0xffffffff action 0xe frozen
ata8: SError: { blah blah }
ata8.00: failed command: IDENTIFY PACKET DEVICE
ata8.00: cmd blah blah
res blah blah (ATA bus error)
ata8.00: status: { DRDY }
ata8: hard resetting link


Background:



The ASM1061 is a PCIe to SATA bridge providing 2 x 6Gb/s ports and is supposed to be fully compliant to SATA specs.



I just discovered in the fine print of my ASUS P8Z77-V pro motherboard that "These SATA ports are for data hard drivers only. ATAPI devices are not supported."



However, I have already installed Windows 7 using this drive and I can run the Ubuntu 12.04 installer from it as well. The only time I have a problem is during Ubuntu boot when it tries an IDENTIFY PACKET DEVICE which seems to be an ATAPI command.



I can't simply switch this device to another SATA port because they are already allocated to other devices. (My chipset's 2 x 6Gb/s are connected to my boot SSD and a fast HDD while the 4 x 3Gb/s ports are running a RAID 5 array.) If this can't be fixed or worked around, I suppose I'll have to go buy SATA add-in card. Blech.



Thoughts:



If indeed this is a device specific issue (that it doesn't support ATAPI discovery) then I can't expect - is it udev? - to work with it. But, it seems that Windows and even the Ubuntu installer work just fine. So why does udev have a problem?



At the end of the day, it would be nice to have the DVD working under Ubuntu, but I can live without it. But, as this is a dual-boot machine, I can't physically disconnect it because I want it to work with Windows. (And physically disconnecting it every time I want to boot Ubuntu is NOT an option. ;-)



Questions:




  1. Should this be considered a bug? My feelings are that if it works with other OS that it should probably work with Ubuntu as well.


  2. How can I work around this problem? I have a limited knowledge of linux internals, but it seems I should be able to somehow tell udev (or whatever is doing the discovery) to ignore that device. Is there a way?











share|improve this question
















This is related to a previous question related to installation that is now resolved. I'm opening a new question, because I still need to get my DVD drive working.



Problem:



Failed boot when my ASUS DRW-24B1/ST DVD drive is attached to my asmedia ASM1061.



Symptom:



ata8.00: exception Emask 0x52 Sact 0x0 SErr 0xffffffff action 0xe frozen
ata8: SError: { blah blah }
ata8.00: failed command: IDENTIFY PACKET DEVICE
ata8.00: cmd blah blah
res blah blah (ATA bus error)
ata8.00: status: { DRDY }
ata8: hard resetting link


Background:



The ASM1061 is a PCIe to SATA bridge providing 2 x 6Gb/s ports and is supposed to be fully compliant to SATA specs.



I just discovered in the fine print of my ASUS P8Z77-V pro motherboard that "These SATA ports are for data hard drivers only. ATAPI devices are not supported."



However, I have already installed Windows 7 using this drive and I can run the Ubuntu 12.04 installer from it as well. The only time I have a problem is during Ubuntu boot when it tries an IDENTIFY PACKET DEVICE which seems to be an ATAPI command.



I can't simply switch this device to another SATA port because they are already allocated to other devices. (My chipset's 2 x 6Gb/s are connected to my boot SSD and a fast HDD while the 4 x 3Gb/s ports are running a RAID 5 array.) If this can't be fixed or worked around, I suppose I'll have to go buy SATA add-in card. Blech.



Thoughts:



If indeed this is a device specific issue (that it doesn't support ATAPI discovery) then I can't expect - is it udev? - to work with it. But, it seems that Windows and even the Ubuntu installer work just fine. So why does udev have a problem?



At the end of the day, it would be nice to have the DVD working under Ubuntu, but I can live without it. But, as this is a dual-boot machine, I can't physically disconnect it because I want it to work with Windows. (And physically disconnecting it every time I want to boot Ubuntu is NOT an option. ;-)



Questions:




  1. Should this be considered a bug? My feelings are that if it works with other OS that it should probably work with Ubuntu as well.


  2. How can I work around this problem? I have a limited knowledge of linux internals, but it seems I should be able to somehow tell udev (or whatever is doing the discovery) to ignore that device. Is there a way?








12.04 boot-failure udev sata






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 13 '17 at 12:24









Community

1




1










asked Dec 18 '12 at 21:34









Brian SpisakBrian Spisak

138127




138127













  • Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI. The solution is to edit the /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line. Thanks to Olli Helin for his answer to my previous post for this answer!

    – Brian Spisak
    Dec 24 '12 at 18:07











  • some related link I collected: - bugzilla.redhat.com/show_bug.cgi?id=906532 - bugs.debian.org/cgi-bin/bugreport.cgi?bug=701201 - linuxquestions.org/questions/… - forum.ubuntuusers.de/topic/… - forums.debian.net/viewtopic.php?p=605475 - forums.tweaktown.com/asrock/…

    – kolAflash
    5 hours ago



















  • Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI. The solution is to edit the /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line. Thanks to Olli Helin for his answer to my previous post for this answer!

    – Brian Spisak
    Dec 24 '12 at 18:07











  • some related link I collected: - bugzilla.redhat.com/show_bug.cgi?id=906532 - bugs.debian.org/cgi-bin/bugreport.cgi?bug=701201 - linuxquestions.org/questions/… - forum.ubuntuusers.de/topic/… - forums.debian.net/viewtopic.php?p=605475 - forums.tweaktown.com/asrock/…

    – kolAflash
    5 hours ago

















Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI. The solution is to edit the /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line. Thanks to Olli Helin for his answer to my previous post for this answer!

– Brian Spisak
Dec 24 '12 at 18:07





Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI. The solution is to edit the /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line. Thanks to Olli Helin for his answer to my previous post for this answer!

– Brian Spisak
Dec 24 '12 at 18:07













some related link I collected: - bugzilla.redhat.com/show_bug.cgi?id=906532 - bugs.debian.org/cgi-bin/bugreport.cgi?bug=701201 - linuxquestions.org/questions/… - forum.ubuntuusers.de/topic/… - forums.debian.net/viewtopic.php?p=605475 - forums.tweaktown.com/asrock/…

– kolAflash
5 hours ago





some related link I collected: - bugzilla.redhat.com/show_bug.cgi?id=906532 - bugs.debian.org/cgi-bin/bugreport.cgi?bug=701201 - linuxquestions.org/questions/… - forum.ubuntuusers.de/topic/… - forums.debian.net/viewtopic.php?p=605475 - forums.tweaktown.com/asrock/…

– kolAflash
5 hours ago










2 Answers
2






active

oldest

votes


















4














Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI.



The solution is to edit /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line.



Thanks to Olli Helin for his answer to my previous post for this answer!






share|improve this answer































    1














    Apparently, ASM106x and optical drives just don't go together. It works - most of the time. But then bam! the entire machine crashes, and this was the last message on screen:



    ata10.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
    ata10: SError: { RecovData REcovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
    ata10.00: failed command: IDENTIFY PACKET DEVICE
    ata10.00: cmd a1/00:01:00:00:00/00:00:00:00:00/0 tag 0 pio 512 in
    res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x56 (ATA bus error)
    ata10.00: status: { DRDY }
    ata10: hard resetting link


    The issue also was discussed on the linux-ide mailing list: http://thread.gmane.org/gmane.linux.ide/55284



    Another workaround mentioned there is libata.atapi_passthru16=0 (kernel parameter).



    But in the end it seems to be a buggy SATA controller and you should avoid using it for optical drives altogether. Use a SATA port backed by another controller, or an USB adapter.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      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: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      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%2faskubuntu.com%2fquestions%2f230396%2fcan-i-prevent-an-identify-packet-device-command-to-a-specific-device-at-boot%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









      4














      Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI.



      The solution is to edit /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line.



      Thanks to Olli Helin for his answer to my previous post for this answer!






      share|improve this answer




























        4














        Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI.



        The solution is to edit /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line.



        Thanks to Olli Helin for his answer to my previous post for this answer!






        share|improve this answer


























          4












          4








          4







          Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI.



          The solution is to edit /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line.



          Thanks to Olli Helin for his answer to my previous post for this answer!






          share|improve this answer













          Turns out these are libata messages from the kernel resulting from ATAPI commands being sent to the DVD drive. The problem is, the ASM1061 to which the DVD is attached doesn't support ATAPI.



          The solution is to edit /lib/udev/rules.d/60-persistent-storage.rules, find the line containing the word "ATAPI" and comment out the next line.



          Thanks to Olli Helin for his answer to my previous post for this answer!







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 24 '12 at 18:08









          Brian SpisakBrian Spisak

          138127




          138127

























              1














              Apparently, ASM106x and optical drives just don't go together. It works - most of the time. But then bam! the entire machine crashes, and this was the last message on screen:



              ata10.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
              ata10: SError: { RecovData REcovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
              ata10.00: failed command: IDENTIFY PACKET DEVICE
              ata10.00: cmd a1/00:01:00:00:00/00:00:00:00:00/0 tag 0 pio 512 in
              res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x56 (ATA bus error)
              ata10.00: status: { DRDY }
              ata10: hard resetting link


              The issue also was discussed on the linux-ide mailing list: http://thread.gmane.org/gmane.linux.ide/55284



              Another workaround mentioned there is libata.atapi_passthru16=0 (kernel parameter).



              But in the end it seems to be a buggy SATA controller and you should avoid using it for optical drives altogether. Use a SATA port backed by another controller, or an USB adapter.






              share|improve this answer




























                1














                Apparently, ASM106x and optical drives just don't go together. It works - most of the time. But then bam! the entire machine crashes, and this was the last message on screen:



                ata10.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
                ata10: SError: { RecovData REcovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
                ata10.00: failed command: IDENTIFY PACKET DEVICE
                ata10.00: cmd a1/00:01:00:00:00/00:00:00:00:00/0 tag 0 pio 512 in
                res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x56 (ATA bus error)
                ata10.00: status: { DRDY }
                ata10: hard resetting link


                The issue also was discussed on the linux-ide mailing list: http://thread.gmane.org/gmane.linux.ide/55284



                Another workaround mentioned there is libata.atapi_passthru16=0 (kernel parameter).



                But in the end it seems to be a buggy SATA controller and you should avoid using it for optical drives altogether. Use a SATA port backed by another controller, or an USB adapter.






                share|improve this answer


























                  1












                  1








                  1







                  Apparently, ASM106x and optical drives just don't go together. It works - most of the time. But then bam! the entire machine crashes, and this was the last message on screen:



                  ata10.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
                  ata10: SError: { RecovData REcovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
                  ata10.00: failed command: IDENTIFY PACKET DEVICE
                  ata10.00: cmd a1/00:01:00:00:00/00:00:00:00:00/0 tag 0 pio 512 in
                  res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x56 (ATA bus error)
                  ata10.00: status: { DRDY }
                  ata10: hard resetting link


                  The issue also was discussed on the linux-ide mailing list: http://thread.gmane.org/gmane.linux.ide/55284



                  Another workaround mentioned there is libata.atapi_passthru16=0 (kernel parameter).



                  But in the end it seems to be a buggy SATA controller and you should avoid using it for optical drives altogether. Use a SATA port backed by another controller, or an USB adapter.






                  share|improve this answer













                  Apparently, ASM106x and optical drives just don't go together. It works - most of the time. But then bam! the entire machine crashes, and this was the last message on screen:



                  ata10.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
                  ata10: SError: { RecovData REcovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
                  ata10.00: failed command: IDENTIFY PACKET DEVICE
                  ata10.00: cmd a1/00:01:00:00:00/00:00:00:00:00/0 tag 0 pio 512 in
                  res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x56 (ATA bus error)
                  ata10.00: status: { DRDY }
                  ata10: hard resetting link


                  The issue also was discussed on the linux-ide mailing list: http://thread.gmane.org/gmane.linux.ide/55284



                  Another workaround mentioned there is libata.atapi_passthru16=0 (kernel parameter).



                  But in the end it seems to be a buggy SATA controller and you should avoid using it for optical drives altogether. Use a SATA port backed by another controller, or an USB adapter.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Apr 29 '14 at 17:03









                  frostschutzfrostschutz

                  664511




                  664511






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • 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%2faskubuntu.com%2fquestions%2f230396%2fcan-i-prevent-an-identify-packet-device-command-to-a-specific-device-at-boot%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

                      數位音樂下載

                      When can things happen in Etherscan, such as the picture below?

                      格利澤436b