lsmod # show modulesĪs far as I know ext2 modules are already loaded by default. Check if there is a module for that filesystem and it is loaded. If, after you specified -t, you get a problem like that, it is very likely that the kernel cannot mount the requested filesystem for you. dev/mmcblk0p3 on /media failed: No such device?
Why does mount -t ext2 /dev/mmcblk0p3 /media cause mount: mounting The kernel can probably mount the filesystem, but it wrongly guess its type. dev/mmcblk0p3 on /media failed: Invalid argument? Why does $ mount /dev/mmcblk0p3 /media cause mount: mounting Why does mount -t ext2 /dev/mmcblk0p3 /media cause mount: mounting /dev/mmcblk0p3 on /media failed: No such device?.Why does $ mount /dev/mmcblk0p3 /media cause mount: mounting /dev/mmcblk0p3 on /media failed: Invalid argument?.The kernel version is 2.6.32-17-ridgerun with BusyBox v1.18.2. An Ubuntu 10.04 desktop system has been used to verify that the partition type is ext2 and is able to mount the SD card partition but this needs to work on the embedded Linux target.
I need to change from FAT32 to ext2 since the FAT32 partition 3 is too easily hosed in this embedded Linux target (power cycle, USB mass storage disconnects, etc.). Mount point /media definitely exists and $ mount /dev/mmcblk0p3 /media works fine when mmcblk0p3 is a FAT32 FS on a Win95 FAT32 partition. Fdisk is used to create mmcblk0p3 on the 64G SD card.
0 kommentar(er)
