Hi Admins,
The short version:
My new hd seems to give linux fits. Maxtor DiamondMAX 10g CHS=1401/255/63
on a FIC VA503+ motherboard. Any ideas?
The long version:
I'm having some trouble with my linux box, and I'm pretty sure I know what
going on, but I'm hoping you can help me find a workaround. I use my box
mainly as a fileserver for my home network, and to increase storage space I
installed a 10g drive. On the outside of the packaging the hd came it, it
stated clearly "requires Windows95 or better". I figured this was to
utilize fat32, and I was going to be using ext2 anyway, so I put it into
the machine and created some partitions. Right now there are three
partitions on it, two with 2g each (/vol1 & /vol2, /dev/hdb1 & /dev/hdb3
respectively) and one of 500m (/home, /dev/hdb2).
Everything worked perfectly for a month or two until /vol1 (/dev/hdb1)
started filling up. After that, I began coming home to find my system
locked up with messages about inode trouble with /dev/hdb on my syslog
screen. Rebooting would tell me to run fsck manually, which I did and it
would fix the problem and boot normally. This has been going on for about
a month and and half - annoying, but a situation I could live with.
Now, twice last week, I've come home to hex dumps all over my screen. Keep
in mind, I've seen a total of three hex dumps in the entire life of this
box, including the two last week - so this is normally a very stable system
which I have set up as a samba server. Does anyone know of any BIOS tweeks
or settings inside linux that would help alleviate this situation?
Hardware-wise, the machine is an AMD k6ii-450 running on a FIC VA503+
motherboard. The hard drive in question is a Maxtor DiamondMAX 10g drive.
Any help would be greatly appreciated.
[root@crab /root]# cat /var/log/dmesg | grep hdb
ide0: BM-DMA at 0x6000-0x6007, BIOS settings: hda:pio, hdb:pio
hdb: Maxtor 91152D8, ATA DISK drive
hdb: Maxtor 91152D8, 10991MB w/256kB Cache, CHS=1401/255/63
hdb: hdb1 hdb2 hdb3
[root@crab /root]# fdisk /dev/hdb
The number of cylinders for this disk is set to 1401.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/hdb: 255 heads, 63 sectors, 1401 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 262 2104483+ 83 Linux
/dev/hdb2 263 326 514080 83 Linux
/dev/hdb3 327 588 2104515 83 Linux
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
