From: Dan A. <da...@co...> - 2005-01-28 10:45:12
|
On Tue, Jan 18, 2005 at 08:56:57AM +1000, Sam Moffatt wrote: > Something interesting from coLinux-users; appears that we have > eventual corruption on native mode ext3 drives over time. It would > appear that it might be a memory issue as he notes that it takes a > while for it to become apparent. > >[..] > > VFS: Cannot open root device "cobd/0" or unknown-brock(0,0) > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) > colinux: kernel panic suggests that either you forget to supply a > root= kernel boot parameter or the file / device mapped to the root > file system is not found or inaccesible. Plesae Check your > coLinux configuration >[..] That is not file system corruption, but something else. Notice the print-out of 'unknown-block(0,0)', this suggests that the kernel wasn't able to resolve the device name from a string to a proper [major, minor] tuple. cobd is major 117. Perhaps because the passed string was 'cobd/0' instead of 'cobd0'? -- Dan Aloni da...@co... |