I have downloaded the full Mageia 8 iso by BitTorrent. Neither Etcher
nor isodumper is able to write it to a USB stick successfully. I
checked the download and tried to use a .torrent file from Distrowatch.
Both said that the download had no problems. The report from Isodumper
was a bit more informative. It said that the checksum in the ISO was defective and unreadable. In these circumstances, the BitTorrent
protocol should ensure that the download is O.K.
I have downloaded the full Mageia 8 iso by BitTorrent. Neither Etcher
nor isodumper is able to write it to a USB stick successfully. I
checked the download and tried to use a .torrent file from Distrowatch.
Both said that the download had no problems. The report from Isodumper
was a bit more informative. It said that the checksum in the ISO was defective and unreadable. In these circumstances, the BitTorrent
protocol should ensure that the download is O.K.
I always do a checksum on the download and burn.
Saves me from creating coasters and wasting time on a bad
burn/xfer to cd or usb.
Using isodumper, it will check the sha3 sum of the copy from the usb
stick after
copying it, not the copy on disk. If the on disk copy is ok and the on
usb stick
copy is not, then the copy failed, likely due to a bad usb stick.
On 16/1/22 00:04, Bit Twister wrote:
I always do a checksum on the download and burn.A fair comment, but the checksum you need is that of the CD you burned.
Saves me from creating coasters and wasting time on a bad
burn/xfer to cd or usb.
In my experience, that checksum never matches the one from the
download. k3b derives its own checksum before the burn. and the two iso-dumpers would have done the same. Apparently, after the burn, the checksum could not be read to compare. The burn might still be good.
On 16/1/22 00:04, Bit Twister wrote:
I always do a checksum on the download and burn.A fair comment, but the checksum you need is that of the CD you burned.
Saves me from creating coasters and wasting time on a bad
burn/xfer to cd or usb.
In my experience, that checksum never matches the one from the
download. k3b derives its own checksum before the burn. and the two iso-dumpers would have done the same. Apparently, after the burn, the checksum could not be read to compare. The burn might still be good.
On 16/1/22 09:05, David W. Hodgins wrote:
Using isodumper, it will check the sha3 sum of the copy from the usb
stick after
copying it, not the copy on disk. If the on disk copy is ok and the on
usb stick
copy is not, then the copy failed, likely due to a bad usb stick.
What I downloaded was set by the .torrent file. It included checksums
for MD5, sha3 and sha512, with gpg files for them all, including the iso itself.
I burned the iso to 2 different USB sticks, the USB2 one I used
originally and a fairly new Lexar USB3 one. Both burns failed.
I burned the iso to 2 different USB sticks, the USB2 one I used
originally and a fairly new Lexar USB3 one. Both burns failed.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 39:56:38 |
Calls: | 6,648 |
Files: | 12,193 |
Messages: | 5,329,408 |