Ubuntu error “Gave up waiting for root device” on 9.10 Netbook Remix












0















So I installed Ubuntu Netbook Remix 9.10 onto my Asus EeePC 1008HA netbook.



It worked perfectly and was pretty quick. Restarting, suspending and hibernating worked just fine but the very first time I shut it down, I can no longer boot back into Ubuntu.



I created 3 partitions.
/
/home
swap



All using the default filesystem (I'm still new but, I believe, it was EXT4?).



Anyway, now I only get this error stating "Gave up waiting for root device" when I attempt to boot.



I've tried typing in "exit" at the initramfs prompt as suggestions but it never works.



So I booted off of the USB stick I used to install and I took a look at my partitions. My boot partition now says "unknown" instead of the filesystem I used. So I used fsck on it which seemed to do something (it asked about future dates which it fixed). Then I attempted to use e2fsck but I always get the error "Invalid non-numeric argument to -P ("/dev/sda1")".



What can I do to attempt to resolve this? It's such a shame because everything worked perfectly and I had no problems with multiple restarts, hibernates and suspends but the first time I shut it down this starts happening. I didn't even hold the power button.










share|improve this question















migrated from stackoverflow.com Jan 1 '10 at 20:29


This question came from our site for professional and enthusiast programmers.























    0















    So I installed Ubuntu Netbook Remix 9.10 onto my Asus EeePC 1008HA netbook.



    It worked perfectly and was pretty quick. Restarting, suspending and hibernating worked just fine but the very first time I shut it down, I can no longer boot back into Ubuntu.



    I created 3 partitions.
    /
    /home
    swap



    All using the default filesystem (I'm still new but, I believe, it was EXT4?).



    Anyway, now I only get this error stating "Gave up waiting for root device" when I attempt to boot.



    I've tried typing in "exit" at the initramfs prompt as suggestions but it never works.



    So I booted off of the USB stick I used to install and I took a look at my partitions. My boot partition now says "unknown" instead of the filesystem I used. So I used fsck on it which seemed to do something (it asked about future dates which it fixed). Then I attempted to use e2fsck but I always get the error "Invalid non-numeric argument to -P ("/dev/sda1")".



    What can I do to attempt to resolve this? It's such a shame because everything worked perfectly and I had no problems with multiple restarts, hibernates and suspends but the first time I shut it down this starts happening. I didn't even hold the power button.










    share|improve this question















    migrated from stackoverflow.com Jan 1 '10 at 20:29


    This question came from our site for professional and enthusiast programmers.





















      0












      0








      0








      So I installed Ubuntu Netbook Remix 9.10 onto my Asus EeePC 1008HA netbook.



      It worked perfectly and was pretty quick. Restarting, suspending and hibernating worked just fine but the very first time I shut it down, I can no longer boot back into Ubuntu.



      I created 3 partitions.
      /
      /home
      swap



      All using the default filesystem (I'm still new but, I believe, it was EXT4?).



      Anyway, now I only get this error stating "Gave up waiting for root device" when I attempt to boot.



      I've tried typing in "exit" at the initramfs prompt as suggestions but it never works.



      So I booted off of the USB stick I used to install and I took a look at my partitions. My boot partition now says "unknown" instead of the filesystem I used. So I used fsck on it which seemed to do something (it asked about future dates which it fixed). Then I attempted to use e2fsck but I always get the error "Invalid non-numeric argument to -P ("/dev/sda1")".



      What can I do to attempt to resolve this? It's such a shame because everything worked perfectly and I had no problems with multiple restarts, hibernates and suspends but the first time I shut it down this starts happening. I didn't even hold the power button.










      share|improve this question
















      So I installed Ubuntu Netbook Remix 9.10 onto my Asus EeePC 1008HA netbook.



      It worked perfectly and was pretty quick. Restarting, suspending and hibernating worked just fine but the very first time I shut it down, I can no longer boot back into Ubuntu.



      I created 3 partitions.
      /
      /home
      swap



      All using the default filesystem (I'm still new but, I believe, it was EXT4?).



      Anyway, now I only get this error stating "Gave up waiting for root device" when I attempt to boot.



      I've tried typing in "exit" at the initramfs prompt as suggestions but it never works.



      So I booted off of the USB stick I used to install and I took a look at my partitions. My boot partition now says "unknown" instead of the filesystem I used. So I used fsck on it which seemed to do something (it asked about future dates which it fixed). Then I attempted to use e2fsck but I always get the error "Invalid non-numeric argument to -P ("/dev/sda1")".



      What can I do to attempt to resolve this? It's such a shame because everything worked perfectly and I had no problems with multiple restarts, hibernates and suspends but the first time I shut it down this starts happening. I didn't even hold the power button.







      linux ubuntu boot root






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jul 21 '14 at 14:05









      Cfinley

      1,43331120




      1,43331120










      asked Jan 1 '10 at 20:20









      KrisKris

      11817




      11817




      migrated from stackoverflow.com Jan 1 '10 at 20:29


      This question came from our site for professional and enthusiast programmers.









      migrated from stackoverflow.com Jan 1 '10 at 20:29


      This question came from our site for professional and enthusiast programmers.
























          4 Answers
          4






          active

          oldest

          votes


















          1














          If you ran fsck that would have called e2fsck for you.



          it sounds like something might have hosed the filesystem UUID which makes the initrd unable to locate your root partition.



          try hitting e in grub and changing the root=UUID=..... to just root=/dev/sda1



          if that works you just need to set the UUID back to what your system expects..



          tune2fs /dev/sda1 -U xxxxxxxxxx


          you can see what the UUID was previously by looking in /etc/fstab or /boot/grub/menu.lst






          share|improve this answer































            1














            Try this,
            Zee's 6 step Ubuntu fix!
            http://zeeis.me/ubuntu-boot-error-si...r-root-device/



            (This is not my contribution so as the site says please mention a linkback as credit If you wish to share it with anyone or post it on your website)






            share|improve this answer































              0














              I was able to boot by changing the root=UUID=... to root=/dev/sda1. after looking at /etc/fstab the UUID is the same as the one displayed on the shell when the system failed to boot






              share|improve this answer































                0














                I think it's quite similar to this (Deleted a partition, now getting 'Gave up waiting for suspend/resume device' message during boot).



                I gave the answer below as it worked for me.



                In my case, the boot message looked like this. The swap partition was deleted.



                Gave up waiting for suspend/resume device
                /dev/sda4 ... ...

                [***] A start job is running for dev-disk-by..........device
                ...
                ...
                ...


                First, look at the content of your fstab file,

                cat /etc/fstab

                will return this kind of output



                # /etc/fstab: static file system information.
                #
                # Use 'blkid' to print the universally unique identifier for a
                # device; this may be used with UUID= as a more robust way to name devices
                # that works even if disks are added and removed. See fstab(5).
                #
                # <file system> <mount point> <type> <options> <dump> <pass>
                # / was on /dev/sda4 during installation
                UUID=8c1977eb-ac90-426b-bc9b-a7fb2ec8d760 / ext4 errors=remount-ro 0 1
                # swap was on /dev/sda3 during installation
                UUID=00fd67-123DE-4b98-aa17-2d4025aed54 none swap sw 0 0
                /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0


                Then you notice , "swap was on /dev/sdax during installation".



                Recreate the deleted partition (fdisk or Gparted for instance), then
                use this command to find the new uuid of the partition.



                ls -l /dev/disk/by-uuid/


                This outputs:



                total 0
                lrwxrwxrwx 1 root root 10 févr. 19 07:18 00151dcd-2bf5-4b98-aa17-8f40ef4cfd86 -> ../../sda4
                lrwxrwxrwx 1 root root 10 févr. 19 07:18 6C5A1AC45A1A8B4A -> ../../sda2
                lrwxrwxrwx 1 root root 10 févr. 19 07:18 8c1977eb-ac90-426b-bc9b-a7fb2ec8d760 -> ../../sda3
                lrwxrwxrwx 1 root root 10 févr. 19 07:18 C064106664106188 -> ../../sda1


                Update your fstab with the correct uuid that were displayed by the last command by copy/pasting the adequate uuid of the swap in the fstab file.
                Then reboot, It should correct the problem.






                share|improve this answer























                  Your Answer








                  StackExchange.ready(function() {
                  var channelOptions = {
                  tags: "".split(" "),
                  id: "3"
                  };
                  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%2fsuperuser.com%2fquestions%2f90200%2fubuntu-error-gave-up-waiting-for-root-device-on-9-10-netbook-remix%23new-answer', 'question_page');
                  }
                  );

                  Post as a guest















                  Required, but never shown

























                  4 Answers
                  4






                  active

                  oldest

                  votes








                  4 Answers
                  4






                  active

                  oldest

                  votes









                  active

                  oldest

                  votes






                  active

                  oldest

                  votes









                  1














                  If you ran fsck that would have called e2fsck for you.



                  it sounds like something might have hosed the filesystem UUID which makes the initrd unable to locate your root partition.



                  try hitting e in grub and changing the root=UUID=..... to just root=/dev/sda1



                  if that works you just need to set the UUID back to what your system expects..



                  tune2fs /dev/sda1 -U xxxxxxxxxx


                  you can see what the UUID was previously by looking in /etc/fstab or /boot/grub/menu.lst






                  share|improve this answer




























                    1














                    If you ran fsck that would have called e2fsck for you.



                    it sounds like something might have hosed the filesystem UUID which makes the initrd unable to locate your root partition.



                    try hitting e in grub and changing the root=UUID=..... to just root=/dev/sda1



                    if that works you just need to set the UUID back to what your system expects..



                    tune2fs /dev/sda1 -U xxxxxxxxxx


                    you can see what the UUID was previously by looking in /etc/fstab or /boot/grub/menu.lst






                    share|improve this answer


























                      1












                      1








                      1







                      If you ran fsck that would have called e2fsck for you.



                      it sounds like something might have hosed the filesystem UUID which makes the initrd unable to locate your root partition.



                      try hitting e in grub and changing the root=UUID=..... to just root=/dev/sda1



                      if that works you just need to set the UUID back to what your system expects..



                      tune2fs /dev/sda1 -U xxxxxxxxxx


                      you can see what the UUID was previously by looking in /etc/fstab or /boot/grub/menu.lst






                      share|improve this answer













                      If you ran fsck that would have called e2fsck for you.



                      it sounds like something might have hosed the filesystem UUID which makes the initrd unable to locate your root partition.



                      try hitting e in grub and changing the root=UUID=..... to just root=/dev/sda1



                      if that works you just need to set the UUID back to what your system expects..



                      tune2fs /dev/sda1 -U xxxxxxxxxx


                      you can see what the UUID was previously by looking in /etc/fstab or /boot/grub/menu.lst







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Jan 1 '10 at 23:56









                      user23307user23307

                      5,51511412




                      5,51511412

























                          1














                          Try this,
                          Zee's 6 step Ubuntu fix!
                          http://zeeis.me/ubuntu-boot-error-si...r-root-device/



                          (This is not my contribution so as the site says please mention a linkback as credit If you wish to share it with anyone or post it on your website)






                          share|improve this answer




























                            1














                            Try this,
                            Zee's 6 step Ubuntu fix!
                            http://zeeis.me/ubuntu-boot-error-si...r-root-device/



                            (This is not my contribution so as the site says please mention a linkback as credit If you wish to share it with anyone or post it on your website)






                            share|improve this answer


























                              1












                              1








                              1







                              Try this,
                              Zee's 6 step Ubuntu fix!
                              http://zeeis.me/ubuntu-boot-error-si...r-root-device/



                              (This is not my contribution so as the site says please mention a linkback as credit If you wish to share it with anyone or post it on your website)






                              share|improve this answer













                              Try this,
                              Zee's 6 step Ubuntu fix!
                              http://zeeis.me/ubuntu-boot-error-si...r-root-device/



                              (This is not my contribution so as the site says please mention a linkback as credit If you wish to share it with anyone or post it on your website)







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Sep 28 '10 at 19:25









                              rickyricky

                              111




                              111























                                  0














                                  I was able to boot by changing the root=UUID=... to root=/dev/sda1. after looking at /etc/fstab the UUID is the same as the one displayed on the shell when the system failed to boot






                                  share|improve this answer




























                                    0














                                    I was able to boot by changing the root=UUID=... to root=/dev/sda1. after looking at /etc/fstab the UUID is the same as the one displayed on the shell when the system failed to boot






                                    share|improve this answer


























                                      0












                                      0








                                      0







                                      I was able to boot by changing the root=UUID=... to root=/dev/sda1. after looking at /etc/fstab the UUID is the same as the one displayed on the shell when the system failed to boot






                                      share|improve this answer













                                      I was able to boot by changing the root=UUID=... to root=/dev/sda1. after looking at /etc/fstab the UUID is the same as the one displayed on the shell when the system failed to boot







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Jan 3 '10 at 14:02







                                      Flamoxed






























                                          0














                                          I think it's quite similar to this (Deleted a partition, now getting 'Gave up waiting for suspend/resume device' message during boot).



                                          I gave the answer below as it worked for me.



                                          In my case, the boot message looked like this. The swap partition was deleted.



                                          Gave up waiting for suspend/resume device
                                          /dev/sda4 ... ...

                                          [***] A start job is running for dev-disk-by..........device
                                          ...
                                          ...
                                          ...


                                          First, look at the content of your fstab file,

                                          cat /etc/fstab

                                          will return this kind of output



                                          # /etc/fstab: static file system information.
                                          #
                                          # Use 'blkid' to print the universally unique identifier for a
                                          # device; this may be used with UUID= as a more robust way to name devices
                                          # that works even if disks are added and removed. See fstab(5).
                                          #
                                          # <file system> <mount point> <type> <options> <dump> <pass>
                                          # / was on /dev/sda4 during installation
                                          UUID=8c1977eb-ac90-426b-bc9b-a7fb2ec8d760 / ext4 errors=remount-ro 0 1
                                          # swap was on /dev/sda3 during installation
                                          UUID=00fd67-123DE-4b98-aa17-2d4025aed54 none swap sw 0 0
                                          /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0


                                          Then you notice , "swap was on /dev/sdax during installation".



                                          Recreate the deleted partition (fdisk or Gparted for instance), then
                                          use this command to find the new uuid of the partition.



                                          ls -l /dev/disk/by-uuid/


                                          This outputs:



                                          total 0
                                          lrwxrwxrwx 1 root root 10 févr. 19 07:18 00151dcd-2bf5-4b98-aa17-8f40ef4cfd86 -> ../../sda4
                                          lrwxrwxrwx 1 root root 10 févr. 19 07:18 6C5A1AC45A1A8B4A -> ../../sda2
                                          lrwxrwxrwx 1 root root 10 févr. 19 07:18 8c1977eb-ac90-426b-bc9b-a7fb2ec8d760 -> ../../sda3
                                          lrwxrwxrwx 1 root root 10 févr. 19 07:18 C064106664106188 -> ../../sda1


                                          Update your fstab with the correct uuid that were displayed by the last command by copy/pasting the adequate uuid of the swap in the fstab file.
                                          Then reboot, It should correct the problem.






                                          share|improve this answer




























                                            0














                                            I think it's quite similar to this (Deleted a partition, now getting 'Gave up waiting for suspend/resume device' message during boot).



                                            I gave the answer below as it worked for me.



                                            In my case, the boot message looked like this. The swap partition was deleted.



                                            Gave up waiting for suspend/resume device
                                            /dev/sda4 ... ...

                                            [***] A start job is running for dev-disk-by..........device
                                            ...
                                            ...
                                            ...


                                            First, look at the content of your fstab file,

                                            cat /etc/fstab

                                            will return this kind of output



                                            # /etc/fstab: static file system information.
                                            #
                                            # Use 'blkid' to print the universally unique identifier for a
                                            # device; this may be used with UUID= as a more robust way to name devices
                                            # that works even if disks are added and removed. See fstab(5).
                                            #
                                            # <file system> <mount point> <type> <options> <dump> <pass>
                                            # / was on /dev/sda4 during installation
                                            UUID=8c1977eb-ac90-426b-bc9b-a7fb2ec8d760 / ext4 errors=remount-ro 0 1
                                            # swap was on /dev/sda3 during installation
                                            UUID=00fd67-123DE-4b98-aa17-2d4025aed54 none swap sw 0 0
                                            /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0


                                            Then you notice , "swap was on /dev/sdax during installation".



                                            Recreate the deleted partition (fdisk or Gparted for instance), then
                                            use this command to find the new uuid of the partition.



                                            ls -l /dev/disk/by-uuid/


                                            This outputs:



                                            total 0
                                            lrwxrwxrwx 1 root root 10 févr. 19 07:18 00151dcd-2bf5-4b98-aa17-8f40ef4cfd86 -> ../../sda4
                                            lrwxrwxrwx 1 root root 10 févr. 19 07:18 6C5A1AC45A1A8B4A -> ../../sda2
                                            lrwxrwxrwx 1 root root 10 févr. 19 07:18 8c1977eb-ac90-426b-bc9b-a7fb2ec8d760 -> ../../sda3
                                            lrwxrwxrwx 1 root root 10 févr. 19 07:18 C064106664106188 -> ../../sda1


                                            Update your fstab with the correct uuid that were displayed by the last command by copy/pasting the adequate uuid of the swap in the fstab file.
                                            Then reboot, It should correct the problem.






                                            share|improve this answer


























                                              0












                                              0








                                              0







                                              I think it's quite similar to this (Deleted a partition, now getting 'Gave up waiting for suspend/resume device' message during boot).



                                              I gave the answer below as it worked for me.



                                              In my case, the boot message looked like this. The swap partition was deleted.



                                              Gave up waiting for suspend/resume device
                                              /dev/sda4 ... ...

                                              [***] A start job is running for dev-disk-by..........device
                                              ...
                                              ...
                                              ...


                                              First, look at the content of your fstab file,

                                              cat /etc/fstab

                                              will return this kind of output



                                              # /etc/fstab: static file system information.
                                              #
                                              # Use 'blkid' to print the universally unique identifier for a
                                              # device; this may be used with UUID= as a more robust way to name devices
                                              # that works even if disks are added and removed. See fstab(5).
                                              #
                                              # <file system> <mount point> <type> <options> <dump> <pass>
                                              # / was on /dev/sda4 during installation
                                              UUID=8c1977eb-ac90-426b-bc9b-a7fb2ec8d760 / ext4 errors=remount-ro 0 1
                                              # swap was on /dev/sda3 during installation
                                              UUID=00fd67-123DE-4b98-aa17-2d4025aed54 none swap sw 0 0
                                              /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0


                                              Then you notice , "swap was on /dev/sdax during installation".



                                              Recreate the deleted partition (fdisk or Gparted for instance), then
                                              use this command to find the new uuid of the partition.



                                              ls -l /dev/disk/by-uuid/


                                              This outputs:



                                              total 0
                                              lrwxrwxrwx 1 root root 10 févr. 19 07:18 00151dcd-2bf5-4b98-aa17-8f40ef4cfd86 -> ../../sda4
                                              lrwxrwxrwx 1 root root 10 févr. 19 07:18 6C5A1AC45A1A8B4A -> ../../sda2
                                              lrwxrwxrwx 1 root root 10 févr. 19 07:18 8c1977eb-ac90-426b-bc9b-a7fb2ec8d760 -> ../../sda3
                                              lrwxrwxrwx 1 root root 10 févr. 19 07:18 C064106664106188 -> ../../sda1


                                              Update your fstab with the correct uuid that were displayed by the last command by copy/pasting the adequate uuid of the swap in the fstab file.
                                              Then reboot, It should correct the problem.






                                              share|improve this answer













                                              I think it's quite similar to this (Deleted a partition, now getting 'Gave up waiting for suspend/resume device' message during boot).



                                              I gave the answer below as it worked for me.



                                              In my case, the boot message looked like this. The swap partition was deleted.



                                              Gave up waiting for suspend/resume device
                                              /dev/sda4 ... ...

                                              [***] A start job is running for dev-disk-by..........device
                                              ...
                                              ...
                                              ...


                                              First, look at the content of your fstab file,

                                              cat /etc/fstab

                                              will return this kind of output



                                              # /etc/fstab: static file system information.
                                              #
                                              # Use 'blkid' to print the universally unique identifier for a
                                              # device; this may be used with UUID= as a more robust way to name devices
                                              # that works even if disks are added and removed. See fstab(5).
                                              #
                                              # <file system> <mount point> <type> <options> <dump> <pass>
                                              # / was on /dev/sda4 during installation
                                              UUID=8c1977eb-ac90-426b-bc9b-a7fb2ec8d760 / ext4 errors=remount-ro 0 1
                                              # swap was on /dev/sda3 during installation
                                              UUID=00fd67-123DE-4b98-aa17-2d4025aed54 none swap sw 0 0
                                              /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0


                                              Then you notice , "swap was on /dev/sdax during installation".



                                              Recreate the deleted partition (fdisk or Gparted for instance), then
                                              use this command to find the new uuid of the partition.



                                              ls -l /dev/disk/by-uuid/


                                              This outputs:



                                              total 0
                                              lrwxrwxrwx 1 root root 10 févr. 19 07:18 00151dcd-2bf5-4b98-aa17-8f40ef4cfd86 -> ../../sda4
                                              lrwxrwxrwx 1 root root 10 févr. 19 07:18 6C5A1AC45A1A8B4A -> ../../sda2
                                              lrwxrwxrwx 1 root root 10 févr. 19 07:18 8c1977eb-ac90-426b-bc9b-a7fb2ec8d760 -> ../../sda3
                                              lrwxrwxrwx 1 root root 10 févr. 19 07:18 C064106664106188 -> ../../sda1


                                              Update your fstab with the correct uuid that were displayed by the last command by copy/pasting the adequate uuid of the swap in the fstab file.
                                              Then reboot, It should correct the problem.







                                              share|improve this answer












                                              share|improve this answer



                                              share|improve this answer










                                              answered Feb 19 at 12:46









                                              Pat. ANDRIAPat. ANDRIA

                                              12




                                              12






























                                                  draft saved

                                                  draft discarded




















































                                                  Thanks for contributing an answer to Super User!


                                                  • 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%2fsuperuser.com%2fquestions%2f90200%2fubuntu-error-gave-up-waiting-for-root-device-on-9-10-netbook-remix%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

                                                  Probability when a professor distributes a quiz and homework assignment to a class of n students.

                                                  Aardman Animations

                                                  Are they similar matrix