**** BEGIN LOGGING AT Wed May 05 02:59:56 2010 May 05 07:57:11 Is there a way to check ext2/ext3 filesystems from busybox before the root filesystem is mounted? May 05 07:57:57 Busybox I'm currently using only has fsck and fsck.minix. I suppose I need to add a fsck.ext2 to it, but I don't know how to do it. May 05 08:05:27 youll have to see if it has a config option for fsck.ext2 May 05 08:05:54 * XorA suspects though that your meant to use the big boys version May 05 08:06:14 The big boys version? :| May 05 08:06:25 e2fstools version May 05 08:07:23 But e2fstools binaries can't be used before mounting the root filesystem, right? May 05 08:07:46 nor can busybox it its on the rootfs May 05 08:07:59 normally you mount ro, do the fsck, then remount rw May 05 08:08:48 and the scripts in Angstrom should handle this May 05 08:10:27 OK... I'm trying to check the root filesystem each boot. Could you please point me the easiest way to do it?. I tried the /forcefsck trick, but it looks like Angstrom scripts just ignore that file. Then I tried to add a fsck command in the "mountall.sh" script but it needs e2fsck... May 05 08:11:11 is mountall.sh a good place to add the e2fsck line? May 05 08:14:01 if you install e2fstools-fsck it should do a fsck on every boot May 05 08:14:11 but it will only do a full fsck every 30 days May 05 08:14:22 unless someone broke the init scripts May 05 08:16:51 OK, thanks a lot, I'll try bitbaking e2fstools. May 05 08:18:05 Just another question. The "fast" fsck Angstrom is supposed to do each boot, can correct problems if the filesystem is not cleanly unmounted? Or do I need to do a full fsck? May 05 08:21:20 erm, I dont remeber exactly what scripts do, but Im sure they used to do full fsck on unclean fs May 05 08:21:38 but someone might have changed since then, Ive been using flash storage so long now May 05 08:22:23 OK, again, thanks a lot. I'll browse the scripts and try to figure out how it works. (I hope I can figure it out, I'm still a Linux noob). May 05 09:19:41 It looks like the init scripts don't check the root filesystem anymore. I installed e2fsprogs-e2fsck, and filesystem doesn't get checked at boot. Even shutting down the system with "shutdown -rF now" doesn't seem to work :( May 05 09:20:11 I'll have to browse the init scripts and figure out how to check the filesystem. May 05 09:22:53 Or maybe it's quietly checking the filesystem and doesn't print anything to the console... May 05 10:44:02 hello, is there some possibility to integrate ipkg (opkg) to console environment to Angstrom? May 05 10:51:18 You only have to install ipkg May 05 10:53:04 If you use OpenEmbedded, you can add "ipkg" to your IMAGE_INSTALL packages May 05 10:53:05 ok, but how? i have not any packaging system in the donloaded archive May 05 10:53:48 i have Angstrom May 05 10:53:54 If you do not use OE, I suppose you can download a precompiled package and install it to the root filesystem manually May 05 10:59:36 ok, i hoped there can be other way than install it manually May 05 10:59:40 thanks May 05 10:59:46 np May 05 11:04:38 I'm having all kind of problems trying to check the filesystem at boot. To get fsck to start each boot, I set 'ENABLE_ROOTFS_FSCK=yes' in /etc/defaults/rcS. Then I edited fstab to change filesystem type to 'ext3' instead of 'auto'. May 05 11:06:42 Now fsck starts each boot, but when I uncleanly shut down the system, e2fsck fails because dunno why, the rootfs doesn't get remounted read only. May 05 11:25:14 I think my problem is '/' gets mounted twice (even though it's only once listed in fstab). It gets mounted as 'rootfs on /' and as '/dev/root on /' How can stop this happening? May 05 11:26:45 It gets even mounted a third time as '/dev/mmcblk0p2 on /media/mmcblk0p2' :( May 05 11:29:30 Is there an automounter daemon or something I can disable to prevent this happening? May 05 11:39:04 In other words, Who mounts 'rootfs on /', as it is not in fstab? May 05 13:31:08 Well, FINALLY I got fsck to start every boot. Here are the steps I followed if anyone wants to follow them: May 05 13:31:56 1.- edit /etc/defaults/rcS and set 'ENABLE_ROOTFS_FSCK=yes' May 05 13:33:45 2.- edit /etc/fstab and leave the first line like this '/dev/mmcblk0p2 / ext3 defaults 1 1' (note I changed rootfs with /dev/mmcblk0p2 and auto with ext3) May 05 13:34:18 3.- create an empty /forcefsck file May 05 13:35:32 4.- And now, this is the trick that took me all the day to figure out: edit /etc/udev/mount.blacklist and add two lines: '/dev/root' and '/dev/mmcblk0p2' May 05 13:36:02 Now it's working every boot, and the root filesystem does get mounted only once May 05 13:36:15 :) May 05 13:45:43 doragasu: why can't you use a more robust filesystem (like a journalling filesystem for example) May 05 13:48:44 Noob question: Aren't journalling filesystems very slow? May 05 13:49:41 Could you recommend me a filesystem? May 05 13:49:53 (now I'm using ext3) May 05 14:18:57 doragasu: ext3 is a journalling filesystem... May 05 14:19:40 May 05 14:24:58 they are slower than non-journaling filesystems May 05 14:25:30 Not always. May 05 14:26:00 With appropriate hardware they can be a massive speed win. May 05 14:27:15 not really, the best they can do is equal a non-journaling fs May 05 14:27:23 and i doubt most devices running angstrom are going to have the hardware for even that ;) May 05 14:28:11 No, they can help a lot by converting a very seeky write pattern into a streaming write pattern (which is normally nicer for the disk). May 05 14:39:09 Anyway, for me ext3 is OK, I only needed to check the filesystem each boot to correct unclean shutdowns. May 05 14:57:29 doragasu: you do realise ext3 corrects unclean shutdowns without fsck May 05 15:04:22 that's the point May 05 15:04:54 the problem I had is I wasn't able to make Angstrom check the root filesystem on boot. May 05 15:05:07 sorry May 05 15:05:15 I misread your statement May 05 15:05:25 forget the last I wrote May 05 15:05:55 so you say ext3 corrects corrupted files because of a unclean shutdown even without using fsck? May 05 15:19:19 doragasu: yes, thats the whole point of a journaling filesystem May 05 15:19:46 doragasu: im my expereince if journal replay doesnt fix it, then unattended fsck wont either May 05 15:20:18 doragasu: yes it is a journalling FS **** ENDING LOGGING AT Thu May 06 02:59:56 2010