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
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:
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 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)?
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.
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've had a look at some similar threads but as I'm very new to linux they're already a bit technical for me. Sorry, this calls for someone with patience. I gather from other threads that disconnecting an external drive without unmounting is a no-no, and this seems to be the likely cause. Now the disk is read only and I'm unable to change any settings through the usual control panel on ubuntu. I'm just not familiar with the terminal instructions. I tried to cut and past a few command lines from other threads but I got some warnings that proceding could damage data. Like this one: WARNING! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.
I added an ext4dev filesystem to my hard drive as /dev/sda3 and mounted at /share with the goal of putting all of my multimedia files on it and sharing it through NFS. I followed this guide: [url]
Of course, this was from lenny (hence the -dev). The partition was fine, and I mounted it numerous times. I also performed a dist-upgrade to squeeze. I shutdown that computer with the usual 'shutdown -h now' and disconnected the AC power cord from it, because I wasn't planning on using that machine for awhile. As far as I could determine, everything was fine before I unplugged it.
Every time that computer is powered off, the clock resets to 1999 because the battery is bad. So I am used to getting the "last mount time is in the future" error.
Three weeks after halting, I powered the computer back on. It was unplugged until this point. I got an error message when it attempted to mount /dev/sda3
I then removed its line from /etc/fstab, rebooted. and tried to check it, but I just keep getting the same error-- even with the '-b 8193' option.
The machine is still using the 2.6.26 kernel from lenny. I am building a new one right now (2.6.30), hoping that the problem is caused by the ext4dev/ext4 module. Otherwise I don't know what to do.
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.
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
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?
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?
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?
This is very bad even in 11.04! I have an usb disk 40 Gb. And I was loading it with data real fast (svn). At once I could no more write, Read-only file system was reported. I reckon that problem from years ago on redhat, so I try to fix it. But It became worse. It was severe damaged. I created a new filesystem while the disk was out the usb-box and directly connected to de IDE. Started all over, and the error also. Tried to repair with no luck. It looks like the journal get overrun but I'm not sure. However I do think its reproducible. I did it 3 times now and now I am very sick of it. This is happening on a updated 10:10 to 11:04 system, a few weeks ago.
I am installing Ubuntu 9.04 Desktop on my system. using entire disk. my disk is new one. first time i installed ubuntu on it successfully, used it and installed new kernel and some upgrades. all were successful.but on installing some drivers, its files system corrupted. so I had the need to re-install the OS again. NOW , when i am installing the OS, it gives error "(Errno 30] Read only filesystem" explaining that either CD/DVD is corrupt or HDD is corrupt. temperature of the environment may be high. I changed the system , ehanged the environment, moved to some cool place, changed CD drive and CD (after making new one from ISO), changed the HDD but all useless, error is there,
while installation is in progress my sda1 is mount on /target. when i see fstab, here in the line of /dev/sda1 ,error=remount-ro is observed. sometime installation gives error no 5 sometimes it gives error no 30 but both the errors convey almost same message explaining that either HDD is corrupt or CD. As i have explained that I changed every thing including HDD and CD but the error is same.
I want to install 11.04 next to my working 10.04 system. First I need to make room for the new system so I have booted from a live cd and started GParted. In GParted the partition with the 10.04 system on it, /dev/sda1, has a red circle with an exclamation mark in it and I cannot resize it. When I doubleclick on /dev/sda1 there is the following warning
Failed to change to directory '.'(Stale NFS file handle) Failed to change to directory '.'(Stale NFS file handle) Unable to read the contents of this file system! Because of this some operations may be unavailable.
The following list of software packages is required for ext4 file system support: e2fsprogs v1.41+.
The 10.04 system is working and has worked like a dream for a couple of years and the machine has never had any other system on it. Why would the live CD not be able to read ext4 fs?
openSuse v9.3 (Yes, it's old)linux 188.8.131.52-21.17-smp i686At some time after July 28 the entire filesystem has become read-only. It was functional on July 28, the last time I logged into the machine and edited a file. Even as the superuser when I attempt to change, say, the permissions of a file, I get:
Code: > # chmod 777 /opt chmod: changing permissions of `/opt': Read-only file system
I have 64bit install with CentOS release 5.3 (Final)It's been stable for about six months. What happened a while ago is really weird, I haven't messed with anything lately but the entire /home filesystem became read-only. Can't write, can't delete to anything on /home. The other filesystems are fine. I am root, and the permissions look normal. My directories and files are writable and readable.
root@atlanta [/home]# touch foo.txt touch: cannot touch `foo.txt': Read-only file system root@atlanta [/home]# ls -l
I accidentally changed etc., folder ownership, and now my computer doesn't even start up. I tried starting up in failsafe mode and changing the ownership from the root console, but somehow I wasn't allowed to do that. Then I loaded kubuntu from a live disk and I changed etc ownership to root. I thought that would clear up the mess, but apparently live disk's root is not equivalent to system's: when I try to start up the computer I get a message saying the filesystem is readonly. I'm not too concerned, because I have a complete backup, but I'd rather avoid the time of re-installing all my software again.
I'm attempting to build a load balancing cluster for shared web hosting clients and the only thing left is security. Given the track record with some of these sites, I don't trust them being centralized. We've had rootkits on some of the other servers that replaced system binaries, mostly ssh to capture passwords. I figured the only real way to lock it down tight enough to keep this from happening is to use a live cd for the filesystem or read-only toggle USB stick. But I also need to mount a rw drive to store the clients data and config files that are bound to change.
Is this really the way to go about this? If so do I simply make a live cd iso and edit the files within to handle mounting a rw hard drive and linking data and configuration files to that drive? I've considered just leaving all the data on the physical hard disk and mounting it as ro on boot for binaries and such but can't that just be changed with the right permissions?
Some moments ago, I plugged my drive into a computer with some strange data protection software. It turned my drive's filesystem into read only and now it can neither be formatted nor mounted with write option. I've tried
Code: $ sudo dd if=/dev/zero of=/dev/sdb but it doesn't work.
The problem is, the computer and the software that have caused this problem has lost forever.
Yesterday I post this note, because I've an urgent issue with the filesystem in opensuse 11.4, used like VMWare guest OS, over VMware Server 2 for w2k3 64bit like a host) opensuse 11.4 Filesystem goes read-only in VMware
But, Novell have a fix published for SLES 10, with the 184.108.40.206-0.12 kernel version .
I'm using a Opensuse 11.4 with the 220.127.116.11-0.5-desktop kernel version. May be related with the LSI virtual scsi hardware?
Because exists a fix for SLES 9, 10, RedHat EL 4,5 and Ubuntu 7.10, but doesn't work in opensuse 11.4
I have double boot (windows7 and Opensuse) on my laptop.
My problem is when try to login Opensuse says Read only file system.(While booting a lot of things FAILS(written red) because of Read only file system). So i can't login.
Cause of this problem is want to reach my Opensuse filesystem from windows7.I installed Ext2fsd software to windows7.After installed software can see my opensuse filesystem.But it looks empty from windows7.So uninstalled the software.
After that day try to login my Opensuse.While booting alot of thing fails to load it says "FAILED".and when entered my password after entering my username cant login it says ..... Read Only File System.
How can i make the filesystem Read/write permissions to my opensuse operating system.
I can't use any command beceause can't login. (I will try to boot with Opensuse Dvd)