Crc Error Suse Boot
Wed, 15 Apr 2009 14:39:12 -0400 Message-id: <49E629D0.3060008@xxxxxxxxxxxxx> AV pecked at the keyboard and wrote: Hi, have HP DC7800 PC with BlueRay and two 1,5TB disks. Until recent update system was ok running suse 11.1. After update can not boot, get crc error. Reinstalled system and did update - same error. How can I solve this error. Kernel 2.6.27.21-0.1. Audrius Rats, the crystal ball has stopped working again. :-) Try giving us more info: 32 or 64 bit install what extra packages installed if any what was updated Could be a failing memory with a bad spot somewhere, try running memtest overnight. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx < Previous Next > Thread Index Author Index Date Index All Messages Search this list List Navigation Overview Next Thread Previous Thread Top of the Page Feedback This Thread AV Ken Schneider - openSUSE Message not available AV AV AV Carlos E. R. Rajko M. AV Rajko M. AV Rajko M. Rajko M. Carlos E. R. AV Follow Ups AV References AV
+0300 Message-id: On Wed, Apr 15, 2009 at 11:32 PM, AV wrote: And when I use repair - File system check I get: -executing file system check for partition /dev/sda2... /dev/sda2 contains no valid Ext3 file system But how!?! I just installed system and formated all https://lists.opensuse.org/opensuse/2009-04/msg01136.html partitions? Just reinstalled system and no update - system boots and works OK. Could it be related to new kernel and big disks like I have (1,5TB)? Or some ext3 module? Or...? Now I have working system and can provide any info you need... https://lists.opensuse.org/opensuse/2009-04/msg01161.html I think will try to update all packages except kernel... Yep! If I update everything except kernel all is ok. When I updated kernel I get crc error... I updated to 2-6.27.21-0.1. Definitely there is something wrong with that kernel... -- To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx < Previous Next > Thread Index Author Index Date Index All Messages Search this list List Navigation Overview Next Thread Previous Thread Top of the Page Feedback This Thread AV Ken Schneider - openSUSE Message not available AV AV AV Carlos E. R. Rajko M. AV Rajko M. AV Rajko M. Rajko M. Carlos E. R. AV Follow Ups Carlos E. R. References AV Ken Schneider - openSUSE AV
in Linux (DRBL) Discussion Diskless Remote Boot in Linux (DRBL) Brought to you by: steven_shiau Summary Files Reviews Support Wiki Mailing Lists Tickets ▾ Support Requests Feature Requests Bugs News Discussion Donate Create Topic Stats Graph Forums DRBL Live 131 DRBL for Debian/Ubuntu/B2D 460 DRBL https://sourceforge.net/p/drbl/discussion/DRBL_for_Redhat/thread/38e891c6/ for RedHat/Mandriva/SuSE 354 Help 131 Open Discussion 83 Help Formatting Help crc error at client boot Forum: DRBL for RedHat/Mandriva/SuSE Creator: Antony JULIEN Created: 2005-04-06 Updated: 2012-12-12 Antony JULIEN - 2005-04-06 Hello, I have installed DRBL on the server with no error messages but I have a random problem at client boot : RAMDISK: Compressed image found at block 0 crc error VFS: Cannot open root device "" or unknown-block(72,3) Please append a correct "root=" boot option Kernel crc error panic - not syncing: VFS: Unable to mount root fs on unknown-block(72,3) This appends sometimes but not always (about 50 percent of client boots). This looks-like another error mentioned in this forum (https://sourceforge.net/forum/forum.php?thread_id=1240716&forum_id=394007) but the initial error is not the same (crc error). Please, could you help me if you have an idea on the purpose? PS : Excuse the bad quality of my english because i am French. If you would like to refer to this comment somewhere crc error suse else in this project, copy and paste the following link: Steven Shiau - 2005-04-11 What's the kernel used by client ? Please run cat /tftpboot/nbi_img/kernel_version_in_initrd.txt Say, if you got "2.6.10-1.770_FC3", then find the "CONFIG_CRAMFS" in /tftpboot/node_root/boot/config-2.6.10-1.770_FC3 Tell us it's a module (=m) or builtin (=y). BTW, another test is that you can try to use good quality cross-over RJ-45 cable to connect your client and server directly. Check if "crc error" will occur or not. If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Antony JULIEN - 2005-04-11 Hello, the kernel used by client is 2.6.10-1.770_FC3 and the CONFIG_CRAMFS is m (module) I am going to test with a cross-over cable and I'll tell you. If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Antony JULIEN - 2005-04-12 I have tested with a cross-over cable a few times (about 10) and it seems to work, I got no error. The problem is that DRBL will be used all over the company and we need it works through swiths and hubs. Do you know if it could be possible to modify DRBL to make the client reload the image if a crc error occurs ? Thank you for advance. If you would like to refer to this comment somewhere else in this