[Expired for debian-installer (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: debian-installer (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
From the hw-labs point of view, this problem is not happening anymore
after a full disk wipe (comment #14), so I'll set as Invalid.
** Changed in: hw-labs
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: debian-installer (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) =
(unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/834731
Title:
Dell PowerEdge
Removed the blocks-hwcert tag as the system is now installable. On
slangaseks I'll leave the bug as incomplete incase someone else
encounters it.
** Tags removed: blocks-hwcert
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/834731
Title:
Dell PowerEdge R810 fails to mount file system at /dev/sda1
To manage notifications about this bug go
Hi,
We wiped the disk and the problem is not reproducible anymore. This
might make it a bit difficult to debug...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/834731
Title:
Dell PowerEdge R810
We are still looking for information per Steve's comments in comment
#12. Pinged brendand on irc:
09:45 brendand bdmurray, at the moment that server is having a
different issue so it doesn't even get that far
I'm going to set it to incomplete since we still need some more
information and
Also, sorry if this seems like the wrong question but doesn't the fact
that it worked just fine with Natty indicate it's a genuine bug
(hardware config would have been identical)? It may be you just want to
establish that the RAID signature is or isn't causing the bug - in which
case ignore me.
