|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] Does this sound like a lemon?
|
From what I am reading it seems that fdisk never removed the FAT
partitions. Thus if the FAT partition was never removed but only
renamed like /boot you never removed the Windows garbage.
I would do a clean install with removing all partitions with a Linux
fdisk or cfdisk. Have fdisk write the blank partition table and exit.
Reboot the system and see what happens.
If the system still has a FAT partition along with DOS/Windows then it
seems to me that your bios might be preventing you from removing the FAT
boot partition or from writing to the MBR. If this is the case you
might want to prob the bios aand see what is preventing you from setting
up your system.
As a final approach I would low level format the HD if it is not a
Seagate drive. If you lowlevel a Seagate drive you void the warranty on
the drive.
Here's where it gets weird... Also in that directory were command.com,
io.sys, a progra~1 directory, and a windows directory (along with a few
other non linux files). I tried to delete the windows stuff and it
said read only file system canot delete. Odd (keep in mind I fdisked
and did quick formats on all drives) Out of curiosity I booted to the
HD. Up came Windows ME...I decided to take another tack and booted up
a suse cd rescue disk and removed the /boot partition (/dev/hda1) wrote
the table, then added it back and re-wrote the table. I then booted up
with the floppy again. Lo and behold, no boot partition, but the
windows crap was now in root...
Grrrrr.... I then decided to get a windows floppy, did a win95 fdisk,
removed all the partitions, and booted the HD again. OK, no WinMe. I
reinstalled with the Slack boot and root floppies (still had the lilo
issue) and lilo still doesn't work. Further, the windows crap is back
in the boot directory. How could this happen? (The disks were made by
rawrite on an XP box, btw)
Further, I'm getting hostname kernel: hda: dma-intr status=0x51 {
DriveReady SeekCompleteError }
hostname kernel: hda: dma-intr status=0x84 { DriveStatusErrror
BadCRC}
in syslog unless I turn of DMA with hdparm. I googled and found this
could be due to cabling or a bad HD. I welcome any thoughts on those
errors (keeping in mind the above behavior)
Lastly, I'm getting FAT errors in dmesg
FAT Bogus LogicalSector size 0
FAT: Did not find valid FSINFO signature
Directory 1 bad FAT (Along with File system Panic)
So, did I get a lemon, or am I missing something obvious...
Thanks for any help.
Rob Carlson
_________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
--
Rev. LeRoy D. Cressy mailto:leroy@lrcressy.com /\_/\
http://lrcressy.com ( o.o )
Phone: 215-535-4037 > ^ <
Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me. (John 14:6)
_________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|