Ben Hutchings wrote:
> On Tue, 2016-06-28 at 00:49 +0200, deloptes wrote:
>> Jeffrey Mark Siskind wrote:
>>
>> > I had big issues with mptsas and 3.16 in jessie, so I am still using
>> > 3.2.0-4-rt-amd64
>> >
>> > Will jessie run with 3.2.0-4-rt-amd64? If so, where do I get it and how
>> > do I
On Mon, 2016-06-27 at 11:58 -0400, Jeffrey Mark Siskind wrote:
> The non-determinism in which identifiers are shown might be a bug in the
> installer, or it might be caused by failure of ID commands to the
> drives.
>
> I think most of the problems you're still having must be caused by
On Tue, 2016-06-28 at 00:49 +0200, deloptes wrote:
> Jeffrey Mark Siskind wrote:
>
> > I had big issues with mptsas and 3.16 in jessie, so I am still using
> > 3.2.0-4-rt-amd64
> >
> > Will jessie run with 3.2.0-4-rt-amd64? If so, where do I get it and how do
> > I install it on a fresh jes
I had big issues with mptsas and 3.16 in jessie, so I am still using
3.2.0-4-rt-amd64
Will jessie run with 3.2.0-4-rt-amd64? If so, where do I get it and how do I
install it on a fresh jessie install that wasn't dist-upgraded from wheezy?
Jeff (http://engineering.purdue.edu/~qobi)
Ben Hutchings wrote:
> I think most of the problems you're still having must be caused by a
> bug in the RAID driver, mpt2sas (or its firmware, if that's not
> embedded in the BIOS).
I had big issues with mptsas and 3.16 in jessie, so I am still using
3.2.0-4-rt-amd64
rootdelay=15 did not help i
The non-determinism in which identifiers are shown might be a bug in the
installer, or it might be caused by failure of ID commands to the
drives.
I think most of the problems you're still having must be caused by a
bug in the RAID driver, mpt2sas (or its firmware, if that's not
On Mon, 2016-06-27 at 08:07 -0400, Jeffrey Mark Siskind wrote:
[...]
> Whenever I observe any of the behavior reported in this email, it is
> almost always associated with dmesg reporting the same error on the same
> sector 2056 (sometimes 2058 or 2062). Given the dozens of attempted
>
I'd like to thank everyone for helping out.
Here is an update on installing jessie on R815s.
I succeeded in installing on three of my four R815s. But I am holding off on
the last because it is my file server and there are still issues. Please read
on. I don't believe that the problem is solved an
On Fri, Jun 24, 2016 at 06:22:37PM -0400, Jeffrey Mark Siskind wrote:
>Please note that bootint with rootdelay=20 does not solve the problem. It only
>masks it.
>
> 1. If I attempt a fresh USB install of jessie, when md0 is correctly built
>before the install, the process of doing the fresh ins
Please note that bootint with rootdelay=20 does not solve the problem. It only
masks it.
1. If I attempt a fresh USB install of jessie, when md0 is correctly built
before the install, the process of doing the fresh install breaks
md0. When it gets to grub install, components of md0 are mi
Dell Customer Communication
>>Are you certain that there isn't a PERC H700 in this machine? [Sort of
>>odd that mpt2sas is triggering a state error in your screenshot if
> there
>>actually isn't one.]
>>
>> There could be one. But I probably don't use it. I use soft
>Are you certain that there isn't a PERC H700 in this machine? [Sort of
>odd that mpt2sas is triggering a state error in your screenshot if there
>actually isn't one.]
>
> There could be one. But I probably don't use it. I use software RAID. Dell
> wouldn't sell an R8
I conjecture that there may be two to five separate issues.
1. Setting up md0 upon boot takes a long time. rootdelay=20 fixes this.
2. There is a problem writing to disk. Perhaps just writing to certain blocks.
Because even when the machine boots with rootdelay=20, and md0 has all 6
comp
>Are you certain that there isn't a PERC H700 in this machine? [Sort of
>odd that mpt2sas is triggering a state error in your screenshot if there
>actually isn't one.]
>
> There could be one. But I probably don't use it. I use software RAID. Dell
> wouldn't sell an R815 without an OS.
> and attempted
>
>mdadm /dev/md0 --add /dev/sda1
>mdadm /dev/md0 --add /dev/sdb1
>mdadm /dev/md0 --add /dev/sdc1
>mdadm /dev/md0 --add /dev/sdd1
>mdadm /dev/md0 --add /dev/sde1
>mdadm /dev/md0 --add /dev/sdf1
>
> but these all failed.
Thi
Are you certain that there isn't a PERC H700 in this machine? [Sort of
odd that mpt2sas is triggering a state error in your screenshot if there
actually isn't one.]
There could be one. But I probably don't use it. I use software RAID. Dell
wouldn't sell an R815 without an OS. I think I pu
On Wed, 22 Jun 2016, Jeffrey Mark Siskind wrote:
> and attempted
>
>mdadm /dev/md0 --add /dev/sda1
>mdadm /dev/md0 --add /dev/sdb1
>mdadm /dev/md0 --add /dev/sdc1
>mdadm /dev/md0 --add /dev/sdd1
>mdadm /dev/md0 --add /dev/sde1
>mdadm /dev/md0 --add /dev/sdf1
>
> but these
On Wed, Jun 22, 2016 at 09:24:51PM +0200, deloptes wrote:
> Sorry previous went out incomplete, because of some shortcut I pressed
> wrongly
>
> Here is what I found
>
> lrwxrwxrwx 1 root root 9 Jun 22 14:16
> ata-WDC_WD800GD-75FLC3_WD-WMAKE1962410 -> ../../sda
> lrwxrwxrwx 1 root root 9 Jun
Sorry previous went out incomplete, because of some shortcut I pressed
wrongly
Here is what I found
lrwxrwxrwx 1 root root 9 Jun 22 14:16
ata-WDC_WD800GD-75FLC3_WD-WMAKE1962410 -> ../../sda
lrwxrwxrwx 1 root root 9 Jun 22 14:16
ata-WDC_WD800JD-75JNC0_WD-WCAM97914701 -> ../../sdb
lrwxrwxrwx 1
Don Armstrong wrote:
> Yes; it's possible that a change in one of the drivers between the
> wheezy and jessie kernels is exposing a firmware bug (or there's a bug
> in the kernel itself) which is causing this issue.
>
> What I'm trying to do is get enough information so that the error is
> obviou
On Tue, 21 Jun 2016, Jeffrey Mark Siskind wrote:
> http://upplysingaoflun.ecn.purdue.edu/~qobi/20160619_140357.jpg
Are you certain that there isn't a PERC H700 in this machine? [Sort of
odd that mpt2sas is triggering a state error in your screenshot if there
actually isn't one.]
> I don't believe
This is the separate lesser issue I hinted at in an earlier post. I also
upgraded my four Dell Poweredge C6145s. A fresh install of wheezy was
successfull on those. And again, the disks were partitioned in a similar
fashion to those on my R815s. (Four larger disks on the C6145s and six smaller
disk
Thanks for your help.
> Here is a screen picture.
Could you upload this to an image paste site or send it along (or use a
serial console to get it as text?)
http://upplysingaoflun.ecn.purdue.edu/~qobi/20160619_140357.jpg
(The other screen picture of a machine (not an R815) that does bo
On Tue, 21 Jun 2016, Jeffrey Mark Siskind wrote:
> Please note that all of the above systems have / as md0 RAID1. The fresh
> install of jessie was successfull on all but the R815s.
>
>> Then it fails to reboot
My posting has not appeared on debian-{boot,kernel,user}. I think it is
because of the attachments. I have removed them. I'll send the screen images
to people individually if they request them.
---
I am cross posting this t
Please don't send the same question separately to multiple lists. Use
cross-posting in future.
Ben.
--
Ben Hutchings
Never put off till tomorrow what you can avoid all together.
signature.asc
Description: This is a digitally signed message part
I am attempting to install jessie on a Dell Poweredge R815 (I have four). It
has been running wheezy reliably for years. And running squeeze reliably for
years before that. But no matter what I try it won't install or boot.
I have tried two ways.
1. I attempt a fresh install from a USB dongle. I
27 matches
Mail list logo
