SATA not recognised after kernel upgrade VFS: Can't find ext3 filesystem on dev sda1.
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
SATA not recognised after kernel upgrade VFS: Can't find ext3 filesystem on dev sda1.
# mount /dev/sda1
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
# dmesg | tail
VFS: Can't find ext3 filesystem on dev sda1.
VFS: Can't find ext3 filesystem on dev sda1.
VFS: Can't find ext3 filesystem on dev sda1.
VFS: Can't find ext3 filesystem on dev sda1.
VFS: Can't find ext3 filesystem on dev sda1.
VFS: Can't find ext3 filesystem on dev sda1.
VFS: Can't find ext3 filesystem on dev sda1.
VFS: Can't find ext3 filesystem on dev sda1.
# fdisk -l
Disk /dev/hda: 10.2 GB, 10205282304 bytes
255 heads, 63 sectors/track, 1240 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 1182 9494383+ 83 Linux
/dev/hda2 1183 1240 465885 5 Extended
/dev/hda5 1183 1240 465853+ 82 Linux swap / Solaris
Disk /dev/hdb: 164.6 GB, 164696555520 bytes
255 heads, 63 sectors/track, 20023 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 20023 160834716 83 Linux
Disk /dev/hdd: 10.0 GB, 10005037056 bytes
255 heads, 63 sectors/track, 1216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdd1 * 1 1215 9759456 7 HPFS/NTFS
Disk /dev/sda: 2087 MB, 2087976960 bytes
28 heads, 27 sectors/track, 5394 cylinders
Units = cylinders of 756 * 512 = 387072 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 5395 2038921+ 6 FAT16
Disk /dev/sdb: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 14946 120053713+ c W95 FAT32 (LBA)
Disk /dev/sdc: 257 MB, 257949696 bytes
16 heads, 32 sectors/track, 984 cylinders
Units = cylinders of 512 * 512 = 262144 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 984 251887+ 6 FAT16
Partition 1 has different physical/logical endings:
phys=(982, 15, 32) logical=(983, 15, 31)
Any more files people need to lend me a hand, i'll be happy to oblige. I've searched google for a few hours now and haven't found anything that I can understand to help fix the problem.
# uname -a
Linux atlas 2.6.25 #1 SMP Sat May 10 13:02:30 BST 2008 i686 GNU/Linux
I'm not sure where youve found a Debian 2.6.25 kernel But I'm running Debian Etch (upgraded repositories to testing) and latest kernel is
anc@slave:~$ uname -a
Linux slave 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 GNU/Linux
2.6.24. Try changing all repositories to testing, an try the 2.6.24 kernel.
I have a single SATA drive in my Compaq nc6400 laptop.
To find out what module you are missing, one way is to load your 2.6.18 kernel and issue
lsmod > module2.6.18list
this will create a text file of your modules which you can read later. If you can load your system with your 2.6.25 kernel you could create a similar
list; however I dont think your system boots with that kernel, so its going to be difficult.., try 2.6.24 kernel first.
Even if you did a kernel update, you still have to make sure the require modules are included in the initrd file. The initrd file is saved in a gzip file. A utility to help you make an initrd file is mkinitrd. There are others too that are proprietary to your own distribution.
What you are missing is the EXT3 module. You could also be missing the SATA module too. I think it is ata-piix.
I suggest always do make oldconfig when upgrading the kernel. Then use make menuconfig to double check the options then compile. This will make sure you have the options of your present kernel for your upgrade kernel.
I found out a little more. Aparantly, the SATA support is depreciated and there's a new experimental Serial ATA driver. I've enabled that (using my old config, then using menu config as suggested) and it is compiling again.
It seems that since its depreciated, menuconfig removes the depreciated sata option from the config but doesn't enable the new one.
Seems to work nicely for sound, graphics, CPU, smp everything but sata. I'm recompiling now with extra options enabled and i'll report back on successes and failures.
Thanks for your help so far.
Edit:
Enabling the new options didn't work... Time to try the old (depreciated) sata option now. Another re-compile x.x
Ah screw it. I'll pick it back up in the morning, i'm half asleep now. If anyone has any brainstorms, i'd apreciate knowing =]
Edit2:
I think I found the option I need to enable:
Intel ESB, ICH, PIIX3, PIIX4, PATA/SATA Support
Recompiling.
Last edited by mariofreak; 05-11-2008 at 06:31 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.