I'm trying to get some data off of an external harddrive. I get a few errors:Unable to mountError mounting: mount: /dev/sdb1: can't read superblock.I then tried to run a read disk benchmark on disk utility and that seemed okay.I then tried
Code:
ubuntu@ubuntu:~$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 320.1 GB, 320072933376 bytes
[code]....
I have a problem in my ubuntu 10.01 that it can't load a drive/volume in ubuntu. When I tried, it said: "Unable to mount location Error mounting: mount: /dev/sda1: can't read superblock". And when I boot my pc with 'Windows', it said : "UNMOUNTABLE_BOOT_VOLUME" under a blue screen. What can I do to solve this problem?
View 9 Replies View Relatedwhat does this error message mean? im trying to mount an ipod in disc mode. let me know if there is a way to manually mount it to get around this. but not too technical, the simpler the language, the easier i will understand it.
View 9 Replies View RelatedI am newer to Slackware but not to Linux. I am having the hardest time trying to get my CDROM to mount for me so that I can play audio cd;s and the like. I can see that the system knows that my CDROM drive is there and that it works because I installed Slackware 13 from my CDROM drive as /dev/hdc. Now when I put in a cd nothing happens? I have googled away and searched this forum quite a bit before posting this but I have tried almost everything I can think of and what others have mentioned. I have screenshots to show you what I mean. When I try to run the command:
mount /dev/cdrom /mnt/cdrom
I get it as mounting as read only and it says can't read superblock? Now that is fro my slave IDE CDROM on top as hdd. I have tried before to mount it as /dev/hdc but to no avail. I know both CD drives work just fine because I used them to install the system. I am going to put the screenshots below so maybe someone can help me! Also I can eject the top CD drive with the command 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?
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 am unable to boot my server and it is erroring with the message "Kernel panic - not syncing: Attempted to kill init!". Here are the details:
I have a brand new Dell PowerEdge T110 server with Quad-Core Xeon CPU and 2GB 1333MHz RAM. I have installed a hard disk (SATA, 7.2rpm) on this machine that I removed from another Dell PowerEdge T100 server with Dual-Core Xeon CPU that was running software RAID 1.
Now when I boot the new T110 server, it displays the following error messages code...
I am running CentOs v5.5 x86-64. If I put the hard disk back into T100, it boots fine. I do not know why it is not working with T110 server.
I got a CentOS server + KDE from a server (which I had no contact until now), he had 2 HD's one for the system and another for files.
I brought the HD system home to try to make it run on a virual machine (VMware) so I can do some testing before you put in practice.
But already converted the VMware HD to the system, it tries to start but it shows some errors and in a message "kernel panic - not syncing: attemped to kill init"
I think the drivers are correct, has edited the file "/ etc / modprobe.conf" edited these entries equal to another I installed CentOS on VMware.
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptspi
ata_piix alias scsi_hostadapter2
Look at the picture attached the full error.
Link to large image
Link to large image
I have a server that has a Fibre Channel mount that is having issues. When I can in this morning I found that it had switched to read only. Now looking through /var/log/messages I see that there are errors reported on the disk. I know that i will need to run fsck on it, but I do see lines about the device mapper failing for mpath0 first, which is the device which is mounted. I am wondering if someone can take a look and see if this is just a drive issue, or an issue with the fibre channel connection.
uname -a
Linux server 2.6.27.25-78.2.56.fc9.x86_64 #1 SMP Thu Jun 18 12:24:37 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
Mar 28 00:12:36 server kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
Mar 28 00:12:36 server kernel: end_request: I/O error, dev sdb, sector 314570452
Mar 28 00:12:36 server kernel: device-mapper: multipath: Failing path 8:16.
Mar 28 00:12:36 server multipathd: 8:16: mark as failed
[Code].....
I used the ntfs-config utility to mount my windows drives automatically at startup. While doing so, I had my USB-HDD still attached, and after making changes and rebooting, it did something unknown I didn't expect and I cannot mount my USB-HDD again, and it gives me the following error message:
Error mounting: mount exited with exit code 1: helper failed with:
mount: only root can mount /dev/sdb1 on /media/MyUSBDrive
I did manage to open it somehow, but then all the data was erased apart from ~3 GiB [edit: it's got some kind of extra drive built-in which is mounted as a CD-ROM drive, and when I open that one first all the files are missing in the actual drive, otherwise I get the message above]. I don't know what information I should include here, but my fstab looks like this:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
[code]....
This line in terminal:
sudo mount -t ntfs-3g /dev/sdb1 /media/sdb1
Gives:
fuse: failed to access mountpoint /media/sdb1: No such file or directory
What should I do to recover my files and fix the mount error? [edit: at the very least, how do I backup my files onto my internal HDD so I can format it and recover it in this manner]
How can i read out the superblock of a filesystem?
View 5 Replies View RelatedI 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:
[code]...
how I can repair the drive and retrive data?
I removed a hard drive from a failed Buffalo LinkStation NAS. The drive was 1TB and formatted in XFS. I installed Debian Linux on my Mac using Virtual Box just so I could get to the files.
When plugin the drive (via USB) two volumes show up, but there's another that I can't seem to open (and may have all of the shared files I need). It's the largest volume (over 900 MB).
I keep reading to run xfs_repair, but when I type that in the terminal, I am given "command not found". I am not sure how to use it.
Also when I try to open the volume I am given "can't open superblock" error.
I am not too familiar with using Linux and ma just trying to get to my files.
I just installed pysdm so I could configure what drives mount on boot, and now when I go to access my external harddrive, this is what I get:
Unable to mount Hard Drive
Error mounting: mount exited with exit code 1: helper failed with:
[mntent]: line 11 in /etc/fstab is bad
[mntent]: line 12 in /etc/fstab is bad
[mntent]: line 13 in /etc/fstab is bad
[mntent]: line 14 in /etc/fstab is bad
mount: can't find /dev/sdb1 in /etc/fstab or /etc/mtab
I am having problems with an old laptop I have. It had windows xp on it, and after loaning it to a friend it wouldn't boot up. I decided to try linux, but I'm having problems loading it. If I try to run the liveCD it halts because its unable to mount root. If I try to install it just doesnt work well (will stop at different points).
So I figured a mem test would help. I am running the test, currently its on test #6, but it is coming up with a ton of errors. Does this mean I need to replace the RAM?
If so, this is the computer I have. Will this RAM work? I've been out of the tech game for awhile so not really following hardware anymore, and just want to double check.
I have a removable USB pen drive, that all of a sudden, when it got 99% used, stopped working. When I try to mount it (manually) I get "can't read superblock". I know there is a ton about this on Google and I've read a lot of them, but most seem to be about formatting a drive, or fiddling in fstab. I'm trying to run fsck on it, and it finds errors, (among them: two FAT-tables?) but then it just freezes, and CPU goes to 100 % and I let it be like that for 4 minutes, before aborting. Scandisk in windows is rubbish (fails to start), and running "chkdsk /f F:", in windows, results in nothing, the shell crashes immediately. Is it normal for fsck to get stuck and just chew up CPU? It does not seem to be reading from the drive, according to conky. Also, is it possible to run fsck as normal user, (at my work)?
View 2 Replies View Related[URL]
This problem has arrived again.......I tried the same solution but didn't work out...the problem is described below.
I use Ubuntu 9.10 .
I did this in Ubuntu 9.10 live CD.
quote from terminal :-
ubuntu@ubuntu:~$ sudo mkdir /win
ubuntu@ubuntu:~$ sudo mount /dev/sda5 /win
ubuntu@ubuntu:~$ sudo mkdir /vdisk
ubuntu@ubuntu:~$ sudo mount -o loop /win/ubuntu/disks/root.disk /vdisk
[Code]....
The superblock could not be read or does not describe a correct ext2 filesystem. 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>
ubuntu@ubuntu:~$ "
> ^C
ubuntu@ubuntu:~$
^^ quote ends.
I used dual booting with Windows Xp and Ubuntu 10.04. Because errors, I reinstall Windows and then I could not enter GRUB, and Ubuntu partition disappear. I tried to reinstall ubuntu using live CD but I could not detect last ubuntu partitions. After I installed fresh Ubuntu on new partition, I got error message like this:
Unable to mount floppy0 Mount: block device /dev/fd0 is write protected, mounting read-only Mount: could not determine the file system type, and none was specified
I want to populate an array of string by files exists in directory on mounting of file system. I got an entry point for file system mount. I can use either do_mount function or fill_superblock function. But I am not clear about how to call readdir from there itself. I need inputs for calling readdir from fill_superblock function.
View 2 Replies View Relatedi 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....
The HDD is a 500GB internal SATA, The smart claims that the "file system is not clean" but is still green.FSCK ran a few errors and using fsck i copied a new superblock from a backup location, It still won't let me mount and FSCK is still trying to fix a TON of errors. I'm sorry I don't know any of this yet, but I'm concerned that FSCK could be destroying the data on the drive, for example photos and other important things. FSCK is coming with a lot of things to fix, It's gone from trying to fix errors in free blocks of group #1 to over #3000.. Is this safe? Will this work? Can I get rid of whatever caused this problem in the first place?
View 1 Replies View RelatedI recently got a computer donated to me for free from my Computer Science class, as the teacher couldn't figure out what the problem was that was preventing him from booting to the startup screen (all I could figure out was that the slot the memory card was in was bad, so I switched slots and got it working). The hard drive on the computer was wiped with a disk nuker called DBAN. Now I would like to install a Linux OS on the computer, but whatever disc or distro I try gives me similar "unable to read" errors. I would like to know if there's anything software-wise I need to do before attempting to replace any hardware. An example of the error I'm getting is as follows (using a mandriva livecd):
/etc/rc.d/rc.sysinit: line 1281: /var/log/dmesy: Read-only file system
SQUASHFS error: sb_bread failed reading block 0xa6e58
SQUASHFS error: unable to read cache block [29b963ea:782]
SQUASHFS error: unable to read directory block [29b963ea:782]
Anyone know what I need to do to get this fixed so that I can install a Linux distro?
Also I have all files it asks for installed including dostools..Btw I used usb creator, then went to gparted and did something. The system is fat 32 now but with same message, not including ext4 part. Just the mount point message, and something about dosftools and mtools, wihich also are installed.
View 4 Replies View RelatedI 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
View 8 Replies View RelatedAfter several crashes during videos it seemed like a good idea to fsck root. Downloaded the latest systemrescuecd and ran it at boot. The error message was 'bad magic number, corrupt superblock' with a suggested command to try another superblock. That failed with the same message. Tried tune2fs to force fsck at boot and got the same message. The drive is less than 6 months old and the installed system is working more or less ok. The command I used was 'fsck.ext4 /dev/sdc2'. What am I doing wrong?
View 9 Replies View RelatedI 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 have 10.10 installed and working OK. The Home directory is located on a second 1TB disk (sdb1). Recently, I've started to experience random boot failures where the start-up routine gets as far as showing the '10.10' logo with the progress dots underneath, but then throws up an error message saying that it cannot mount sdb1. I then have an option to Quit or drop into the shell to do a manual restart.
If I then do a Ctrl/Alt/Del, the system reboots, but usually fails again. Powering off and on, sometimes more than once, is the only way to eventually get a clean boot. The drive causing the problem is fairly new and all the diagnostic checks seem to indicate that it's healthy, so I'm not sure what causes the problem.
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
ata2.00: status: { DRDY ERR }
ata2.00: error: { UNC }
ata2.00: configured for UDMA/133
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: BMDMA stat 0x4
[Code]....
I have an mdadm linear array of 4 500GB drives. One of them had a few bad sectors, so I've dd'ed it to a new one (conv=noerror), and tried to start my array. Mdadm refuses, saying, "mdadm: /dev/md4 assembled from 3 drives - not enough to start the array."I had diffed different samples from different positions on the source and the mirror drive and confirmed they were identical. Checking the superblocks confirms three old drives still having their superblocks as expected, while the newly mirrored one has,
daniel@lnxsrv:~$ sudo mdadm --misc --examine /dev/sdf1
mdadm: No md superblock detected on /dev/sdf1.
- and,
daniel@lnxsrv:~$ sudo blkid /dev/sdf1
[code]....
As before. The mirror apparently has no uuid, but the original does. To confirm my sanity, I did,
daniel@lnxsrv:~$ sudo dd bs=1M count=50 if=/dev/sdc of=./sdc && sudo dd bs=1M count=50 if=/dev/sdd of=./sdd && sudo diff -s sdc sdd
50+0 records in
[code]...
How can the uuid not be the same when bit-for-bit from the very first byte of the drive, covering MFT etc., these two drives are identical according to diff?
First of all: it's been more than 12 years ago since I worked with Linux, and a lot has changed in the meantime. But I considered it a challenge to install Ubuntu 9.10 and lateron upgraded to 10.04 LTS without any troubles, until now:
Except my main partition ("/") all other partitions fail to mount. All NTFS partitions from my other OS and also 2 other linux ext4 partitions I've made are not accessible anymore. and, what bothers me the most: I deleted those 2 new linux partitions in the meantime because I couldn't access them initially because Root was the owner (Duh! root is standard disabled in Ubuntu, right?). After an attempt to try to automount all partitions following the help guides I got now big grey errors on my splashscreen while booting, telling that an error occured with e.g. /media/Backup because it is missing or it cannot be mounted, with 3 options below: waiting, skipping or using a command prompt to solve this. I always choose Skip for safety.
Now if I want to see the content of all my other partitions I got a popup telling me unable to mount e.g. /media/Downloads and the message included:
[Code]....