From: Jose R R <Jose.r.r@metztli-it.com>
To: Adam Borowski <kilobyte@angband.pl>, 823986@bugs.debian.org
Cc: Debian Bug Tracking System <submit@bugs.debian.org>,
ReiserFS Development List <reiserfs-devel@vger.kernel.org>
Subject: Re: Bug#823986: installation-reports: "hardware" errors on virtualbox
Date: Tue, 10 May 2016 19:36:52 -0700 [thread overview]
Message-ID: <CAM12Q5QAV6LV__eahx16_rLxtT3zNuZnxKXVXbpExLkAzo5LNg@mail.gmail.com> (raw)
In-Reply-To: <146293002411.13267.14445852398726516532.reportbug@umbar.angband.pl>
"02:29 < kilobyte> reproduced in virtualbox: lots of I/O errors: ata1.00:
failed command: WRITE FPDMA QUEUED"
As I frequently test Reiser4-enabled unstable Debian-Installers on
VirtuaBox 5.0.16 (my latest version), on a frequent basis I come
across similar I/O errors: ata related as well as some other
idiosyncrasies related to unstable nature of my d-i builds. Wait a few
days for the debian-installer component UDEBs to stabilize and work
better together --in harmony-- then try your installation again.
On Tue, May 10, 2016 at 6:27 PM, Adam Borowski <kilobyte@angband.pl> wrote:
> Package: installation-reports
> Severity: normal
>
>
> 00:37 < calops> hi, is there any known issue about the testing installer
> (netinst and CD) failing around the "selecting packages"
> step?
> 00:39 < calops> it happens to me both natively on my machine, and as a
> virtualbox guest
> 01:35 < Sledge> calops: anything in syslog?
> 02:29 < kilobyte> reproduced in virtualbox: lots of I/O errors: ata1.00:
> failed command: WRITE FPDMA QUEUED
>
> Syslog attached. The failed step was "Select and install software", no
> error message was given other than "installation step failed".
>
> No hardware or software errors on the host, other VMs work fine, so this is
> not a fault of the new version of virtualbox (current unstable --
> 5.0.20-dfsg-1). And that calops guy reports it's failing on bare metal too.
>
>
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (150, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.6.0-rc6-debug2+ (SMP w/6 CPU cores)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
--
Jose R R
http://metztli.it
---------------------------------------------------------------------------------------------
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
---------------------------------------------------------------------------------------------
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
---------------------------------------------------------------------------------------------
parent reply other threads:[~2016-05-11 2:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <146293002411.13267.14445852398726516532.reportbug@umbar.angband.pl>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM12Q5QAV6LV__eahx16_rLxtT3zNuZnxKXVXbpExLkAzo5LNg@mail.gmail.com \
--to=jose.r.r@metztli-it.com \
--cc=823986@bugs.debian.org \
--cc=kilobyte@angband.pl \
--cc=reiserfs-devel@vger.kernel.org \
--cc=submit@bugs.debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).