Boyd Stephen Smith Jr. <bss03 <at> volumehost.net> writes:
> > /dev/sda2 /boot reiserfs defaults 1 2 > > /dev/sda4 / reiserfs defaults 1 1 > > which should force an fsck on the reiserfs file system? > I don't see how this would force a fsck. Well so much for the man page on fstab... ount to return on my 2+TiB filesystem.) > Also, resiserfsck is different than other fscks. It has two "fix" modes, > neither of which is automatic and one of which is quite dangerous; the one > you should use is based on the output of the "check" mode. Well OK, I got your instructions. However, xdm is not turned on so the system boots straight to a command line prompt. Previously I suspected the xorg.conf file for startup during xdm launch-->latchup. After disabling X/kde/xdm, the system still has problems. Last night it was just sitting in a quiescent state and it just latched up. Not good for a brand new laptop. Today I booted it up and set the date on the command line. Then I issued 'hwclock --systohc' and the system latched up tight, again. Power cycle and the minimal CD has the system running a memtest86 for a while, to ensure it's not the ram. If the ram proves up OK, then I'm going to follow your previous instructions on repairing the reiserfs partitions. What else could it be? This was a vista only laptop, so if all else fails, I'll just blame Microsoft...... I ran fdisk but, it may need an old fashion dos format? Suggestions on robust low_level formatting is I have to re-install this machine? I've got over a dozen systems with reiserfs on the /boot partition and not a single problem in almost 4 years of running gentoo and reiser on the boot partition. Losing 32M of space is a non issue for me. Reiser gets a lot of bad press, but, I like it very much and cannot wait until reiser4 is a bit more of a commodity. I've had lots of problems with ext2 and ext3 (No thanks)...... I'll drop a line when the memory testing is conclusive. thx, James -- [EMAIL PROTECTED] mailing list
