Bug 148408

Summary:	separate ext2 fs on /boot is not checked after crash
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Carl-Daniel Hailfinger <kernel01>
Component:	Basesystem	Assignee:	Dr. Werner Fink <werner>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	fstab, tune2fs -l, /var/log.bot.msg

Description Carl-Daniel Hailfinger 2006-02-06 15:24:33 UTC

I have a separate /boot on ext2. If I boot after a crash, no fsck is run on /boot and the kernel complains:
ext2-fs warning: mounting unchecked fs, running e2fsck is recommended.

Unfortunately I can't attach /var/log/boot.msg because it doesn't exist (apparmor refused klogd write access to it).

Comment 1 Michael Gross 2006-02-06 15:31:34 UTC

Please attach the fstab of this system. Maby you should reconfigure AppArmor to work correctly here or disable it temporarily ;) What does `tune2fs -l' for that partition say? Was everything set up correctly (max mount count, and so on).

Comment 2 Carl-Daniel Hailfinger 2006-02-06 16:21:16 UTC

Created attachment 66565 [details]
fstab, tune2fs -l, /var/log.bot.msg

I disabled Apparmor and gathered all the logs you requested in the tarball.

Comment 3 Michael Gross 2006-02-06 16:26:18 UTC

Werner: Please comment about this?

Comment 4 Dr. Werner Fink 2006-02-06 16:50:30 UTC

Sorry, no idea.  The order of the boot script should be OK with Beta3.
This seems to be a duplet of bug #146606

*** This bug has been marked as a duplicate of 146606 ***