thanks for the info here, guys...
as maybe a little corroborating data on this, i'm not sure that the ext2 fs is the only thing going on here:
i had the exact same problem with '/' being fsck'd at every boot.
This is a "real" HDD installation of bt3 on fresh cfdisk'd partitions of a 40g hd on a Dell D600 laptop. these partitions were never anything but ext3 and were created specifically for bt3 (no previous data):
initially, i tried either logging in as a non-root account or logging in without X (and just immediately "shutdown -h now") just to see if that helped, of course it didnt....Code:Disk Drive: /dev/hda Size: 40007761920 bytes, 40.0 GB Heads: 255 Sectors per Track: 63 Cylinders: 4864 Name Flags Part Type FS Type [Label] Size (MB) ------------------------------------------------------------------------------------- hda1 Primary Linux swap 1019.94 hda2 Boot Primary Linux ext3 5000.98 hda3 Primary Linux ext3 5000.98 hda4 Primary Linux 28985.89
i booted off of my slack 12 disk and ran a manual fsck on unmounted hda2...
it complained about the last mount and the last write being in the future...blah blah blah (which i let it fix) and it only had 0.8 non-contiguous...so i didnt think that was really related.
sure enough, after the next bt3 reboot, the issue was back.
i've tried several different ways of mounting the drive (/etc/fstab)...here is the latest:
yeh, its a little messy by nowCode:# aufs / aufs defaults 0 0 # AutoUpdate # /dev/sda1 /mnt/sda1 ext3 auto,noatime,users,suid,dev,exec 0 0 # AutoUpdate # /dev/fd0 /mnt/floppy vfat noauto,noatime,users,suid,dev,exec 0 0 # AutoUpdate # /dev/hda2 / ext3 defaults 1 1 #AutoUpdate /dev/hda3 /forensics ext3 defaults 1 1 #AutoUpdate /dev/hdc /mnt/hdc iso9660 noauto,users,exec 0 0 # AutoUpdate # devpts /dev/pts devpts gid=5,mode=620 0 0 # AutoUpdate proc /proc proc defaults 0 0 # AutoUpdate sysfs /sys sysfs defaults 0 0 # AutoUpdate
so, i tried the rc.6 fix and uncommented the killall as posted here and the issue seems to have resolved.
i don't really see a down-side to the resolution (for me, anyway) but i suppose im a little curious about the cause.
reiser has scared me in the past on a data restore so im a little gun-shy there...but as long as this fixes it, no blood no foul.
thanks again for all the info in the thread....
peace!
~k



