tags 582177 + moreinfo thanks * maximilian attems <m...@stro.at> [Mit Mai 19, 2010 at 09:49:56 +0200]: > On Wed, May 19, 2010 at 02:50:42PM -0400, crop...@acm.org wrote:
[...] > > _____________________________________________ > > Kernel output (LITERAL DATA, except for "... area below"): > > [1.185516] rtc_cmos 00:0a: setting system clock to 2010-05-19 18:18:27 UTC > > (1274293107) > > [1.185628] Waiting 12sec before mounting root device > > [1.199432] input: AT translated Set 2 keyboard as > > /devices/platform/i8042/serio0/input/input1 > > [12.992053] List of all partitions: > > [12.992128] No filesystem could mount root, tried: > > [12.992221] kernel panic - no syncing: VFS: unable to mount root fs on > > unknown wn-block(0,0) > > [12.992287] Pid: 1, comm: swapper Not tainted 2.6.32-3-amd64 #1 > > [12.992340] Call Trace: > > [12.992397] [<ffffffff812ed349>] ? panic+0x86/0x141 > > ... ... ... > > ... ... ... > > [12.992880] [<ffffffff81011ba0>] ? child_rip+0x0/0x20 > aboves says that linux-2.6 is not getting the initramfs. > thus indeed blaming GRUB seems the current state of affair. [...] > > Questions: > > 1) Could this be grub? > > 2) Could "resynchronizing" md0 fix this problem? I seem to > > remember doing something like this and the problem went away in > > March... :-/ > > 3) Any other suggestions? > adding GRUB maintainers to Cc as this new bug report seems to be a > recurring trend. #578473 seems to be duplicate of that one. > GRUB maintainers can you advise? To the bugreporter: Could you please boot a rescue system / live system and synchronize your md device(s) and retry? This strongly looks like an issue with out-of-sync data to me. To maks + grub maintainers: any objections against reassigning to grub? regards, -mika-
signature.asc
Description: Digital signature
