[opensuse-factory] Before I can test Beta 2...
I would like to install and help test Beta 2. Unfortunately, before I can install it I'm running into a few problems... I downloaded the x86-64 DVD image via BitTorrent. Problem 1: http://download.opensuse.org/distribution/11.0-Beta2/iso/torrent/ doesn't have an MD5SUMS or SHA1SUMS file, so I don't know if these files are downloaded correctly. Problem 2: While the Beta1 directory *did* have a MD5SUMS file, the Beta1 MD5SUMS file only contained entries for the *.torrent files, NOT for the resulting .iso files. Consequently with Beta 1, after burning to disk and running Check Installation Media, it failed. The same has happened to me *twice* with Beta 2 -- Check Installation Media reports that there's an error reading sector 2081125. Now, this is likely a problem with either (a) my iso image, (b) my DVD writer, (c) the DVD writer program I'm using (nautilus-cd-burner), or (d) horribly bad luck. Unfortunately I can't verify (a) without an MD5SUM/SHA1SUM for my ISO image, which I don't have (courtesy problems 2/3), and I'd like to ensure that (a) isn't a problem before I further investigate (c). So... Could anyone provide me the MD5SUM or SHA1SUM for a working, valid, openSUSE-11.0-Beta2-DVD-x86_64.iso file? Thanks, - Jon --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 5/4/08, Jonathan Pryor
I would like to install and help test Beta 2. Unfortunately, before I can install it I'm running into a few problems...
I downloaded the x86-64 DVD image via BitTorrent. I also got my x86_64 DVD image through BitTorrent. Because there was no MD5SUM available, I ran a data integrity check after the image completed. Interestingly, KTorrent found a bad block which it re-downloaded subsequently.
So maybe the files get corrupted through the BitTorrent download. Has anyone an idea how frequently these bittorrent corruptions are? I don't know if KTorrent's integrity check can replace an MD5SUM file; anyhow it would be preferrable to have such a file on the download site.
So... Could anyone provide me the MD5SUM or SHA1SUM for a working, valid, openSUSE-11.0-Beta2-DVD-x86_64.iso file? My MD5sum is: 41391ca57bd2dda30d69ebb55752e84c openSUSE-11.0-Beta2-DVD-x86_64.iso
Cheers, Michael --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, El Sunday 04 May 2008 14:40:43 Michael Schmuker escribió:
My MD5sum is: 41391ca57bd2dda30d69ebb55752e84c openSUSE-11.0-Beta2-DVD-x86_64.iso
It looks good! :-) http://download.opensuse.org/distribution/11.0-Beta2/iso/delta/MD5SUMS.of.DV... Guillermo
Cheers,
Michael --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-- Guillermo Ballester Valor gbv@oxixares.com http://www.oxixares.com/~gbv Ogijares, Granada - SPAIN --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, El Sunday 04 May 2008 12:39:31 Jonathan Pryor escribió:
I would like to install and help test Beta 2. Unfortunately, before I can install it I'm running into a few problems...
I downloaded the x86-64 DVD image via BitTorrent.
Problem 1: http://download.opensuse.org/distribution/11.0-Beta2/iso/torrent/ doesn't have an MD5SUMS or SHA1SUMS file, so I don't know if these files are downloaded correctly.
Check the MD5sums for DVDs here: http://download.opensuse.org/distribution/11.0-Beta2/iso/delta/MD5SUMS.of.DV... These are: 90adec92cb7fa6d5be59041bb2c0ea42 openSUSE-11.0-Beta2-DVD-i386.iso 22b3b18678704546a8422bbc7b7245bd openSUSE-11.0-Beta2-DVD-ppc.iso 41391ca57bd2dda30d69ebb55752e84c openSUSE-11.0-Beta2-DVD-x86_64.iso Guillermo
Problem 2: While the Beta1 directory *did* have a MD5SUMS file, the Beta1 MD5SUMS file only contained entries for the *.torrent files, NOT for the resulting .iso files.
Consequently with Beta 1, after burning to disk and running Check Installation Media, it failed.
The same has happened to me *twice* with Beta 2 -- Check Installation Media reports that there's an error reading sector 2081125.
Now, this is likely a problem with either (a) my iso image, (b) my DVD writer, (c) the DVD writer program I'm using (nautilus-cd-burner), or (d) horribly bad luck.
Unfortunately I can't verify (a) without an MD5SUM/SHA1SUM for my ISO image, which I don't have (courtesy problems 2/3), and I'd like to ensure that (a) isn't a problem before I further investigate (c).
So... Could anyone provide me the MD5SUM or SHA1SUM for a working, valid, openSUSE-11.0-Beta2-DVD-x86_64.iso file?
Thanks, - Jon
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-- Guillermo Ballester Valor gbv@oxixares.com http://www.oxixares.com/~gbv Ogijares, Granada - SPAIN --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 04 May 2008 07:39:31 am Jonathan Pryor wrote:
I would like to install and help test Beta 2. Unfortunately, before I can install it I'm running into a few problems...
I downloaded the x86-64 DVD image via BitTorrent.
Problem 1: http://download.opensuse.org/distribution/11.0-Beta2/iso/torrent/ doesn't have an MD5SUMS or SHA1SUMS file, so I don't know if these files are downloaded correctly.
Problem 2: While the Beta1 directory *did* have a MD5SUMS file, the Beta1 MD5SUMS file only contained entries for the *.torrent files, NOT for the resulting .iso files.
Consequently with Beta 1, after burning to disk and running Check Installation Media, it failed.
The same has happened to me *twice* with Beta 2 -- Check Installation Media reports that there's an error reading sector 2081125.
Now, this is likely a problem with either (a) my iso image, (b) my DVD writer, (c) the DVD writer program I'm using (nautilus-cd-burner), or (d) horribly bad luck.
Unfortunately I can't verify (a) without an MD5SUM/SHA1SUM for my ISO image, which I don't have (courtesy problems 2/3), and I'd like to ensure that (a) isn't a problem before I further investigate (c).
So... Could anyone provide me the MD5SUM or SHA1SUM for a working, valid, openSUSE-11.0-Beta2-DVD-x86_64.iso file?
Thanks, - Jon
http://download.opensuse.org/distribution/11.0-Beta2/iso/delta/ MD5SUMS.of.DVDs is the same for download method. I checked media, on old computer that has problem reading DVD-RW and test passed. The same reader has no problem with original media like 10.3 DVD. When I burn CD/DVD I use speed much smaller than declared on burner or disk. That is what I didn't do with DVD-RW, but I'll reburn iso with 50% speed and see how it works then. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-05-04 at 08:39 -0400, Jonathan Pryor wrote:
I would like to install and help test Beta 2. Unfortunately, before I can install it I'm running into a few problems...
I downloaded the x86-64 DVD image via BitTorrent.
Problem 1: http://download.opensuse.org/distribution/11.0-Beta2/iso/torrent/ doesn't have an MD5SUMS or SHA1SUMS file, so I don't know if these files are downloaded correctly.
They are not needed. The .torrent file contain checksum information internally, so that when a chunk is downloaded incorrectly, it retries till it gets the chunk correct. That's why the .torrent file is big: it contains the checksums for all the chunks. Now, if KTorrent is unable to produce a perfect downloaded iso, and even more, unable to correct the possible errors, that's a bug of KTorrent. Don't use it. Use the plain "BitTorrent", for instance (btdownloadgui or btdownloadcurses), or probably azureus. I have sucesfully used btdownloadcurses to reconstruct bad downloads produced by KTorrent or ftp. Now, if after a download using a good client is finished, Yast says the image is wrong, that's a bug in yast. cer@nimrodel:~> btshowmetainfo openSUSE-11.0-Beta2-DVD-i386.torrent btshowmetainfo 20021207 - decode BitTorrent metainfo files metainfo file.: openSUSE-11.0-Beta2-DVD-i386.torrent info hash.....: 8ba2847cd9addc842af41eef355e224bd1ad808b directory name: openSUSE-11.0-Beta2-DVD-i386-iso files.........: openSUSE-11.0-Beta2-DVD-i386.iso (4582096896) archive size..: 4582096896 (17479 * 262144 + 81920) announce url..: http://tracker.opensuse.org:6969/announce - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIHgQKtTMYHG2NR9URApDgAJ0W0rg2mhOmltiqfYXu7vbjLbB1ggCdEgWW r0lJdvvpHHH6yUPEdT2f/DA= =wbx4 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, 2008-05-04 at 20:44 +0200, Carlos E. R. wrote:
The Sunday 2008-05-04 at 08:39 -0400, Jonathan Pryor wrote:
I would like to install and help test Beta 2. Unfortunately, before I can install it I'm running into a few problems...
I downloaded the x86-64 DVD image via BitTorrent.
Problem 1: http://download.opensuse.org/distribution/11.0-Beta2/iso/torrent/ doesn't have an MD5SUMS or SHA1SUMS file, so I don't know if these files are downloaded correctly.
They are not needed.
The .torrent file contain checksum information internally, so that when a chunk is downloaded incorrectly, it retries till it gets the chunk correct. That's why the .torrent file is big: it contains the checksums for all the chunks.
Now, if KTorrent is unable to produce a perfect downloaded iso, and even more, unable to correct the possible errors, that's a bug of KTorrent. Don't use it.
Use the plain "BitTorrent", for instance (btdownloadgui or btdownloadcurses), or probably azureus. I have sucesfully used btdownloadcurses to reconstruct bad downloads produced by KTorrent or ftp.
Now, if after a download using a good client is finished, Yast says the image is wrong, that's a bug in yast.
And in order to determine in which of these apps the bug actually occurs in... It would be really handy to have the MD5SUM, no? :-) - Jon --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-05-04 at 15:38 -0400, Jonathan Pryor wrote:
And in order to determine in which of these apps the bug actually occurs in...
It would be really handy to have the MD5SUM, no? :-)
Yes :-) Somebody said where they are, I think. however, I would trust "btdownloadcurses" to do a good job, and I don't trust the kde client. I've been bitten, and heard of some people also bitten. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIHjg0tTMYHG2NR9URAqXOAKCXa105g+/cS2uKf8RnIck9TpxsbgCeOjHo dkIR0uewHhYxgqv+MACq2lc= =+kA0 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, 2008-05-04 at 08:39 -0400, Jonathan Pryor wrote:
Now, this is likely a problem with either (a) my iso image, (b) my DVD writer, (c) the DVD writer program I'm using (nautilus-cd-burner), or (d) horribly bad luck.
Unfortunately I can't verify (a) without an MD5SUM/SHA1SUM for my ISO image, which I don't have (courtesy problems 2/3), and I'd like to ensure that (a) isn't a problem before I further investigate (c).
Thank you for all your help. (a) is no longer an issue -- my ISO verifies the other MD5SUMs posted to this list (and for good measure passes "Check Installation Media" within VMware). (c) probably isn't an issue, as I've tried nautilus-cd-burner, Brasero, and K3B, and they've all failed for me. I've created 6 coasters today, so I don't think (d) is at issue, this is far too consistent. Which leaves (b) my DVD writer is bad. As trying to burn on another computer which has successfully burned DVDs before also results in coasters (3 of them), I think I'm going to have to blame (e) the blank DVD-R media itself. :-/ Thank you for your assistance. - Jon --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-05-04 at 16:31 -0400, Jonathan Pryor wrote:
(a) is no longer an issue -- my ISO verifies the other MD5SUMs posted to this list (and for good measure passes "Check Installation Media" within VMware).
(c) probably isn't an issue, as I've tried nautilus-cd-burner, Brasero, and K3B, and they've all failed for me.
I've created 6 coasters today, so I don't think (d) is at issue, this is far too consistent.
What do you use for testing? If you use yast to do the checking, and it says "bad", then do the check directly with md5sum on the dvd itself. Something like: md5sum /dev/dvd - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIHjlWtTMYHG2NR9URAqzzAJ4rKw6kPjrUSRfM0yuwMYYKuDI76QCfc0bh 3RiKXs0ZtxEdij2jrEV6uiA= =2eS2 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Monday 05 May 2008 01:31:48 Carlos E. R. wrote:
If you use yast to do the checking, and it says "bad", then do the check directly with md5sum on the dvd itself. Something like:
md5sum /dev/dvd
Better use: dd if=/dev/dvd | head --bytes=4595124224 | md5sum where replace 4595124224 with the size in bytes of the iso (this value is for beta1 iso). Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-05-05 at 08:45 +0300, Andras Mantia wrote:
md5sum /dev/dvd
Better use: dd if=/dev/dvd | head --bytes=4595124224 | md5sum
I'm curious: Why? :-? I mean, why is it better, what is the advanteage?
where replace 4595124224 with the size in bytes of the iso (this value is for beta1 iso).
Why not use "count" and "bs" instead of "| head..."? It saves a huge piping job. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIHt8XtTMYHG2NR9URAs66AKCKAyM2HvE8twq92VjXCaQ7WqyjQACfX0e4 LYlKX7uwA8sdyIK+J8+gHjg= =05WL -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Monday 05 May 2008, Carlos E. R. wrote:
The Monday 2008-05-05 at 08:45 +0300, Andras Mantia wrote:
md5sum /dev/dvd
Better use: dd if=/dev/dvd | head --bytes=4595124224 | md5sum
I'm curious: Why? :-?
I mean, why is it better, what is the advanteage?
Because without it some padding bytes are read and the md5sum will be different. That is the explanation I read and the personal experience as well.
where replace 4595124224 with the size in bytes of the iso (this value is for beta1 iso).
Why not use "count" and "bs" instead of "| head..."? It saves a huge piping job.
Well, I did not think about what is better, I took the above command from a website. :) Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-05-05 at 21:05 +0300, Andras Mantia wrote:
On Monday 05 May 2008, Carlos E. R. wrote:
The Monday 2008-05-05 at 08:45 +0300, Andras Mantia wrote:
md5sum /dev/dvd
Better use: dd if=/dev/dvd | head --bytes=4595124224 | md5sum
I'm curious: Why? :-?
I mean, why is it better, what is the advanteage?
Because without it some padding bytes are read and the md5sum will be different. That is the explanation I read and the personal experience as well.
Ah... Does that apply to the md5sum command used directly, or only via dd? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIH2SttTMYHG2NR9URAuZ2AJ4htVk2WKfaNi9+n7pQJRuxeiF3GQCfT6VI D05obr3In3CU93Uk7IYG6co= =5LLb -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Monday 05 May 2008, Carlos E. R. wrote:
Ah...
Does that apply to the md5sum command used directly, or only via dd?
AFAIK it does apply for both, I tried the direct command and get wrong md5sum, while with the command I listed I got the correct one. Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-05-05 at 23:01 +0300, Andras Mantia wrote:
On Monday 05 May 2008, Carlos E. R. wrote:
Ah...
Does that apply to the md5sum command used directly, or only via dd?
AFAIK it does apply for both, I tried the direct command and get wrong md5sum, while with the command I listed I got the correct one.
I see... that's very interesting. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIH6KptTMYHG2NR9URAmFHAJ4iQsrquW19jLb8zmo9LruynR+p6gCdGV6W RhM+cpZgBwqPPCKjif4r+OE= =AV0T -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue 06 May 2008 07:49:01 NZST +1200, Carlos E. R. wrote:
Because without it some padding bytes are read and the md5sum will be different. That is the explanation I read and the personal experience as
Does that apply to the md5sum command used directly, or only via dd?
There are several issues which cause the equivalent of a cat /dev/sr0 to not return the correct number of bytes, making it useless for md5 sums. The only functional way to verify checksums of burnt media is to obtain the number of blocks occupied by the iso9660 filesystem, e.g. using isoinfo -d -i, and then to use dd bs=2k count=thatnumber - and hope the kernel doesn't screw you. The kernel detects EOM (end of media) by attempting to always read another bunch of 2k blocks. This fails to give the number of blocks you want/need because the burning process tends to write some blocks full of zeros at the end. Worse, a kernel problem present since the mid/late 90s attempts to read more blocks then there are, killing the lot with the ensuing I/O error, so you never get the last blocks used by the ISO filesystem. While mucking around doing this the drive in question (and all other accesses to it, including the other drive on the same IDE cable) is deadlocked for quite some time. Things are worse when DMA is enabled. Relief can be obtained by disabling read-ahead with hdparm -a0 at the expense of serious(!) performance loss. Not sure whether sdparm has a similar option (if not you're stuffed). dd bs=2k count=1 skip=N will never save you as the read-ahead will always read a chunk of blocks at once. For this reason I always burn with a script which chucks a pile of 0-filled blocks at the end of everything. If you install my scriptutils package the commands md5 -I / -y and writecd --blockread will always read the correct number of blocks for checksumming etc - as long as there is no I/O error. HTH, Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, 2008-05-05 at 00:31 +0200, Carlos E. R. wrote:
The Sunday 2008-05-04 at 16:31 -0400, Jonathan Pryor wrote:
(a) is no longer an issue -- my ISO verifies the other MD5SUMs posted to this list (and for good measure passes "Check Installation Media" within VMware).
(c) probably isn't an issue, as I've tried nautilus-cd-burner, Brasero, and K3B, and they've all failed for me.
I've created 6 coasters today, so I don't think (d) is at issue, this is far too consistent.
What do you use for testing?
K3B's validation check (which I believe is a sector-by-sector comparison of the ISO against the DVD) and booting the physical DVD within VMware and running the Check Installation Media target. - Jon --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-05-05 at 13:23 -0400, Jonathan Pryor wrote:
What do you use for testing?
K3B's validation check (which I believe is a sector-by-sector comparison of the ISO against the DVD)
No, that one calculates a checksum.
and booting the physical DVD within VMware and running the Check Installation Media target.
If both test say it is bad, then it is bad. Al coasters have the same incorrect checksum, or each a different one? You could also boot the iso image from vmware, that would check the iso itself. And you could also try the trick Andras Mantia proposes. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIH2WhtTMYHG2NR9URAi3iAJ0YqSOMlX7HhyukwgWYLggyRHIAAgCggpD9 0qHzCq0FDNtbwjcdKRobyP8= =OwnR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, 2008-05-05 at 21:53 +0200, Carlos E. R. wrote:
The Monday 2008-05-05 at 13:23 -0400, Jonathan Pryor wrote: If both test say it is bad, then it is bad. Al coasters have the same incorrect checksum, or each a different one?
They all seem to have a different sector where they fail. Which implies (to me) that my DVD media is at fault, not the writers. Thanks, - Jon --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, On Mon, 5 May 2008, Jonathan Pryor wrote:
On Mon, 2008-05-05 at 21:53 +0200, Carlos E. R. wrote:
The Monday 2008-05-05 at 13:23 -0400, Jonathan Pryor wrote: If both test say it is bad, then it is bad. Al coasters have the same incorrect checksum, or each a different one?
They all seem to have a different sector where they fail.
Which implies (to me) that my DVD media is at fault, not the writers.
You can try mkdir xx cd xx ln <where-your-ISO-is>/openSUSE-11.0-Beta2-DVD-i386.iso rsync -vvv rsync://ftp5.gwdg.de/pub/opensuse/distribution/11.0-Beta2/iso/dvd/openSUSE-11.0-Beta2-DVD-i386.iso . and watch on stdout which block(s) get refetched. I don't have the originating mail present, so change i386 against x86_64 if appropriate. Viele Grüße Eberhard Mönkeberg (emoenke@gwdg.de, em@kki.org)
On Mon, 2008-05-05 at 23:05 +0200, Eberhard Moenkeberg wrote:
On Mon, 5 May 2008, Jonathan Pryor wrote:
On Mon, 2008-05-05 at 21:53 +0200, Carlos E. R. wrote:
The Monday 2008-05-05 at 13:23 -0400, Jonathan Pryor wrote: If both test say it is bad, then it is bad. Al coasters have the same incorrect checksum, or each a different one?
They all seem to have a different sector where they fail.
Which implies (to me) that my DVD media is at fault, not the writers.
You can try mkdir xx cd xx ln <where-your-ISO-is>/openSUSE-11.0-Beta2-DVD-i386.iso rsync -vvv rsync://ftp5.gwdg.de/pub/opensuse/distribution/11.0-Beta2/iso/dvd/openSUSE-11.0-Beta2-DVD-i386.iso .
and watch on stdout which block(s) get refetched. I don't have the originating mail present, so change i386 against x86_64 if appropriate.
By "media" I didn't mean my .iso file (which matches the MD5SUM previously posted on this list), I mean my actual, physical blank DVD-R media. If all the DVDs failed consistently on the same sector, AND the MD5SUM didn't match, then the ISO would be at fault. Neither is true. So either both of my DVD writers are bad (and writing bad DVDs in inconsistent ways), or my spindle is full of bad DVD-Rs. I'm hoping it's the DVD-Rs. - Jon --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, On Mon, 5 May 2008, Jonathan Pryor wrote:
On Mon, 2008-05-05 at 23:05 +0200, Eberhard Moenkeberg wrote:
On Mon, 5 May 2008, Jonathan Pryor wrote:
On Mon, 2008-05-05 at 21:53 +0200, Carlos E. R. wrote:
The Monday 2008-05-05 at 13:23 -0400, Jonathan Pryor wrote: If both test say it is bad, then it is bad. Al coasters have the same incorrect checksum, or each a different one?
They all seem to have a different sector where they fail.
Which implies (to me) that my DVD media is at fault, not the writers.
You can try mkdir xx cd xx ln <where-your-ISO-is>/openSUSE-11.0-Beta2-DVD-i386.iso rsync -vvv rsync://ftp5.gwdg.de/pub/opensuse/distribution/11.0-Beta2/iso/dvd/openSUSE-11.0-Beta2-DVD-i386.iso .
and watch on stdout which block(s) get refetched. I don't have the originating mail present, so change i386 against x86_64 if appropriate.
By "media" I didn't mean my .iso file (which matches the MD5SUM previously posted on this list), I mean my actual, physical blank DVD-R media.
If all the DVDs failed consistently on the same sector, AND the MD5SUM didn't match, then the ISO would be at fault. Neither is true.
So either both of my DVD writers are bad (and writing bad DVDs in inconsistent ways), or my spindle is full of bad DVD-Rs. I'm hoping it's the DVD-Rs.
So you should try to burn with lower speed than possible (good practice here). Or just do not burn at all, but copy boot/i386/loader/{initrd,linux} into the to-installed-system, install it as a boot target, give network access to the ISO file (http, ftp or nfs) and try "install from network". Viele Grüße Eberhard Mönkeberg (emoenke@gwdg.de, em@kki.org)
On Mon, 2008-05-05 at 23:21 +0200, Eberhard Moenkeberg wrote:
So you should try to burn with lower speed than possible (good practice here).
I tried with a 2x burn speed, the slowest speed I could select. That failed.
Or just do not burn at all, but copy boot/i386/loader/{initrd,linux} into the to-installed-system, install it as a boot target, give network access to the ISO file (http, ftp or nfs) and try "install from network".
Are there any additional docs/HOWTOs on how to set this up? Thanks, - Jon --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, May 05, 2008 at 07:53:50PM -0400, Jonathan Pryor wrote: [ 8< ]
Or just do not burn at all, but copy boot/i386/loader/{initrd,linux} into the to-installed-system, install it as a boot target, give network access to the ISO file (http, ftp or nfs) and try "install from network".
Are there any additional docs/HOWTOs on how to set this up?
http://en.openSUSE.org/Network_Install doesn't notice 10.3 but this one works well too. This even allows remote clean updates. The mechanism only misses the reuse of the ssh server keys of the system intended to update. I've filed a feature request quite some time ago. By specifying the root device this little drawback might get fixed. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Jonathan Pryor wrote:
On Mon, 2008-05-05 at 21:53 +0200, Carlos E. R. wrote:
The Monday 2008-05-05 at 13:23 -0400, Jonathan Pryor wrote: If both test say it is bad, then it is bad. Al coasters have the same incorrect checksum, or each a different one?
They all seem to have a different sector where they fail.
Which implies (to me) that my DVD media is at fault, not the writers.
Thanks, - Jon
The DVD writers being produced are substandard. I have only one, the oldest, that produces good disks. I wasted many that way. One I produced only worked on the same box, but wouldn't on the others. That one was exchanged after I had trouble with the previous one on different motherboards. I read somewhere (LKML?) that a guy had problems with +R's, the -R's worked fine, but I have seen problems with both. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (10)
-
Andras Mantia -
Carlos E. R. -
Eberhard Moenkeberg -
Guillermo Ballester Valor -
Jonathan Pryor -
Lars Müller -
Michael Schmuker -
Rajko M. -
Sid Boyce -
Volker Kuhlmann