When I try to boot to OpenSUSE I get the following error during boot-up: unknown filesystem type 'reiserfs' could not mount root filesystem - exiting to /bin/sh$
This only started happening quite recently - before this I could boot to Linux quite happily.
Formated new drive with ext3 on external drive on Suse 11.1 When upgraded to 11.2, drive was not connected... Could not get mounted after that... Set up another boot drive, could not get to mount. Found post with following:
>cryptsetup luksOpen /dev/sde1 restore
>mkdir /restore
>mount /dev/sde1 /restore
Error as follows: mount: unknown filesystem type 'crypto_LUKS' Have also got to another point where superblock was incorrect. I can use terminal, but am not a linux guru... Have looked at other posts under luks, but can not find a solution.
I recently upgrade my armel NAS from etch to squeeze. During the partitioning step of the installation I intentionally left unmounted the data partition (900GB formatted XFS) but after the installation I'm not able to mount it.
I edited the fstab file adding the last line
And tried a mount but I get the message
So i noticed throught lsmod that I don't have the module for xfs
Tried installing xfsprogs but it didn't helped. So I searched for xfs-modules but seems it doesn't exists for armel architecture. Am I right? What does it means? That XFS is not supported in armel Squeeze? Assumed I can't transfer/backup 900GB of partition, is there a way to convert it on-the-fly to a supported filesystem format?
I dont know anything about linux and just been assigned to amount a drive to it. here's what i did so far: Version of Linux using Red Hat Enterprise Linux Server release 5.3 (Tikanga) [root]# mount -t auto /dev/sdb1 /tmp/archive mount: unknown filesystem type 'ntfs'
when checking the /proc/filesystems, i noticed that 'ntfs' is not listed there, several forum suggested i try running 'modprobe ntfs'. If that is not found, you'll need a kernel with ntfs support. i'm so lost, where to i get the modprobe ntfs
I installed Ubuntu Server 9.10 in a virtual machine, and I'm trying to install the VMware Tools but I can't mount the installer CD: $ sudo mount /dev/scd0 /media/cdrom mount: unknown filesystem type 'iso9660'
View 1 Replies View RelatedI had windows with ntfs I installed ubuntu. All ok. Gurb with 2 os, can ran windows and ubuntu and can mount ntfs partition in ubuntu I installed debian with lvm over ubuntu partition. I can't mount ntfs partition now, and windows doesn't appears in gurb
# mount /dev/sda1 /mnt/windows/
mount: unknown filesystem type 'LVM2_member'
# pvs --all
PV VG Fmt Attr PSize PFree
/dev/dm-1 -- 0 0
/dev/dm-2 -- 0 0
/dev/root -- 0 0
[Code]....
I can't active vg because haven't name, but is not lvm, is only ntfs partition Maybe ubuntu puts in lvm and grub? Any idea? If I change with fdisk to ntfs i lose all the information in the partition?
[Code]...
i am trying to compile kernel 2.6.23 on Fedora 12 After fixing a few bugs (getline error, %dil ,etc) i was able to compile the kernel made initramfs img using dracut updated grub and then booted up the new kernel 2.6.23 but it fails to boot with following error mount: unknown filesystem type 'ext4'
View 8 Replies View RelatedI just updated Fedora 14 with the updates it downloaded and I am now stuck with the error.
View 10 Replies View RelatedI am trying to mount a file image, like this
mount -o loop /tmp/apps.img /media/apps
But I get the following:
mount: you must specify the filesystem type
I try ext3:
mount -o loop /tmp/apps.img /media/apps -t ext3
dmesg says:
error: can't find ext3 filesystem on dev loop6.
I've also tried ext2, vfat etc. How can I detect the filesystem type of apps.img?
I am running 11.2, kde4. The day before yesterday, the system updated and I think there was kernal update within that. I had no problems immediately afterward. Then I did a total shutdown for the night, and turned it back on yesterday only to find this:
Mount: wrong fs, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error
In some cases useful info is found in syslog--try dmesg | tail or so
Could not mount root filesystem--exiting to /bin/sh
sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell
$
Besides the last updates from the other day, I did nothing out of the ordinary, no downloads or any system/configuration tweeks. Will I have to reinstall opensuse? or is there a way to reclaim my previous setup--or at least reclaim my files and documents? I'm running off of the 11.2 livecd.
I have opensuse 11.3 installed, and my motherboard has the intel i845 chipset,
one day windows had enough of the intel graphics chip and would not let me have anything but 640x480 pixels, well you cant do much with that so I put an ati card in and disabled the intenal graphics. windows was happy enough but suse could not boot - more specifically could not mount the root filesystem, saying it had errors (did a very quick fsck), could not find the journal, and I had a bad superblock. the "failsafe kernel" was no better. If I take the ati card out suse boots fine. however I do swap frequently between windows and linux and changing graphics cards between boots is somewhat irritating.
I changed the first line of /etc/fstab in an attempt to get rid of an annoying message "mount: unknown filesystem type 'static'". All I did was put a "#" on the first line .... changing the original from:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
to:
#
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
I have tried desperately to get to the file system so that I can edit that first line in fstab out but nothing works and the file system comes up as read only ...
I have a following problem: Recently my drive with Ubuntu 9.4 has mysteriously stopped working, i.e. when I switch the computer on it informs me that GRUB didn't find the filesystem. Well, I suppose it happens.
First, I though it was due to the drive dying, but I popped it in an external enclosure and HDTune told me the drive was fine. Wanting to recover the files on the drive before reinstalling I first tried to mount it in said external enclosure under Windows (I have Win Ext2 driver installed which used to work just fine). This time, however, drive gets assigned a letter but upon opening it Windows popped up an error saying that the drive was not formatted and whether I would like to format it then.
Unfazed by this streak of failures I tried to mount it under Linux but, alas, to no avail. I might have tried every single -t operator under mount command but it still won't budge and let me mount.
I have download file from this site and have done these steps [URL].
tar -xvf ntfsprogs-2.0.0.tar.gz
chown root.root -R ntfsprogs-2.0.0
cd ntfsprogs-2.0.0
./configure
make && make install
Still I have failed to mount ntfs partition with this command..
mount -t ntfs /dev/hda1 /mnt
or
ntfs-3g /dev/hda1 /mnt
The error is .................
mount: unknown filesystem type 'ntfs'
I am using RHEL5.4 and kernel is 2.6.18-164.el5
I'm trying to mount an external DVD +RW Drive so I can burn a directory from my Linux Server to disk. I think I've figured out how to mount the drive, but it only works when there's a disk with data in the drive. When I enter mount /dev/scd1 /mnt I'm able to read from the drive, no problem. When I try to do the same thing, however, with a blank disk I get the following message: "mount: you must specify a filesystem type" So I'm assuming I need to prepare the disk somehow. I've verified that the dvd+rw-tools package is installed on the RH server but I'm not sure what the next step is.
View 4 Replies View RelatedI just got an Acer netbook Aspire One. I put the Ubuntu remix on it successfully, and was using it for several days without problems. Now all of a sudden when I turn on my computer I get a grub error message with a command prompt. I've tried following the direction to restore grub but I'm getting stuck right away on the command to mount my ubuntu partition. After I type "sudo mount /dev/sda4 /mnt", I keep getting the error message "mount: you must specify the filesystem type."
View 3 Replies View RelatedHave been running 11.1 on a generic notebook (eRacks) just fine until a few days ago when CUPS couldn't be reached. Rather than futz more with 11.1, I decided to install 11.2 (which has been on my desktop). Using the same CD, which continues to check ok, the install has failed many times at about the same point: 87% through "copying root filesystem" in yast2.
Specs: Intel P4 2.4 GHz, 1.5 GB RAM, ATI radeon PV250Lf
The HD was partitioned into /, swap, /home, and an extended partition of /opt, /var, /usr. Only / was ext4 and the rest were ext3. Tried various options:
* no apic
* no acpi
* "noapic acpi=off" entered manually
* Vesa instead of 1024x768
Each time had to edit partition table to mount the extended partitions. Always formatted /. At first didn't format the extended patitions, later formated all but /home. Then set yast2 to format / as ext3, to match the other partitions. In the sysinfo page the / partition is now shown as /mnt containing 723.6 MB out of 7 GB, still formatted as ext4. On rescan by yast2 partition manager, / shows as ext3. The install halts every time with an error while "copying root filesystem." Tried booting from the CD direct to install and to the Live OS followed by install--same result. So, hours later, went back to 11.1--which installed in minutes.
I have a dual booting newly installed 64 bit Ubuntu 9.10 on my machine. It was all fine until today. Now when I boot into Ubuntu, I see the error Failed to mount root filesystem. I cant remember any significant changes during the last session. One thing I remember is I upgraded the system using the update manager which asked me to choose an option for grub boot loader. I opted for its upgradation. After the upgrade, I was able to work with Ubuntu for a few more sessions. Windows XP works very fine.I checked other threads which suggested running fsck, but it did not help. fsck does not report any errors.
View 1 Replies View RelatedI am using GRUB bootloader. I can boot into windows fine. But booting into linux gives me the error "kernel panic: unable to mount root fs on unknown block(0,0)I got LILO to load linux fine but GRUB always gives me this error regardless of the linux OS for this particular computer.
View 11 Replies View RelatedI have successful tar an existing CentOS 5.2 partition from Fefora10. The idea is to move a working CentOS 5.2 reside in an internal hard drive to a portable hard drive. I know how to edit a stencil in menu.lst to boot the clone CentOS5.2. During boot, I encountered
Red Hat nash version 5.1.19.6
mount: could not find filesystem /dev/root
setuproot: moving /dev failed No such file or directory
setuproot: mounting /proc: No such file or directory
setuproot: mounting /sys: No such file or directory
[Code]...
I am experiencing a problem with virtual box 4. Did an install from binary, and everything went ok and virtual box launches, but once I have created the virtual disk and the want to run it, I get an error, and the log says that it has to do with the ext4 filesystem and has a known kernel bug. How does one go about sorting this out. Here with the log from virtual box.
00:00:00.654 VirtualBox 4.0.4 r70112 linux.x86 (Feb 17 2011 17:29:29) release log
00:00:00.654 Log opened 2011-03-22T15:50:28.174435000Z
00:00:00.654 OS Product: Linux
00:00:00.654 OS Release: 2.6.34.7-0.7-desktop
00:00:00.654 OS Version: #1 SMP PREEMPT 2010-12-13 11:13:53 +0100
00:00:00.654 DMI Product Name: HP Pavilion dv6700 Notebook PC
00:00:00.654 DMI Product Version: Rev 1
00:00:00.655 Host RAM: 1988MB RAM, available: 1595MB .....
Then tried moving the vbox files to my home partition which is ext3, but it says that file system is unknown, again herewith log:
00:00:00.589 VirtualBox 4.0.4 r70112 linux.x86 (Feb 17 2011 17:29:29) release log
00:00:00.589 Log opened 2011-03-22T16:06:15.412283000Z
00:00:00.589 OS Product: Linux
00:00:00.589 OS Release: 2.6.34.7-0.7-desktop
00:00:00.589 OS Version: #1 SMP PREEMPT 2010-12-13 11:13:53 +0100
00:00:00.589 DMI Product Name: HP Pavilion dv6700 Notebook PC
00:00:00.589 DMI Product Version: Rev 1
00:00:00.590 Host RAM: 1988MB RAM, available: 1476MB .....
Running F12 on my compaq evo N410c. Did a system restart 4rm gnome logged in as root & now grub cant mount my root filesystem, it boots vista though. How do i rectify dis.
View 2 Replies View RelatedI have just tried to update my kernel from 2.6.24.5 to 2.6.39-rc3 on a Slackware 12.1 distribution. I have successfully updated the kernel before, but it was from a newer distribution and newer kernel(Slackware 13.1 and 2.6.33.4). After I updated and rebooted, I got the following error:
Code:
List of all partitions:
0300 4194302 hda driver: ide-cdrom
0800 312571224 sda driver: sd
0801 244197560 sda1 00000000-0000-0000-0000-000000000sda1
0802 68372640 sda2 00000000-0000-0000-0000-000000000sda2
No filesystem could mount root, tried: romfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (8,1)
Pid: 1, comm: swapper Not tainted 2.6.39-rc3-smp #1 .....
I am a linux semi-noob who just got the idea that it would be fun to play with Arch Linux.I was dual-booting Windows and OpenSuSE, and I installed Arch by shrinking the Windows partition and putting a new logical partition in between the windows partition and the swap partition I already have.Unfortunately, opensuse still thinks that its root filesystem is on /dev/sda7 so it fails to boot b/c it is looking at an ntfs filesystem that I used for document sharing.If someone has a solution, that will save me from having to reinstall opensuse.
View 5 Replies View RelatedI have been having problems with filesystem corruption on my eeepc 1000H for a long time now. I have tried using different filesystems, kernels and distributions (arch, slackware) to no effect. I am starting to grow suspicious that this problem lies somewhere else, as I haven't seen anyone else having similar problems in such a variety of scenarios.
I have tried testing my ram using memtest86+, didn't come up with anything after a full run through. I also have tried using e2fsck -c to check for bad blocks, it finds none. I had a go at using smartctl but wasn't really sure what I was doing. I did a long test and it came up with nothing anyway.
This problem is in addition to the problems I've been having with my intel graphics chip and KMS. A lot of the time there are lockups when booting into X, which can only be gotten out of by a hard reset. This is sometimes what causes the original filesystem errors. I've stopped messing around with KMS for now to eliminate this but my current system in unbootable. I'm guessing my disk is wrecked but have as yet seen no definitive proof. Can anyone recommend anything that I should do?
I am currently on ext4 with a custom kernel 2.6.33-rc6 (the stock kernel shipping with slackware does not have the elantech extension for psmouse included). When I was using arch, I was just using the stock kernels.
I upgraded from 9.10 to 10.04 and during the upgrade it asked to install a new version of grub or keep the current one. Thinking that I should just upgrade the grub just to make sure that I had the latest version I decided to do it. So I told it the partitions to use the ubuntu, ubuntu swap, vista, and vista recovery.Finished the upgrade and restarted.I tried to boot into both the vista, and vista recovery but I noticed something weird. Grub switched the names, the actual vista install is called recovery, and when you tried to load it, a blinking cursor would appear for a split second and then loop back to grub. If you tried to select the vista recovery now called vista it would just sit at the blinking cursor for infinity. But booting into ubuntu worked.
So I decided to wipe ubuntu and do a fresh install of 10.04. Went through and set up the swap and ext4 partitions at the end of the hard drive(because I would like to expand the windows directory should I ever be able to boot into it). Now when I start up and select vista recovery now called vista it sits at the blinking cursor just as before.
My Fedora 12 System was failed when booting.The message like that : mount: wrong fs type, bad option, bad superblock on /dev/mapper/my_vol missing codepage or helper program, or other error. In some case, useful info is found in syslog - try dmesg | tail or so Can't mount at root filesystem. [drm: drm_mode_rmfb ] *ERROR* tried to remove a fb that we didn't own. Boot has failed, sleep forever. I guess something wrong with my hard disk, so the bootloader can't recognize the filesystem type.
View 2 Replies View RelatedI'm trying to boot Emdebian Grip 1.0 built on Compact Flash on a mini PC with grub2 as bootloader. Unfortunately , the booting is unsuccessful and I got stuck into an error message :Code:No filesystem could mount root , tried : minix msdos iso9660kernel panic - not syncing : VFS : Unable to mount root fs on unknown-block (22,1)It seems grub2 hasn't tried to mount ext2 as the filesystem and my Compact flash is formatted as ext2. Here is the menuentry of the grub.cfg :
Code:
menuentry "Debian GNU/Linux, linux 2.66.2.9-custom" {
insmod ext2
[code]...
I had a LiveUSB of CentOS 5.5, so I decided the install it.With no installer,I just copied the files to my hard drive.his was in a multi boot with Windows 7, Ubuntu 9.10, and FreeDOS.I updated GRUB2 and it detected CentOS. I loaded my entry and it failed to mount the root filesystem.I took the initrd0 file from the LiveUSB syslinux folder and added that ramdisk to the entry. Now it finds the root filesystem (/dev/sda9 as Ext3).But it fails shortly after loading /sbin/init. It talks about an init error where it says "File not found!!!".The previous lines involved umounting old filesystems, like /dev.
View 4 Replies View RelatedA friend of mine upgraded his pc to ubuntu 10.04. Sadly enough we ran into issues with his graphics card, which apparently doesnt work well with lucid. We decided to downgrade to 9.10. I did this by installing over the old partition and chose to import the settings from the old account.The problems started when the pc booted for the first time:The list of kernels in grub2 was the one from 10.04.Somehow grub2 from the old installation seems to be still around and messes everything up. Any ideas how I could fix this?
View 6 Replies View Related