HI Mulyadi , Please find below my */proc/mounts* and */etc/fstab* files detail:
*mounts:* rootfs / rootfs rw 0 0 none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 none /proc proc rw,nosuid,nodev,noexec,relatime 0 0 none /dev devtmpfs rw,relatime,size=1944452k,nr_inodes=486113,mode=755 0 0 none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 /dev/disk/by-uuid/6ef7b91e-7416-4908-97ba-bfb212081a68 / ext4 rw,relatime,errors=remount-ro,barrier=1,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 none /sys/kernel/security securityfs rw,relatime 0 0 none /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0 none /var/run tmpfs rw,nosuid,relatime,mode=755 0 0 none /var/lock tmpfs rw,nosuid,nodev,noexec,relatime 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0 gvfs-fuse-daemon /home/vivekp/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 *fstab* # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/sda1 during installation UUID=6ef7b91e-7416-4908-97ba-bfb212081a68 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=115ae7e6-e27b-4577-9eb1-ab18ecf83877 none swap sw 0 0 Thanks Vivek On Wed, Oct 17, 2012 at 3:56 PM, Vivek Panwar <[email protected]>wrote: > > Hi Mulyadi, > > I did some googling and found one clue that i have to change file system > in menuconfig file for EXT4 , which support both EXT2 and EXT3 as well, > so for that i have enable below features in file systems... > > # CONFIG_EXT2_FS=n > # CONFIG_EXT3_FS=n > > CONFIG_EXT4_USE_FOR_EXT2 3=Y > > After these modifications i crossed earlier error but hit back with 2 new > errors , below is the description: > > 1) EXT4-fs(sda2): could not mount as ext3 due to feature incompatibilities > EXT4-fs(sda2): could not mount as ext2 due to feature incompatibilities > udevd[1075]:error creating queue file > init: udev mian process 1075 terminated with status 1 > init: udev main process ended , respawing > init: udevmonitor main process 1080 terminated with status 2 > > > 2) init: plymouth main process(1038) killed by SEGV signal *(This error > happens ones i skip mounting process)* > > > Can you please elaborate the procedure to update file system or correct me > if i am doing wrong ? > > Thanks for your support > > > Thanks, > Vivek > > > > > On Tue, Oct 16, 2012 at 11:20 PM, Mulyadi Santosa < > [email protected]> wrote: > >> Hi.... >> >> On Tue, Oct 16, 2012 at 12:34 PM, Vivek Panwar >> <[email protected]> wrote: >> > Hi Mulyadi, >> > >> > Below is the kernel panic logs i am getting, for your analysis: >> > >> > [0.820851] tg3 0000:02:00.0: Problem fetching invariants of chip, >> aborting >> > >> > [1.408713] EXT3 -f3 (sda1):error:could not mount because of unsupported >> > optional features (240) >> > >> > [1.449074] Kernel panic - not syncing : VFS: unable to mount root fs on >> > unknown -block(8,1) >> >> Seems like, you forgot to compile the filesystem support of your root >> filesystem. >> >> Try to check that...if the root fs (sda1, from what you wrote) is >> ext2, then check if ext2 module is made builtin or included in >> initrd/initramfs...and so on >> >> >> -- >> regards, >> >> Mulyadi Santosa >> Freelance Linux trainer and consultant >> >> blog: the-hydra.blogspot.com >> training: mulyaditraining.blogspot.com >> > >
_______________________________________________ Kernelnewbies mailing list [email protected] http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
