Very Computer

I don't know if anyone is working on being able to read a Disk Manage-d
drive..

Hope this helps,

Rich Kutter

http://www.mbvlab.wpafb.af.mil/~rkutter

Hi

I just bought a second IDE drive (Maxtor 1.2G).  Using MSdos and some Maxtor
fdisk program i partitioned the drive into 4 equal (300Meg) msdos partitions.
I was then able tomount each partition with MSdos.

I then booted up Linux and tried to mount one of the Maxtor MSdos partitions
(mount -t msdos /dev/hdb1 /mnt) , I received the following error:
" mount: /dev/hdb1 not a mount point "

I read the "Mini HowTo on Large IDE hard drives" and still could not solve the
problem. Could someone please help?

System Config

486dx2, 66Mhz, 16MegBytes
Kernel 1.1.67
Master IDE Conner Peripherals 420MB - CFS420A, 406MB w/64KB Cache, CHS=826/16/63 , MaxMult=64
Slave  IDE Maxtor 71260 AT, 1204MB w/256KB Cache, CHS=2448/16/63, MaxMult=16

My computer was purchased in March 1994, The BIOS does detect the
correct number of cylinders and heads. I do not have EIDE.

Below i have the following (information) output:
    - dmesg
    - fdisk -l
    - lilo.config

*************  My "dmesg"  *************

Console: colour EGA+ 80x25, 1 virtual console (max 63)
Serial driver version 4.00 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16450
tty01 at 0x02f8 (irq = 3) is a 16450
lp_init: lp1 exists, using polling driver
Floppy drive(s): fd0 is 1.44M
FDC 0 is a 8272A
Calibrating delay loop.. ok - 33.55 BogoMips
Memory: 15216k/16384k available (600k kernel code, 384k reserved, 184k data)
This processor honours the WP bit even when in supervisor mode. Good.
Swansea University Computer Society NET3.017
Swansea University Computer Society TCP/IP for NET3.017
IP Protocols: ICMP, UDP, TCP
SLIP: version 0.7.5-NET3.014-NEWTTY (4 channels)
CSLIP: code copyright 1989 Regents of the University of California
eth0: 3c509 at 0x210 tag 1, BNC port, address  00 20 af 4d 76 f1, IRQ 5.

Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction... Ok.

Partition check:
  hda: Conner Peripherals 420MB - CFS420A, 406MB w/64KB Cache, CHS=826/16/63, MaxMult=64
  hda: hda1 hda2 hda3
  hdb: Maxtor 71260 AT, 1204MB w/256KB Cache, CHS=2448/16/63, MaxMult=16
  hdb: hdb1
EXT2-fs warning: maximal mount count reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
[MS-DOS FS Rel. 12,FAT 16,check=n,conv=b,uid=0,gid=0,umask=022,bmap]
[me=0x7c,cs=0,#f=216,fs=0,fl=0,ds=0,de=49294,data=0,se=190,ts=1038615040,ls=1]
VFS: Can't find a valid MSDOS filesystem on dev 0x0341.

***********  output from " fdisk -l "  ******************

Disk /dev/hda: 16 heads, 63 sectors, 826 cylinders
Units = cylinders of 1008 * 512 bytes

   Device Boot  Begin   Start     End  Blocks   Id  System
/dev/hda1   *       1       1     447  225256+   6  DOS 16-bit >=32M
/dev/hda2         448     448     773  164304   83  Linux native
/dev/hda3         774     774     826   26712   83  Linux native

Disk /dev/hdb: 16 heads, 63 sectors, 2448 cylinders
Units = cylinders of 1008 * 512 bytes

   Device Boot  Begin   Start     End  Blocks   Id  System
/dev/hdb1   *       1       1    2447 1233287+  54  Unknown
Partition 1 has different physical/logical endings:
     phys=(398, 15, 63) logical=(2446, 15, 63)
Partition 1 does not start on cylinder boundary:
     phys=(0, 0, 2) should be (0, 1, 1)

********** my   lilo.conf   ******************

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/fd0
#compact        # faster, but won't work on all systems.
# delay = 5
vga = normal    # force sane state
ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /vmlinuz
  root = /dev/hda2
  label = Linux
# Linux bootable partition config ends

**********************************************

Hi

I just bought a second IDE drive (Maxtor 1.2G).  Using MSdos and some
Maxtor fdisk program i partitioned the drive into 4 equal (300Meg)
msdos partitions.I was then able to mount each partition with MSdos.

I then booted up Linux and tried to mount one of the Maxtor MSdos
partitions (mount -t msdos /dev/hdb1 /mnt) , I received the following error:
" mount: /dev/hdb1 not a mount point "

I read the "Mini HowTo on Large IDE hard drives" and still could not solve
the problem. Could someone please help?

It seems that linux's fdisk cannot read the partition table created by the
maxtor fdisk (diskMaganger).  Does anyone know of a diskManager (fdisk)
that will work with maxtor and will create a partition table that linux
can read ????

Someone suggested that i don't use maxtor (diskManager) , and use msdos
fdisk and only partition the first 540Meg as a msdos partition.  Thenuse
linux fdisk to partition the rest. (I hope this will work)Unfortunately i
was hoping to use 800Meg for dos and 400Meg for linux.

System Config

486dx2, 66Mhz, 16MegBytes
Kernel 1.1.67
Master IDE Conner Peripherals 420MB - CFS420A, 406MB w/64KB Cache, CHS=826/16/63 , MaxMult=64
Slave  IDE Maxtor 71260 AT, 1204MB w/256KB Cache, CHS=2448/16/63, MaxMult=16

My computer was purchased in March 1994, The BIOS does detect the correct
number of cylinders and heads. I do not have EIDE.

Below i have the following (information) output:
    - dmesg
    - fdisk -l
    - lilo.config

*************  My "dmesg"  *************

Console: colour EGA+ 80x25, 1 virtual console (max 63)
Serial driver version 4.00 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16450
tty01 at 0x02f8 (irq = 3) is a 16450
lp_init: lp1 exists, using polling driver
Floppy drive(s): fd0 is 1.44M
FDC 0 is a 8272A
Calibrating delay loop.. ok - 33.55 BogoMips
Memory: 15216k/16384k available (600k kernel code, 384k reserved, 184k data)
This processor honours the WP bit even when in supervisor mode. Good.
Swansea University Computer Society NET3.017
Swansea University Computer Society TCP/IP for NET3.017
IP Protocols: ICMP, UDP, TCP
SLIP: version 0.7.5-NET3.014-NEWTTY (4 channels)
CSLIP: code copyright 1989 Regents of the University of California
eth0: 3c509 at 0x210 tag 1, BNC port, address  00 20 af 4d 76 f1, IRQ 5.

Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction... Ok.

Partition check:
  hda: Conner Peripherals 420MB - CFS420A, 406MB w/64KB Cache, CHS=826/16/63, MaxMult=64
  hda: hda1 hda2 hda3
  hdb: Maxtor 71260 AT, 1204MB w/256KB Cache, CHS=2448/16/63, MaxMult=16
  hdb: hdb1
EXT2-fs warning: maximal mount count reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
[MS-DOS FS Rel. 12,FAT 16,check=n,conv=b,uid=0,gid=0,umask=022,bmap]
[me=0x7c,cs=0,#f=216,fs=0,fl=0,ds=0,de=49294,data=0,se=190,ts=1038615040,ls=1]
VFS: Can't find a valid MSDOS filesystem on dev 0x0341.

***********  output from " fdisk -l "  ******************

Disk /dev/hda: 16 heads, 63 sectors, 826 cylinders
Units = cylinders of 1008 * 512 bytes

   Device Boot  Begin   Start     End  Blocks   Id  System
/dev/hda1   *       1       1     447  225256+   6  DOS 16-bit >=32M
/dev/hda2         448     448     773  164304   83  Linux native
/dev/hda3         774     774     826   26712   83  Linux native

Disk /dev/hdb: 16 heads, 63 sectors, 2448 cylinders
Units = cylinders of 1008 * 512 bytes

   Device Boot  Begin   Start     End  Blocks   Id  System
/dev/hdb1   *       1       1    2447 1233287+  54  Unknown
Partition 1 has different physical/logical endings:
     phys=(398, 15, 63) logical=(2446, 15, 63)
Partition 1 does not start on cylinder boundary:
     phys=(0, 0, 2) should be (0, 1, 1)

********** my   lilo.conf   ******************

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/fd0
#compact        # faster, but won't work on all systems.
# delay = 5
vga = normal    # force sane state
ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /vmlinuz
  root = /dev/hda2
  label = Linux
# Linux bootable partition config ends

**********************************************

Any suggestions on how to go about changing the BIOS? Or a pointer to a
FAQ about BIOS upgrades?

--
Mike Makunas-----------------<http://www.tufts.edu/~mmakunas>----->

: I just bought a second IDE drive (Maxtor 1.2G).  Using MSdos and some Maxtor
: fdisk program i partitioned the drive into 4 equal (300Meg) msdos partitions.
: I was then able tomount each partition with MSdos.

: I then booted up Linux and tried to mount one of the Maxtor MSdos partitions
: (mount -t msdos /dev/hdb1 /mnt) , I received the following error:
: " mount: /dev/hdb1 not a mount point "

No doubt you are using the Slackware mount.
Throw it out and get mount from util-linux-2.4.
Then try again.

(When nothing is wrong, both versions will work.
But when you do something wrong, the Slackware version
will give silly error messages, and it can be difficult
to guess what is wrong.)

Quote:

>Maxtor 1.2G IDE, please help

>Hi

>I just bought a second IDE drive (Maxtor 1.2G).  Using MSdos and some
>Maxtor fdisk program i partitioned the drive into 4 equal (300Meg)
>msdos partitions.I was then able to mount each partition with MSdos.

>....

I could not get Disk Manager to work with Linux, so a booted Linux
from floppy and used Linux's fdisk to format the drive with partition 4
being over 520Meg.  Parition 3 was a 50 Meg Linux swap parition. I could
then install Dos is first partion, Linux in second.  Have not used      
fourth extended partition.

Disk Manager installs in the boot sector, I think, where LILO goes. Since
it support 16 paritions, its different from the regular fdisk partion
format.

: Hi

: I just bought a second IDE drive (Maxtor 1.2G).  Using MSdos and some
: Maxtor fdisk program i partitioned the drive into 4 equal (300Meg)
: msdos partitions.I was then able to mount each partition with MSdos.

I just got the very same drive, have the same problem.  What is happening is
the OnTrack software that is loaded from the boot sector really sucks!!
I'm going to get a EIDE controller hopefully in a few weeks, it will speed it
up to the 13.something transfer speed advertized on the back of the box, instead
of the 1.something it is now with a normal IDE controller :)  It will also get
rid of the necessity of OnTrack, so everybody will be happy!!

It's a great deal, 10x the speed, linux compatibility, and only for ~$35!!!

--
73, Joshua

      Northern Arizona University Amateur Radio Club (KC7KCO)

Quote:>Maxtor 1.2G IDE, please help

>Hi

>I just bought a second IDE drive (Maxtor 1.2G).  Using MSdos and some
>Maxtor fdisk program i partitioned the drive into 4 equal (300Meg)
>msdos partitions.I was then able to mount each partition with MSdos.

>I then booted up Linux and tried to mount one of the Maxtor MSdos
>partitions (mount -t msdos /dev/hdb1 /mnt) , I received the following error:
>" mount: /dev/hdb1 not a mount point "

>I read the "Mini HowTo on Large IDE hard drives" and still could not solve
>the problem. Could someone please help?

>It seems that linux's fdisk cannot read the partition table created by the
>maxtor fdisk (diskMaganger).  Does anyone know of a diskManager (fdisk)
>that will work with maxtor and will create a partition table that linux
>can read ????

Since help seem to know so much about Maxstor 1.2G drives I hope they can
solve my problem...

I have a number 832 EDIE controller (basically multi-IO plus one VLB and
one ISA IDE interface) with a 71260A* off the 2nd (ISA) interface.
DOS (including the supplied drivers) never see the 2nd drive and linux
does (but only if I add hdc=2448,16,63 which is the published CHS values
for the device). I only intend to use the device for Linux and not for
booting.

However the problem is the only thing the drive will do is say "drive
not ready" (status=0x80 { Busy } in the kernel messages) to the Kernel
(version 1.3.9 w. a modified kerneld patch applied). If I re-jumper
the drive and make it the secondary drive in the first chain (VLB---it
even works without disabling my old controller [which I have now done]
provided no drives where attached to it). When the drive is attached
to the primary interface (as slave with the jumpers set as per the
manual) the BIOS boot process fails with drive not ready).

It is a good thing I do not want it for DOS because Diskmanager 6.03
(as supplied with the drive) can not cope with the idea of more than
one IDE interface; instead it notices that neither of the drives attached
to the primary interface are Maxtor, says that it is only licenced
for Maxtor stuff and dies.

Any ideas, worarounds etc? Or is this just broken hardware that I should
get Maxtor to fix (difficult as I have no telephone number; little and
epsilon [>0 as usual] in the bank). I can not even think about running a
car or taking legal action that I might lose.

header---it is a MX record or similar redirects mail to that address
to this one).

--
Duncan (-:

"software industry, the: unique industry where the supply of substandard
 goods is legal and you can charge extra for fixing the problems"

My system is (for comparison):
Pentium 100
1.2 gig master hd
Sony CDU76E cd-rom (therein lies my problem) as the 1st slave
540 meg as 2nd master
nothing (yet) for 2nd slave
8 meg RAM
3.5 & 5.25 floppies
trackball
LJ4 printer (don't know about this yet)
hope some of this might help.

Quote:>I too am running a Maxtor 1.2 gig hd with a 540 hd secondary used only for Linux.
>I'll ask the obvious question, did you use the dos "fdisk" to find/format the
>disk?  Also, you need to tell bios in setup that you have the extra disk and what
>it's parameters are.  Oh yeah, get rid of the DiskManager.  As someone said, it can
>(and will) do things that even dos won't recognize.

Steve

I run two Maxtor drives a 1.2G and a 546M.  In the past I've notice that
a lot of people call their Maxtor 546 (model 7546A) drives a 540 meg hd,
I'd like to point out that their are, in fact two different Maxtor drives,
a 7540A and a 7546A.  Now, the interesting thing is that the 7546A will
*NOT* slave to anything, including other Maxtor drives (I have a 7345A and
a 71260A and neither work).  According to Maxtor tech support, there are
two versions of the 7546A and the one I have, while significantly faster,
doesn't like to slave.

If the symptoms you (whoever the original poster is) are experiencing
are that the system won't boot after you partition the drive, then
this may be your problem.  If you call Maxtor, and you speak to someone
who knows what they're talking about, they'll offer to swap your drive
for the slower one.  BTW, the firmware on my drive has the code
'EA7X 3636'.

Have a good one,
SBaker