[hafqa] [hafqa] [Bug 2021] New: initrd fails to fsck root filesystem
From: bugzilla-daemon at lists.maemo.org bugzilla-daemon at lists.maemo.orgDate: Tue Sep 18 14:22:50 EEST 2007
- Previous message: [hafqa] [Bug 1204] MMC read-only/corruption bug persists...
- Next message: [hafqa] [Bug 1204] MMC read-only/corruption bug persists...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://bugs.maemo.org/show_bug.cgi?id=2021 Summary: initrd fails to fsck root filesystem Product: System software Version: 3.2 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: Low Component: startup-shutdown AssignedTo: kimmo.hamalainen at nokia.com ReportedBy: jheather at zoo.co.uk QAContact: startup-shutdown-bugs at maemo.org EXPECTED OUTCOME: Add fsck of root filesystem prior to chroot to it ACTUAL OUTCOME: STEPS TO REPRODUCE THE PROBLEM: Set to boot from external mmc. Boot then remove card - leaving filesystem with repairable minor inconsistencies. Then boot of the card again. OTHER COMMENTS: I must say it is pleasing that the N800 needs none of the shennanigens that (apparently) the N770 needed to boot off the mmc. Simply setting the persistant boot device in the config area of the flash allows a .ext2 formatted mmc to be booted. (I think maybe I should point this out on the forums etc) HOWEVER, the initrd linuxrc SHOULD NOT pass operation over to the filesystem without running fsck -p on it. Failure to do so will happily turn a minor inconsistency into major filesystem corruption. No doubt the code was written with the jffs2 filesystem in mind, where it it unnecessary. Really you should follow the usual linux practice of mounting the unchecked root readonly so you can get at the right fsck and then remounting readwrite (after a reboot if any problems are fixed) only when fsck -p returns with no problems. Oh, yes, and drop into a shell if there are still unfixed problems after the first go. -- Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
- Previous message: [hafqa] [Bug 1204] MMC read-only/corruption bug persists...
- Next message: [hafqa] [Bug 1204] MMC read-only/corruption bug persists...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]