what 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
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 RelatedI'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]....
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 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?
Just moved to Ubuntu from XP. Whole process has gone very smoothly, but left with a small problem (i.e. it isn't actually affecting usability) that I don't seem to be able to fix and can't find on forums/internet. I also have a problem with the Floppy drive, but I've seen that problem elsewhere in the forums.
It's a dual boot system with both NTFS and Ext4 drives. All are visible and fully accessible. I decided to convert one of the NTFS drive to Ext4. That appeared to be successful and was successfully remounted as an Ext4 drive. The drive label is "Data". I did have a bit of a problem getting it remounted so that I could see/use it under my log-in as opposed to just under root. It's at this point I think that I did something to create the problem.
I now have two entries for "Data" in drop down menu for Places. The true one is shown as a standard hard drive icon, but the false one is shown as a different icon - possibly an external drive icon (note that the floppy drive is also showing as the same icon and I can't access that, but I've seen that's a problem elsewhere in the forums).
I can write and read to the true "Data" hard drive. If I click on the other false "Data" icon, I get the message "mount: /dev/sdd1 already mounted or /media/Data busy mount: according to mtab, /dev/sdd1 is already mounted on /media/Data". If unmount the true drive and try to mount the false drive, the system mounts the true drive instead. If I log into nautilus as root, neither the false data drive or the floppy appear in the left hand panel.
I 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:
[code]...
how I can repair the drive and retrive data?
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....
After 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 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
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]....
How can i read out the superblock of a filesystem?
View 5 Replies View RelatedI 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.
Trying to mount my USB stick and getting a superblock error.. Tried a command in the terminal but it said only "ROOT" can access command...How do I get to "ROOT"...??? See attachment.
View 9 Replies View RelatedI'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.
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 RelatedI'm trying to mount my new Western Digital Elements 2tb hard drive, but every time I try to plug it into the computer I get this error message:
Quote:
Error mounting: mount exited with exit code 12: Failed to read last sector (3907027119): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS),
[code].....
But when I tried opening the hard drive from nautilus I still got the same error message as above (no other volumes was connected at the time). I've also tried opening and watching it in GParted, and I can see it there as a volume that's not allocated. When I tried to allocate the hard it I got the message that it had no partition table. And that I cold make one. I tried and Ubuntu suggested to make a MS-DOS partition table for it. But there I got a little scared as I've not done this before. The external hard drive is brand new and was brought today. And I don't have the possibility to test it with Windows or Mac as I'm using Linux only on my machines.
[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 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 have been running a live version on a 8 gig stick. Played nice for a couple of months but now when I try to access the native ntfs file system, I get the following error message.... Error mounting: mount exited with exit code 21: mount: according to mtab, /dev/sda6 is already mounted on /media/c
View 1 Replies View RelatedMy computer has been acting quite strange lately. It's been taking longer to boot, and my sound doesn't play anymore (Only a high pitched sound is heard, and no hardware for sound is detected). Just recently, my Windows 7 Partition returned the error of Disk Error Occured. Press CTRL+ALT+DEL to restart.
Any way I can fix my whole issue, I think my desktop is starting to die on me :O (And its only about 7 months old T_T)
my windows xp system has recently been messed up, everytime i boot, i see the windows logo and then it reboots so i decided to liveboot ubuntu in order to recover the important files on my hard drive and then reboot. Problem is when i try to click on my "500GB Filesystem" I get this message.Unable to mount 500GB FilesystemError mounting: mount exited with code 13:ntfs_attr_pread_i:ntfs_pread failed:/input/output error Failed to read NTFS $Bitmap:Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk/f on Windows then reboot into Windows twice.The usage of the /f parameter is very important! If the device is SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/directory(e.g./dev/mapper/nividia_eahaabcc1). Please see the 'dmraid' documentationfor more details
View 1 Replies View RelatedI 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 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 just built an AMD Phenom II Six Core with 4 Gigs Ram a 160Gib / and swap, and (2) Two Tb mirror for Raid (data storage) I had been using DMRAID in the deprecated box but this box has MDADM v3.1.4 - 31st August 2010 from source (on MDADM wikipedia).
I have no permission problems with using the raid and dmraid is un-installed. The raid is working perfectly and is mounted in my fstab with ext4 defaults 0 2 as my options.
I have two exports
/media/raid/Test
/test
Both show IP and subnet on the showmount -e for the server. I can mount the test just fine on the server. I cannot, however, mount the /media/raid/Test error: mount.nfs: access denied by server while mounting hostname:/media/raid/Test Using dmraid I am able to have the deprecated box export and mount nfs shares from the raid but using MDADM on the new computer, I cannot. I get similar results with pointing MYSQL's data folder to a location on the "/media/raid/Database" (even with apparmor entries).
We recently moved to a new home and I am trying to get my home file/print server set up again. Thanks to swerdna's excellent website, I got my server box (just upgraded from 11.0 to 11.2) running Samba and serving my shares over the network, and my "client" machines can access them without a problem.However, I'm not having much luck setting up CIFS mounts on my Linux desktop. I have my all-purpose user added to the Samba auth list (via smbpasswd), and configured my client as swerdna's howto's specify, and I can access the files just find. However, when I try to mount the shares with this command:
Code:
mount -t cifs -o username=klein,password=klein //192.168.1.70/sharedmedia /home/zak/SharedMedia/
I get the following error:
[code].....
mount: error 6 mounting ext3pivotroot: pivot_root (/sysroot, /sysroot/initrd) failed:2Remounting defs at correct place if necessaryMounted defs on /devFreeing unused kerbel memory: 272k freedKernel panic: No init found. Try passing init=option to kernel
View 1 Replies View RelatedThe 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 RelatedAccidentally the usb plug on my WD "My Book" got halfway unplugged and I didn't notice it. when I rebooted it, it wouldn't read the drive. I tried using G Parted to repair it but no success, it just runs forever accessing the drive and never finishes. (I left it running an entire weekend and it didn't finish) the drive is formated ext3.
When I try to mount the drive in Ubuntu 9.10 it gives this error message:
Strangely if I boot into Windows and use the ext driver I can access the drive just fine. is this something I can fix? if needed I can use Windows to do any repairs.
