Rajko M. schreef:
On Monday 12 April 2010 13:34:51 Oddball wrote:
Oddball schreef:
...
AMD64x2-sfn1:/home/oddball # uname -r 2.6.27.29-0.1-default AMD64x2-sfn1:/home/oddball # grep -i ext4 /boot/config-`uname -r` CONFIG_EXT4DEV_FS=m CONFIG_EXT4DEV_FS_XATTR=y CONFIG_EXT4DEV_FS_POSIX_ACL=y CONFIG_EXT4DEV_FS_SECURITY=y AMD64x2-sfn1:/home/oddball # modprobe --list ext4dev /lib/modules/2.6.27.29-0.1-default/kernel/fs/ext4/ext4dev.ko AMD64x2-sfn1:/home/oddball # modprobe -v ext4dev insmod /lib/modules/2.6.27.29-0.1-default/kernel/lib/crc16.ko insmod /lib/modules/2.6.27.29-0.1-default/kernel/fs/jbd2/jbd2.ko insmod /lib/modules/2.6.27.29-0.1-default/kernel/fs/ext4/ext4dev.ko AMD64x2-sfn1:/home/oddball #
There is no complain from modprobe and that means the driver is loaded.
I would recommend to check is driver really loaded after modprobe or it is crashing later when you try to use it.
Right after the modprobe -v ext4dev run lsmod | grep -i ext4 to see is driver loaded.
Then if you see the driver try to mount hard disk: mount /dev/sda11 /mnt and then run again: lsmod | grep -i ext4 to see is driver still in place.
If it is, then try to see content. If you can't then run again: lsmod | grep -i ext4
As mentioned I used it and it worked fine. The main difference, so far I recall, is that I don't have so many partitions.
If you see kernel update from regular update repo then do it, but make sure that zypper will keep old kernel. Set option: multiversion = kernel-default in /etc/zypp/zypp.conf which will preserve your old kernel, and make possible to boot the old one, if new fails.
AMD64x2-sfn1:/home/oddball # modprobe -v ext4dev insmod /lib/modules/2.6.27.29-0.1-default/kernel/lib/crc16.ko insmod /lib/modules/2.6.27.29-0.1-default/kernel/fs/jbd2/jbd2.ko insmod /lib/modules/2.6.27.29-0.1-default/kernel/fs/ext4/ext4dev.ko AMD64x2-sfn1:/home/oddball # lsmod | grep -i ext4 ext4dev 223264 0 jbd2 72432 1 ext4dev crc16 2344 1 ext4dev mbcache 9484 3 ext4dev,ext2,ext3 AMD64x2-sfn1:/home/oddball # mount /dev/sda11 /mnt AMAMD64x2-sfn1:/home/oddball # modprobe -v ext4dev insmod /lib/modules/2.6.27.29-0.1-default/kernel/lib/crc16.ko insmod /lib/modules/2.6.27.29-0.1-default/kernel/fs/jbd2/jbd2.ko insmod /lib/modules/2.6.27.29-0.1-default/kernel/fs/ext4/ext4dev.ko AMD64x2-sfn1:/home/oddball # lsmod | grep -i ext4 ext4dev 223264 0 jbd2 72432 1 ext4dev crc16 2344 1 ext4dev mbcache 9484 3 ext4dev,ext2,ext3 AMD64x2-sfn1:/home/oddball # mount /dev/sda11 /mnt AMD64x2-sfn1:/home/oddball # lsmod | grep -i ext4 ext4dev 223264 1 jbd2 72432 1 ext4dev crc16 2344 1 ext4dev mbcache 9484 3 ext4dev,ext2,ext3 AMD64x2-sfn1:/home/oddball # D64x2-sfn1:/home/oddball # lsmod | grep -i ext4 ext4dev 223264 1 jbd2 72432 1 ext4dev crc16 2344 1 ext4dev mbcache 9484 3 ext4dev,ext2,ext3 AMD64x2-sfn1:/home/oddball # I have visual on the ext4 partition now.. It is slow, and i do not know the pathdepth yet, but it mounts! Thank you very much for your help.. It will be much easier now to get to the logs i need.. Btw, Stefan Dirsch was able to tackle the 'X' problem...it is not perfect yet, but i have visual there also... -- Enjoy your time around, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 103" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org