On Thu, 30 Dec 2004 21:20:42 -0700, Richard Mixon (qwest)
Would appreciate any ideas before I bite the bullet and have to reinstall.
I have a box I was using to setup mythtv using SuSE Pro 9.2. Its an Athlon XP 1500 with a WD 200GB drive, 512MB RAM.
I had partitioned it with a 100mb "/boot", 512MB swap and the rest as an LVM storage group, which I then divided up into "/", "/var", "/cache" and "/mythtv".
The only unorthodox thing I did (and I say that only in hindsight) was use the partition editor to change my "/mythtv" partition from Reiser to XFS while the partition was mounted. I had read that was much larger for large file. When I rebooted no I got a screen fully of numbers (TTY1, TTY2, ....) and no root partition found.
I used CD #1 and asked it to automatically repair the system. It says it cannot find any partitions with Linux installed - of course I've had it rescan multiple times. The partition editor still shows all partitions as they should be.
What should I do next?
Thanks in advance - Richard
Richard, I don't have any answers for you, but are you sure your IDE controller is compatible with a 200 GB drive? Anytime I see one bigger than 137GB I get nervous. Just a few days ago a co-worker of mine put a 250GB drive full of valid data on 2-yr old Intel Motherboard. (He was running Win2K) The drive seemed to work and he could see the directory structure etc., but he was having file corruption issues. We tracked his problem down to non-compatible IDE controller on the motherboard. Unfortunately some of the data was corrupt by that point. (Yes, we had it on tape, but that delayed us a day to restore such a big drive.) As I understand it, all ATA/133 controllers support large disk drives, and apparently some ATA/100 controllers do as well. Unfortunately, the only way I know to really verify a controller is large drive capable is to write out over 137 GB of data with known md5 checksums, then verify the checksums. If someone knows an easier way, I would like to hear it. Or if Linux is better than Win2K about simply not attempting to access parts of the disk drive beyond the capability of the controller, I would like to know that as well. Greg -- Greg Freemyer