I have a question. For about 2 years I have been running a SOFTWARE MIRROR on a mitel 5 linux distro (based on red hat)
It lost some files. (contents from directories was not shown OVER NETWORK SMB)
After a file system check at boot it was marked READ ONLY. Therefore the distro could not boot. (a repair was run 10 x and result was FAILED)
I hooked it up to my FEDORA CORE 3 desktop, on the second IDE. (instead of cdrom drive)
It was detected by the BIOS and by WINDOWS XP. (i did not write anything to it with windows xp, also not with disk manager)
During boot FEDORA CORE 3 did the same thing as the mitel server, just stopping and complain about READ ONLY file system.
I do not understand why this happens, because the system is running perfectly without the extra disk from the file server and the FEDORA CORE 3 installation is running perfect.
It looks very frustrating that data can't be copied from another disk and that a distro on a perfect disk does not boot because some EXT3 disk with "damage" is hooked up to it.
By now I am coping all data from one of the disks using EXT2FS (read only driver) for WINDOWS to another disk. ALL DATA IS THERE!!! (using robocopy for windows because there are some file name probs)
I would like to know how to get FEDORA CORE 3 booting even if there is some new disk with READ ONLY MARK attached to the computer.
I know how to mount an extra disk and even managed in the past to format and edit fstab so I had new disk in linux.
Anybody an explanation for this behaviour? I am a little upset that I need to fall back to another OS just to copy data there is to find