I agree with Andrew Simpson. It's not clear that this is a duplicate of bug #445852.
I have the SSD in question, the SSDPAMM0008G1, with my Acer Aspire One. I first successfully installed UNR 9.04. I then tried to install UNR 9.10, and received hundreds of the errors noted above: DRDY ERR, UNC ABRT, and "media error." From what I can tell, I never received any HSM errors.
I probably tried about a half-dozen times to reinstall 9.10, always failing when it came to partitioning and formatting. I was convinced that my SSD was failing, and I was about to return my netbook to the seller (I just bought it used) and complain about a defective item.
Then, I tried a hint in the other bug about zeroing the disk with dd: dd if=/dev/zero of=/dev/sda bs=1M
After doing that, I reinstalled UNR 9.04, which went without a hitch. I have been using it for about two days since then, and I have not seen a single error like those above in my dmesg.
From my point of view, UNR 9.10 is unusable on this SSD because of this bug. I am also now terrified to upgrade to 9.10 through the package manager, or for that matter to upgrade the kernel or ATA drivers because I worry this bug will reappear. It is particularly nasty because people affected become convinced their SSD is faulty, when it is really not. Smartctl reports my drive has had less than 100 hours of power-on time.
I agree with Andrew Simpson. It's not clear that this is a duplicate of bug #445852.
I have the SSD in question, the SSDPAMM0008G1, with my Acer Aspire One. I first successfully installed UNR 9.04. I then tried to install UNR 9.10, and received hundreds of the errors noted above: DRDY ERR, UNC ABRT, and "media error." From what I can tell, I never received any HSM errors.
I probably tried about a half-dozen times to reinstall 9.10, always failing when it came to partitioning and formatting. I was convinced that my SSD was failing, and I was about to return my netbook to the seller (I just bought it used) and complain about a defective item.
Then, I tried a hint in the other bug about zeroing the disk with dd: dd if=/dev/zero of=/dev/sda bs=1M
After doing that, I reinstalled UNR 9.04, which went without a hitch. I have been using it for about two days since then, and I have not seen a single error like those above in my dmesg.
From my point of view, UNR 9.10 is unusable on this SSD because of this bug. I am also now terrified to upgrade to 9.10 through the package manager, or for that matter to upgrade the kernel or ATA drivers because I worry this bug will reappear. It is particularly nasty because people affected become convinced their SSD is faulty, when it is really not. Smartctl reports my drive has had less than 100 hours of power-on time.