[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#600329: Fwd: RE: Manual submission: reportbug installation-reports



Forwarding with permission.
--- Begin Message ---
Hi Johnathan,

I'm glad something came of my report on all that way back when. What a
nightmare, I was very relieved to be able to get it installed somehow!
Afterward, it worked just fine, and for awhile it was doing its job without
issue.

Unfortunately, the rack that hardware was installed to was disassembled and
placed in storage shortly after it was all installed & made to be
functional- since December 2010, it's been buried in a storage unit. My
company ran out of money and paused operations last year.

It's not expected to be re-assembled until I have a new office to move my
company into, and that won't happen until I get financing somehow- my
business is on hold right now until I can finish my business plan, and apply
for a loan from the US Small Business Association. I hope to be able to
re-install that rack within another year, and don't expect it to happen in
less time than that.

Once the rack is installed, I don't imagine I'll have time to go through
another install of that box. It'll be in production at that time. The best I
might be able to do is reinstall if there ends up being a problem when I do
a dist-upgrade on it. I can only imagine opting to go through a fresh
re-install if I can't upgrade it from it's current state. If something
changes such that I end up with time & resources to spend reinstalling that
box, I'll keep your message here & let you know we're about to do that, in
case it can be helpful later next year.

Sorry I can't be as helpful as I'd like to be on this. It's too bad I didn't
have something telling me then what you need now, or I would've included it
then.

Come to think of it, I imagine since the box wasn't in service for very long
until it was powered down for good, would the requested syslog maybe still
be available once it gets powered up again? I'd be glad to provide a file or
2 if that's all you need. Providing you can wait until I re-install that
rack. There's no hope of powering it up in it's current condition, and it'll
have to wait until the rack gets a new permanent home maybe next year.



Regards,

Chris Bartels
President/CEO
Superior Sound Systems, LLC



-----Original Message-----
From: Jonathan Nieder [mailto:jrnieder@gmail.com] 
Sent: Sunday, February 19, 2012 12:42 PM
To: Chris Bartels
Cc: 600329@bugs.debian.org; Miguel Figueiredo
Subject: Re: Manual submission: reportbug installation-reports

retitle 600329 PowerEdge R210: d-i: firmware on USB stick not detected and
other problems quit

Hi Miguel,

Miguel Figueiredo wrote:

> what a very problematic installation you report!
> Let's divide the problems, if appropriate they can be divided in several
BRs.

Thanks for this.  It would have been even better if you cc-ed the submitter.
;-)

> a) - firmware search failed
>
> b) - devices order
>
> c) 3 bootloaders failed to install / on LVM
>
> d) - no lvm on /
>
> e) - failed partitioning
>
> On b) (devices order) your lscpi reports:
>
> 01:00.0 Ethernet controller [0200]: Intel Corporation 82598EB 
> 10-Gigabit
> 01:00.1 Ethernet controller [0200]: Intel Corporation 82598EB 
> 10-Gigabit
> 02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme II
> 02:00.1 Ethernet controller [0200]: Broadcom Corporation NetXtreme II
>
> ~# ethtool -i ethX
> will also report the bus info.
>
> Is this (the detection) correct?
>
> For a), c), d) and e) we will need more info to try to understand what 
> happened. Can you send the (gzipped) syslog from the installation?
> Can you provide more info on this? Is this reproducible?

Chris, do you still have access to this hardware?  Would you be able to try
another installation or get the requested information some other way?  What
software is the machine running these days, and has any other information
that could help to resolve these bugs come to light?

Sorry for the slow response, and hope that helps.

Sincerely,
Jonathan

-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2112/4819 - Release Date: 02/19/12


--- End Message ---

Reply to: