After Ghost 4 Linux Root Filesystem mounts readonly
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After Ghost 4 Linux Root Filesystem mounts readonly
I have Ghoted a production Fedora Core 4 box for the purpose of virtualizing it. I simply ghosted my hda3 partition (root partition). On the Virtual Server I created a new virtual machine and installed a base Fedora Core 4 on it. I did this to retain a new /boot and swap partitions. I then restored (via Ghost 4 Linux) the hda3 partition. The system boots, but produces all kinds of errors as it reports that it cannot touch the log files as the filesystem is mounted Read-only.
I have run mount and the filesystem says that it is rw.
If I boot from the Fedora Rescue Cd I am able to touch a test file no problem.
Any ideas. I think the procedure I have performed is flawless, if only I can get this last step to work.
I have umounted /dev/hda3 and run fsck on it. It reports /: clean, 73566/9222528 files, 702234/9215285 blocks.
I then try to remount the device: munt -o remount,rw /dev/hda3
I am given the following message:
ext3_abort called.
EXT3-fs error (device hda3): ext3_remount: Abort forced by user
mount: block device /dev/hda3 is write-protected, mounting read-only
ext3_abort called.
EXT3-fs error (device hda3): ext3_remount: forced by user
Remounting suggests you did this from within the running O.S. I don't know if Linux likes that for root partitions...
Can you mount it as ext2 (even ro?). Does this thread have clues for what to check?: http://www.linuxquestions.org/questi...d.php?t=429986
No this thread does not really pertain to me as I hace SELinux disabled.
OK. Good to know.
Pardon my ignorance, but you want me to mount a EXT3 partiton as a EXT2 partition? How?
-t ext2. Ext3fs is "just" ext2fs with a journal (OK, and some more).
Should I try it from a boot (rescue cd)? Funny thing is if I use the Fedora Rescue Cd and manually mount this root partition, I have full read-write permissions.
Weird. If fsck returns w/o probs and if you can access it w/o probs from a Live/rescue CD then it must be something in the O.S. What's the fstab line? The system boots, but produces all kinds of errors Maybe post those in full?
The errors all pertian to not being able to start xyz service because it could not open the associated log file as it is read-only. If I do a ls -l on the log dir all of the files are rw for root:root.
I am wondering if somehow with the restoring of another hda3 partition to this system if their could be 2 root users? I mean in the windows world it might be possible (not plausible) for two unique users of the same name with a different guid. Could this be happening? I am not familiar enough with linux to determine this. Any help would be greatly appreciated.
I just seems to me that there is some kind of permissions issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.