Keep trying until you either run out of superblocks or it works. See if you get the same messabout about bad superblocks. Now try the command to validate the disk again. #Debian install dmg wrong fs type download#I've had to go the third or fourth one a couple of times. The Debian Live solution works like this: Download or build your own live image (the same kind of live image that can be used on a USB or CD). If not try the next superblock on the list. #Debian install dmg wrong fs type password#Your superblocks may be stored elsewhere. Code: sudo mount -t hfsplus Mac\ OS\ X\ Install\ DVD.dmg /mnt/usb/ sudo password for jason: 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 dmesg tail or so. You will also want to pick one from the list you get from your partition. Pick an alternate superblock - keep in mind that the first one is the default and its bad so let's not use that one. This will output the alternate superblocks stored on your partition. You don't want to do this if your superblock is OK. Get your error message which says the superblock is bad. Ignoring this step can cause you problems later if it's NOT an EXT4 file system. Your device and your file system (ZFS, UFS, XFS, etc.) may vary so know what you have first. sudo -sįigure out which device - assuming /dev/sdc1 for this example along with EXT4 as its the most common for this explanation. That concludes my warning on running your system as root. Like many other things, with great power comes great responsibility. If so directed, it will speedily delivery Mr. Just remember that when you are root, Linux assumes that you know what you're doing when you issue commands. You can sudo yourself silly or just become root for the process. data directory for a data base) so there are times when I don't want to use it or it doesn't work. FSCK can be a "lossy" process because FSCK may want to remove too much data or to remove data from a sensitive location (e.g. I have a different process for this that replaced the bad superblock with one of the alternatives. Sector size (logical/physical): 512 bytes / 4096 bytes I've already read this mount: wrong fs type, bad option, bad superblock on /dev/sdb on CentOS 6.0 to no avail.įdisk output regarding the drive Disk /dev/sdb: 1000 GiB, 1073741824000 bytes, 2097152000 sectors I've done this stuff many times before and have never ran into anything like this. I tried mount -t ext4 /dev/sdb1 /mnt/storage2 with identical outcome. In some cases useful info is found in syslog - try Missing codepage or helper program, or other error It resulted in mount: wrong fs type, bad option, bad superblock on /dev/sdb1, Then I tried to mount the drive mkdir /mnt/storage2 Mv /lib/modules/$(uname -r)/kernel/fs/udf/udf.ko /lib/modules/$(uname -r)/kernel/fs/udf/udf.ko.origĬopy new udf kernel module to modules directory and load itĬp fs/udf/udf.I added a new hard drive ( /dev/sdb) to Ubuntu Server 16, ran parted /dev/sdb mklabel gpt and sudo parted /dev/sdb mkpart primary ext4 0G 1074GB. #Debian install dmg wrong fs type Patch#configĭownload UDF PATCH (click here) Check here for Main PageĬp /tmp/UDF_2.50-linux-2.6.2īzcat UDF_2.50-linux-2.6.2 | patch -p1Ĭhange EXTRAVERSION to which-ever kernel you want.(BE SURE ABOUT THIS) This is really important for me, as I have lots of archived data on DVDs, which I currently can't access in CentOS.ĭownload the kernel source :kernel-2.6.25.Ĭd. I would appreciate any help or comments on the process before I take the plunge and do it. Current status I loaded up Debian 10.5 Live on a Ventoy USB and started following various steps towards recovering volume metadata. Running ls showed all drives but ls on the drives and gpts yielded unknown filesystem every time. Also I have kernel 2.6.18 installed, so i'm not sure it would work anyway. Code: error: unknown filesystem Entering rescue mode. I have never done this before, and am somewhat nervous as a result. helper program) In some cases useful info is found in syslog try. I have however found a patch for kernel 2.6.25, and instructions on using it, but this involves recompiling the kernel. Error: mount: wrong fs type, bad option, bad superblock on xx.xx.x.x:/mount/point, missing codepage or helper program, or other error. It seems that this is an old and well known bug, experienced in loads of different distros and fixed in those using newer kernels.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |