| 2006-11-20 18:44:36 |
tchize |
bug |
|
|
added bug |
| 2006-11-20 19:00:47 |
Ben Collins |
linux-source-2.6.17: status |
Unconfirmed |
Needs Info |
|
| 2006-11-20 19:00:47 |
Ben Collins |
linux-source-2.6.17: statusexplanation |
|
Please add debug to the kernel command line to see if you get any extra output.
Also, please do not paste large output into comments. Use the "attach" functionality.
Thanks |
|
| 2006-11-20 19:35:17 |
tchize |
bug |
|
|
added attachment 'debug-dmesg' (dmesg after booting in debug mode) |
| 2006-11-21 01:36:15 |
Ben Collins |
linux-source-2.6.17: status |
Needs Info |
Confirmed |
|
| 2006-11-21 01:36:15 |
Ben Collins |
linux-source-2.6.17: importance |
Undecided |
Medium |
|
| 2006-11-21 01:36:15 |
Ben Collins |
linux-source-2.6.17: statusexplanation |
Please add debug to the kernel command line to see if you get any extra output.
Also, please do not paste large output into comments. Use the "attach" functionality.
Thanks |
|
|
| 2006-11-21 05:26:53 |
Fabio Massimo Di Nitto |
linux-source-2.6.17: assignee |
|
fabbione |
|
| 2006-11-21 05:26:53 |
Fabio Massimo Di Nitto |
linux-source-2.6.17: statusexplanation |
|
This is interesting because i am not able to reproduce it. Can you please make sure that:
/etc/mdadm/mdadm.conf does actually contain all the correct info about your raid devices? Do you have any dead raid in that set? Once your mdadm.conf has been verified to be correct, could you please try to regenerate the initramfs for that kernel and reboot into it?
The 6 minutes are probably introduced by either mdadm waiting for the raids to show up or lvm waiting for volume groups or mountroot scripts waiting for /dev/md3 to appear.
Fabio |
|
| 2006-11-21 19:37:00 |
tchize |
bug |
|
|
added attachment 'mdadm-original.conf' (The mdadm.conf before any attempt at fixing) |
| 2006-11-21 19:38:02 |
tchize |
bug |
|
|
added attachment 'mdadm.conf' (The final mdadm.conf (no md0 anymore, no partitions scan)) |
| 2006-11-21 19:40:02 |
tchize |
bug |
|
|
added attachment 'boot-with-calltraces' (The dmesg with hitting alt-sysrq-T for call traces during pause) |
| 2006-11-21 21:30:31 |
tchize |
bug |
|
|
added attachment 'mdadm.conf' (failing mdadm.conf. Remove comments and it works) |
| 2006-11-22 00:22:24 |
Ben Collins |
linux-source-2.6.17: status |
Unconfirmed |
Rejected |
|
| 2006-11-22 00:22:24 |
Ben Collins |
linux-source-2.6.17: statusexplanation |
|
|
|
| 2006-11-26 11:29:22 |
Istvan Botka |
bug |
|
|
added attachment 'md.patch' (patch for scanning whole disks as a member of a raid array) |
| 2006-11-26 12:03:36 |
Istvan Botka |
marked as duplicate |
|
67299 |
|
| 2006-12-04 07:27:52 |
Fabio Massimo Di Nitto |
changed duplicate marker |
67299 |
74346 |
|
| 2006-12-04 16:55:41 |
Fabio Massimo Di Nitto |
removed duplicate marker |
74346 |
|
|
| 2006-12-13 05:35:26 |
Fabio Massimo Di Nitto |
mdadm: status |
Confirmed |
Fix Released |
|
| 2006-12-13 05:35:26 |
Fabio Massimo Di Nitto |
mdadm: statusexplanation |
This is interesting because i am not able to reproduce it. Can you please make sure that:
/etc/mdadm/mdadm.conf does actually contain all the correct info about your raid devices? Do you have any dead raid in that set? Once your mdadm.conf has been verified to be correct, could you please try to regenerate the initramfs for that kernel and reboot into it?
The 6 minutes are probably introduced by either mdadm waiting for the raids to show up or lvm waiting for volume groups or mountroot scripts waiting for /dev/md3 to appear.
Fabio |
The fixed package is now available in edgy-updates.
Fabio |
|
