Sorry, I have migrated away from md-raid in favor of hardware raid at
the time of this bug and have not rebuild any system to use md-raid
since. With hardware raid and the same disks the problem does not occur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Rudi Daemen, this bug report is being closed due to your last comment
regarding you no longer using the same setup. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You
Rudi Daemen, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue?
Can you try with the latest development release of Ubuntu? ISO CD images
are available from http://cdimage.ubuntu.com/releases/ .
If it remains an issue,
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/613872
Title:
md raid5 set inaccessible after some time.
--
ubuntu-bugs mailing list
Sorry for the bump but maybe something to keep in mind with this issue.
Some reading up on the internet has gotten me on a different track about
the loss of the RAID Arrays in my old setup:
It seems starting with kernels newer then 2.6.24 there might be a change
in the timers mdadm uses to
** Tags added: acpi-table-checksum
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/613872
Title:
md raid5 set inaccessible after some time.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Tags added: kj-triage
--
md raid5 set inaccessible after some time.
https://bugs.launchpad.net/bugs/613872
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Took less then 24 hours this time. However I did manage to capture dmesg
output this time. See the attachment for the full log, here's the
snippet how it goes wrong:
mdadm detects a drive timeout (these soft hangs of the hard drives have
been present ever since day one and never caused any
Ok, the problem occurred again... However for some reason it did not
capture the errors on the USB drive. I did happen to have a console open
at the time and managed to get the response from a dmesg output. It was
swamped with the following text:
[358579.557869] metapage_write_end_io: I/O error
Managed to get the system up and running again. Had to reassemble all
mdadm raid arrays using a live CD. After reassembling all arrays I
rebooted back into the operating system and had to reboot three times to
get it to work again.
First reboot, it prompted it noticed a size change from 0 to
** Attachment added: lspci -vvv output
http://launchpadlibrarian.net/53108844/lspci_vvv.txt
--
md raid5 set inaccessible after some time.
https://bugs.launchpad.net/bugs/613872
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Dmesg output from last boot.
** Attachment added: dmesg output
http://launchpadlibrarian.net/53108878/dmesg.txt
--
md raid5 set inaccessible after some time.
https://bugs.launchpad.net/bugs/613872
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
12 matches
Mail list logo
