A colleague had troubles with a DVD that contains valuable data, no further backup available. The DVD won't run and I am trying to fix it. Have been playing around on Mac, Windows and Linux successively.
On Mac
Mac shows this message in Toast Titanium 10:
but Finder keeps telling it is an empty disc, no way to get to the files.
On Windows
Windows 7 in VMWare is not of any help.
On Linux
Just installed Ubuntu 11.04 (in VMWare) and did some checks using info on this forum. When trying to mount the disc, this is the error message. Then I used fdisk on the volume (/dev/sr0) and tried fsck. I downloaded UDFTools but cannot find any repair option like udffsck as described in this thread by the last author.
I am running out of inspiration... there are clearly data on the disc, which can be seen by just looking at its surface, but also the info on Mac. However, there might be some bad sector size in the partition table which renders it unreadable. How to recover these data?
I've just made the switch from Ubuntu to Debian Squeeze and am having trouble connecting external media (be it a USB stick or an ext HD). The error I am getting when I connect anything via usb is the following:
Error mounting: mount exited with exit code 1: helper failed with: mount: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
Ubuntu 10.04 has just failed to load from my hard drive, so I've resorted to booting from CD just to get the machine going.I'm wondering if my main boot drive has gone caput??When trying to mount it using DISK UTILITY...get the message: Error mounting volume
Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,missing codepage or helper program, or other error.In some cases useful info is found in syslog - try dmesg | tail or so
I have installed both Windows Xp and Fedora 12. Last time when i was working on Fedora it didn't shut down properly. Now following error occurs and finally the system sleeps.
ata1.00 : exception Emask 0x0 Sact 0x0 SErr 0x0 action 0x0 ata1.00 : BMDMA stat 0x25 ata1.00 : cmd c8/00:00:50:5a:34/00:00:00:00:00/e4 tag 0 dma 131072 1n res 51/40:7f:d1:5a:34//00:00:00:00:00/e4 Emask 0x9 (media error) ata1.00 : status : { DRDY ERR } ata1.00 : err : { UNC } end_request: I/O error, dev sda, sector 70539985 JBD : Failed to read block at offset 5884 EXT4-fs(sda): error loading journal mount: wrong fs type, bad option, bad superblock on /dev/sda8, codepage or helper program, or other error In some case useful info is found in syslog-ty dmesg | tail or so
I am trying to make a copy of the SD card that my TS-7800 SBC boots from. When I plug the SD into my opensuse pc I get this error. Error mounting: mount exited with exit code 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb4, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so There are four partitions on this card and I can only access one of them.
dmesg | tail gives me this
[894.422497] EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
when I do e2fsck -p /dev/sdb4 I get
e2fsck: Bad magic number in super-block while trying to open /dev/sdb4 /dev/sdb4: The superblock could not be read or does not describe a correct ext2 file system. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> I was hoping I could just plug in both cards and do this dd if=/dev/sdb of=/dev/sdc to copy everything and have a back up SD card.
I just installed Slackware 13.1 x86 on a new laptop (you probably remember me from my audio post). I am having one other issue. My root file system is formatted as EXT4. When my computer boots, it tries to mount it as EXT3 then EXT2, fails both types and then tries EXT4. Here are the messages.
Code: EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240) EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240) EXT4-fs (sda2): mounted filesystem with ordered data mode So, eventually / is mounted correctly, but I think this is slowing down my boot time. Does anyone know how to fix this.
I have been trying to mount an NFS share from my REHL server for over an hour, and Google was not able to help me. when I use the command:
mount -t nfs server3:/programs /programs
I get the folowing error :
mount: wrong fs type, bad option, bad superblock on server3:/programs, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program) In some cases useful info is found in syslog - try dmesg | tail or so
I am writing as yesterday, my fourth hard drive within 2 years crashed. Is that normal? One was crashing 2 years ago, one in winter 2009 and 2 just within 2 weeks. What can be the reason for so many crashes? I heard maybe the power supply? How can I find out if that's broken? The voltages at least in BIOS seem normal. The SATA controller? How do I know if its broken? Can I just but one PCI-E card with SATA adapters? Is it the motherboard? Theres not much more in my computer... As well, its wired that my good-old 160 GB drive never crashed, only constantly the bigger ones. Here some typical error code from mount and dmesg:
Code: mount: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error
I'm trying to mount hg2.iso, the Heavy Gear 2 iso image that I converted from hg2.nrg using nrg2iso, and this is what I keep getting: Code: bash-3.1# mount -o loop -t iso9660 hg2.iso /mnt/iso mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try demsg | tail or so
i used to have ubuntu 9.i decided to move to sabayon so i used the live cd to install it ,resize the ubuntu partition and use the remaining space for sabayon.while the resizing procedure i got an error(i dont have a copy of the error log file but i know it has something to do with an anaconda process).i aborted the installation and the result was an filesystem that couldnt be mounted.when i try to mount the hdd i get this:
Code: Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so and this is what i get from fsck: Code: $ sudo fsck -f /dev/sdb1 code....
I have a x64 OpenSUSE server with two hard drivers installed. The first one is used for the / and /home partitions and the other is for backups. Ironically enough it is the backup hard drive I am having trouble with. I was having trouble writting to the drive and unmounted it to preform a fchsk, however now when ever I try to mount it I get the following error:
mount: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
Does anyone know who I can repair the drive and retrive data?
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'
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:
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.
Unable to install Ubuntu 9.10 on a new internal harddrive. The hardrive contains no operating system. This hardrive is the only drive present in the system.
Whenever the installation trys to mount the ext4 partition the following error appears: The attempt to mount a file system with type ext4 in SCSI1 (0,0,0), partition #1 (sda) at /failed
Iv'e tried over and over to get past this error to no avail.
Just upgraded from 9.10 to 10.04 and cannot mount one of my partitions. It is encrypted / decrypted in the following fashion: Code: # dd if=/dev/random bs=4k count=1 | gpg -a --cipher-algo AES256 -c - > /mnt/usb/keys/fs.gpg # gpg -q -o - /mnt/usb/keys/fs.gpg | cryptsetup -v -h sha512 -c aes-xts-plain -s 512 create crypto /dev/md1 # mkfs.ext4 /dev/mapper/crypto # mount /dev/mapper/crypto /crypto
It has been this way for a long time, survived several release upgrades. Now when I decrypt it, I have to use gpg in one command to decrypt the key to a file, then use cat in a second command to pipe to cryptsetup, as such: Code: # gpg -q /mnt/usb/keys/fs.gpg # cat /mnt/usb/keys/fs | cryptsetup -v -h sha512 -c aes-xts-plain -s 512 create crypto /dev/md1
However, I can no longer mount the device: Code: # mount /dev/mapper/crypto /store/ mount: you must specify the filesystem type
This is how it's always been mounted. Well I know it's ext4, so I supplied that and was greeted with: Code: # mount -t ext4 /dev/mapper/crypto /store/ mount: wrong fs type, bad option, bad superblock on /dev/mapper/crypto, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
The only item in dmesg is: Code: [78.212761] EXT4-fs (dm-0): VFS: Can't find ext4 filesystem
I cannot for the life of me get my HD working again. I tried following all the various remedies I could find but to no avail.
Code: ubuntu@ubuntu:~$ sudo e2fsck -f /dev/sda1 e2fsck 1.41.4 (27-Jan-2009) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition?
Code: ubuntu@ubuntu:~$ sudo dumpe2fs -f /dev/sda1 | grep -i superblock dumpe2fs 1.41.4 (27-Jan-2009) dumpe2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Couldn't find valid filesystem superblock.
It goes on and one like this. I'm stuck using the LiveCD for now (Jaunty) so I have some limitations.
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'
I have been using truecrypt to mount a partition on my computer for a few months now. Yesterday I tried to access it and it failed, with the following error:" mount: you must specify the filesystem type "
When creating the partition, the filesystem type was set to ext2. Apart from yesterday, I have not accessed this partition for a number of days now, and have done nothing to the operating in system in the ways of changing settings and such for a good week.
I just loaded octave. I ran through a few examples of how to implement a script file. Everything works until I get to "plot". When I run the "plot" command I get the following.
octave:2> test1.m error: can't perform indexing operations for <unknown type> type sh: gnuplot: not found Just to double check my work, I ran the following code: y=[1 2 3]; plot(y);
I made the unfortunate mistake of doing this (sudo rm -r /bin) instead of (sudo rm -r bin) in the folder I was in..I'm trying to copy my data over from my Karmic system using mount, but I'm unable to mount. When I try to mount I get errors of an wrong fs type..
I've done fdisk -l & I get this: /dev/sda1 * 1 37599 302013936 83 Linux
What the heck filesystem is Linux? Is that like ext3 or something? I don't know. Here is what I'm trying to run: mount -t ??? /dev/sda1 /media/disk -o force
Also, besides that. If there a way I can fix my OS without having to do a reinstall? Or at least is there a way can backup my files? I have a 1tb external so that's not the issue.
sudo: pam_limits(sudo:session): wrong limit value 'unlimited' for limit type 'hard' Dec 28 22:42:29 yn54 sudo: pam_limits(sudo:session): wrong limit value 'unlimited' for limit type 'soft' Dec 28 22:42:29 yn54 sudo: pam_limits(sudo:session): wrong limit value 'unlimited' for limit type 'hard'
I tried to post this then couldn't find it anywhere, so I will try again. I am wondering if there is a way to determine what file system type was put on a volume when the file system was made? I have a MD0 device that wouldn't mount. I was receiving "wrong file system type" messages.
I tried df but this only works with mounted file systems correct? I am looking for a command to run on a drive/volume that is not mounted so I can figure out what file system is on it.
This time I was able to: mount /dev/md0 /mnt/storage without and entry in the fstab file. I then just entered mount and it displayed the file system as jfs.
Is there another way to determine the file system type?
I am having trouble mounting DVD+Rs. I get the following error whenever I try -mount: block device /dev/hda is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/hda, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so
I am having a dual boot system vista/ubuntu 9.04. Till recently whenever I wanted to access my vista partition I had to type in the administrative password. However, strangely, for last few days whenever I access the vista partition I don't need to type the password. The partition is just mounted and I can access the files. I would like to know the reasons and if possible to get back the previous situation (needing password to access the vista partition).
Sometimes when I plug in a USB flash drive, it is mounted to /dev/usb0 instead of /dev/drivename. This poses a problem for me because I have applications that depend on files I keep on flash drives, and having to frequently change the file paths is difficult. I haven't been able to find anything on this topic with a cursory search on Google or through the Debian reference. Heck, I don't even know what /dev/usb0 is (though I would like to learn, in the interest of being less of a noob). This is happening on a Squeeze system running Gnome, so I believe nautilus is what's responsible for auto-mounting my flash drives.
Beyond that, I don't know what other information I should provide; if you need to know something else, ask me (and perhaps tell me how to access that information). Someone on IRC suggested that I didn't have my drives set to mount in /dev/, but I have no idea how I would go about fixing that. If there's a configuration file that deals with this sort of thing, chances are I haven't touched it since installing this system. Debian installer sees usb drive as cd drive, so it adds it in fstab, but with wrong file system options (udf,iso9660) which is not the one your flash drive uses.
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
