|
Bugzilla – Full Text Bug Listing |
| Summary: | I got many different installation errors | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Heiko Schmidt <heiko.schmidt> |
| Component: | Installation | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | mls |
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Installation logs | ||
|
Description
Heiko Schmidt
2005-09-08 09:18:32 UTC
Before I installes SuSE 10.0 Beta 3 on the same maschine without any trouble Did you check your media? Please provide logs as described in http://www.opensuse.org/Bug_Reporting_FAQ#YaST Lowering severity... I downloaded the iso-files from different servers burned all isos twice with the same result. For the log files I´ll try switching to F2 and provide it tomorrow. Did you verify the MD5SUMs of the ISO images? Please check out http://www.opensuse.org/Download_Instructions ! yes I verfied all isos with md5sum and diff it against the MD5SUMS from the download-directory. Also I verified all media during the installation process with Yast-Interface. s far as this everything seemed allwrigth. Created attachment 49321 [details]
Installation logs
This are all logs I found at /var/log/yast2
Michael, have you ever seen logs like these ones? y2logRPM: 2005-09-07 23:48:59 xemacs-packages-info-20050715-3.noarch.rpm installed ok 2005-09-07 23:49:00 apache2-prefork-2.0.54-8.i586.rpm installed ok 2005-09-07 23:49:03 emacs-21.3-206.i586.rpm install failed rpm output: rpmdb: page 633: illegal page type or format rpmdb: PANIC: Invalid argument error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "ediff-diff.elc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->cursor: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "ediff-help.elc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery y2log-9 2005-09-08 00:11:06 <3> linux(14803) [rpmdb] RpmDb.cc(installPackage):1662 error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery 2005-09-08 00:11:06 <3> linux(14803) [rpmdb] RpmDb.cc(installPackage):1662 error: error(-30978) getting "R.." records from Filemd5s index 2005-09-08 00:11:06 <3> linux(14803) [rpmdb] RpmDb.cc(installPackage):1662 rpmdb: PANIC: fatal region error detected; run recovery 2005-09-08 00:11:06 <3> linux(14803) [rpmdb] RpmDb.cc(installPackage):1662 error: db4 error(-30978) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery 2005-09-08 00:11:06 <3> linux(14803) [rpmdb] RpmDb.cc(installPackage):1662 error: error(-30978) getting "...=X.@.Λ..4.J@..........." records from Filemd5s index 2005-09-08 00:11:06 <3> linux(14803) [rpmdb] RpmDb.cc(installPackage):1662 rpmdb: PANIC: fatal region error detected; run recovery y2log-1 2005-09-08 00:13:33 <3> linux(14803) [rpmdb] RpmDb.cc(installPackage):1662 rpmdb: PANIC: fatal region error detected; run recovery 2005-09-08 00:13:33 <3> linux(14803) [rpmdb] RpmDb.cc(installPackage):1662 error: db4 error(-30978) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery 2005-09-08 00:13:33 <3> linux(14803) [rpmdb] RpmDb.cc(installPackage):1662 2005-09-08 20:38:20 <1> linux(15236) [liby2] genericfrontend.cc(main):193 Launched YaST2 component 'y2base' the same also with ElectricFence-2.2.2-532.i586.rpm package in y2log Looks like a corrupt rpm database. I can't help you with this one. Was that a fresh install? If yes you have probably some flaky memory, please run memtest. It was a new installation, but one week before I installed Beta 3 without any problem. I will run memtest and provide informatiom on monday. Thanks! Hi, I was running memtest on Debian Sarge on the same harware and it presents me an memory access error. So I think we should close this defect. I will purchase new memory and have a new try with RC2. Or you have another idea ? Closing bug - probably wrong memory. I'd suggest buing a new memory, `everything` should go well then :) ... well, better, at least ;) |