Re: Problems with drive usage (Debian 1.3.1)
On Sun, Jan 03, 1999 at 11:26:42PM +1300, Carey Evans wrote: > > This might indicate a problem with kernel 2.0.29 - I am not sure if it can > > address more than 16 partitions per disk. > > I don't have any SCSI disks, but it looks like that restriction still > exists in 2.1.130. In fact, you're limited to 14 because /dev/sda is > the entire disk and the extended partition (usually /dev/sda4) doesn't > store anything itself. Oh no - I just saw it. Linux limits the number of partition per scsi drive to 14. That's not good! > > This is easy. mke2fs is right - there is probably no /dev/sda18. Just create > > it yourself: > > > > mknod /dev/sda16 b 8 16 > > mknod /dev/sda17 b 8 17 > > mknod /dev/sda18 b 8 18 > > I don't think so. 8,16 is /dev/sdb, 8,17 is /dev/sdb1, etc. You are right, sorry. I think we should remove that limit to 16 partitions. That's stupid - 62 partition per ide drive and 14 per scsi drive... cu Torsten pgpk4ynVzYNfe.pgp Description: PGP signature
Re: Problems with drive usage (Debian 1.3.1)
Torsten Landschoff <[EMAIL PROTECTED]> writes:
> > - Warning: Unknown PCI device (104c:3d07).
>
> This is probably no problem - you just have a pci device which is not known to
> your ancient kernel. No problem.
It's actually a "Texas Instruments TVP4020 [Permedia 2]", not that I
actually know what *that* is.
[snip]
> > When I try to add the new partitions to the end of the unused space, or all
> > of
> > them as logical partitions, cfdisk installs all of them. But as soon as I
> > try
> > to initialize the new partitions, the system fails to work properly when I
> > arrive at /dev/sda16 ("is the entire device, not just one partition").
>
> This might indicate a problem with kernel 2.0.29 - I am not sure if it can
> address more than 16 partitions per disk.
I don't have any SCSI disks, but it looks like that restriction still
exists in 2.1.130. In fact, you're limited to 14 because /dev/sda is
the entire disk and the extended partition (usually /dev/sda4) doesn't
store anything itself.
> > Initializing the partitions in the reversed order yields: "Could not stat
> > /dev/sda18 - no such file or directory" although cfdisk shows the correct
> > entry in the partition table.
>
> This is easy. mke2fs is right - there is probably no /dev/sda18. Just create
> it yourself:
>
> mknod /dev/sda16 b 8 16
> mknod /dev/sda17 b 8 17
> mknod /dev/sda18 b 8 18
I don't think so. 8,16 is /dev/sdb, 8,17 is /dev/sdb1, etc.
Can you please post what your current disk looks like? For 5 DOS and
4 HPFS partitions you only have five partitions left for Linux, or
four if you're using Boot Manager.
You can probably get by with fewer partitions until you decide you
don't need DOS, though, especially if you can use Dosemu and Wine to
do everything DOS and Win3.1 do. I also think OS/2 would be able to
cope with just one HPFS partition. You can use LOADLIN from DOS if
LILO can't boot off an extended partition.
So, I would get rid of /httpd and /adabas and put them under /usr,
/usr/local, /var and/or /home. I would suggest swap, /, /var, /usr
and /home, and at a pinch you could put /usr on the same partiton as
/. Plan to back it up and reinstall later when you have a better idea
of what size they should be.
It might be possible to put the OS/2 and/or DOS partitions on
/dev/sda16 etc., if they can cope. I'd back up everything, use OS/2
FDISK to create all the partitions, with the Linux ones as DOS
instead, then restore OS/2. Then install Linux and change the DOS
partitions to Linux. This is a lot of trouble, especially if it
doesn't work.
--
Carey Evans http://home.clear.net.nz/pages/c.evans/
Larry froze. Was the bag a trap?
He could see the way in, but the other end appeared to be sealed.
Re: Problems with drive usage (Debian 1.3.1)
On Fri, Jan 01, 1999 at 04:11:04PM +, Alexander Koch wrote:
> - Warning: Unknown PCI device (104c:3d07).
This is probably no problem - you just have a pci device which is not known to
your ancient kernel. No problem.
> - Failed initialization of WD-7000 SCSI card.
This is no problem either as long as you do not own such a scsi controller.
> - PPA: unable to initialize controller at 0x378, eror 2.
Hopefully you not not own such a crap too - the ppa driver is for a parallel
zip drive.
> The error messages upon partitioning/initialization:
> When I try to add the new partitions to the begin of the empty space, cfdisk
> 0.8i labels the remainder "unusable", after I add the two primary partitions
> (/ and swap).
This does not surprise me but you left out your layout on the disk. I guess
you have a primary partition at the start of the disk and a an extended
partition behind with all logical partitions?
This way you used 2 partition slots in the master boot record of the disk. If
you add 2 primary partitions you need 2 other slots and another one for the
logical partitions.
Resolution:
The swap partition does not need to be a primary one. Just use a logical
partition for it.
> When I try to add the new partitions to the end of the unused space, or all of
> them as logical partitions, cfdisk installs all of them. But as soon as I try
> to initialize the new partitions, the system fails to work properly when I
> arrive at /dev/sda16 ("is the entire device, not just one partition").
This might indicate a problem with kernel 2.0.29 - I am not sure if it can
address more than 16 partitions per disk.
> Initializing the partitions in the reversed order yields: "Could not stat
> /dev/sda18 - no such file or directory" although cfdisk shows the correct
> entry in the partition table.
This is easy. mke2fs is right - there is probably no /dev/sda18. Just create
it yourself:
mknod /dev/sda16 b 8 16
mknod /dev/sda17 b 8 17
mknod /dev/sda18 b 8 18
And to get the permissions right:
chown root.disk /dev/sda*
chmod 660 /dev/sda*
> What can I do to work around that problem?
Try the commands I typed above. You can get a shell (command prompt) with
Alt-F2 (Alt-F3?) during the installation. If mknod is not found (or
chown/chmod) do the following:
- format the partitions as far as it works
- install the base system
- use the shell to issue the commands above. You might need to prepend the
path of the installed files of the base system, e.g.
/mnt/bin/mknod, /mnt/bin/chown, /mnt/bin/chmod
> My system:
> OS:
> - DOS/Win3.1
> - OS/2 Warp 4 (dual boot)
> - hopefully soon Debian Linux 1.3.1 (Linux kernel 2.0.29)
Why don't you try Debian 2.0? 1.3.1 is really ancient now.
> Drives:
> - Maxtor 72004 (2 GB, EIDE)
> - IBM DGHS09 (9.1 GB UW-SCSI)
> - Plextor PX-6XCS 2.05 (CD-ROM, SCSI)
Don't boast to much :)
> Any help would be greatly appreciated!
>
> Best wishes and Happy New Year to all Linux experts out there!
>
> Martin Guttenberger
If only all aol users would send such good emails :)
cu
Torsten
pgpltY5d7gsC4.pgp
Description: PGP signature
Problems with drive usage (Debian 1.3.1)
Hello Debian Users..
This mail was caught in a prevention script before going to the
list. If someone could please answer this mail this would be
fine. The Reply-To: is set accordingly.
Thanks,
Alexander
([EMAIL PROTECTED])
--
Alexander Koch - <>< - aka Efraim - PGP - 0xE7694969 - Hannover - Germany
--- Begin Message ---
Hi!
My problem: Debian Linux 1.3.1 (Linux kernel 2.0.29) does not install properly
on my system. I got the Linux version together with a book on Linux-databases,
which recommends to install the following partitions:
- prim 83 / 60 (within the 1024 cylinder boundary)
- prim 82 130
- log 83 /usr600
- log 83 /home 200
- log 83 /var200
- log 83 /tmp 100
- log 83 /adabas 400
- log 83 /httpd 200
I already have 5 FAT16 (1 primary) and 4 HPFS partitions on my IBM DGHS09UW
SCSI-drive but there is sufficient free space left. The block size seems to be
512. Error messages upon booting the kernel during istallation:
- Warning: Unknown PCI device (104c:3d07).
- Failed initialization of WD-7000 SCSI card.
- PPA: unable to initialize controller at 0x378, eror 2.
The error messages upon partitioning/initialization:
When I try to add the new partitions to the begin of the empty space, cfdisk
0.8i labels the remainder "unusable", after I add the two primary partitions
(/ and swap).
When I try to add the new partitions to the end of the unused space, or all of
them as logical partitions, cfdisk installs all of them. But as soon as I try
to initialize the new partitions, the system fails to work properly when I
arrive at /dev/sda16 ("is the entire device, not just one partition").
Initializing the partitions in the reversed order yields: "Could not stat
/dev/sda18 - no such file or directory" although cfdisk shows the correct
entry in the partition table.
What can I do to work around that problem?
My system:
OS:
- DOS/Win3.1
- OS/2 Warp 4 (dual boot)
- hopefully soon Debian Linux 1.3.1 (Linux kernel 2.0.29)
Drives:
- Maxtor 72004 (2 GB, EIDE)
- IBM DGHS09 (9.1 GB UW-SCSI)
- Plextor PX-6XCS 2.05 (CD-ROM, SCSI)
Grafics-adapter: ELSA winner 2000 office, 4 MB (BIOS: 7.03.04; Bus: PCI)
Colordepth: 8 bpp
Resolution: 1280*1024
Refreshrate: 75 Hz
Mainboard: Tyan Tomcat II, Revision: 3.02, BIOS: Award 4.51 PG 1996, Chipset:
Triton2
Processor: AMD K5, 90 MHz
RAM: 48 MB
Soundcard: CreativeLabs Soundblaster 16
SCSI-board: Adaptec 2940UW
Screen: IBM P70
Any help would be greatly appreciated!
Best wishes and Happy New Year to all Linux experts out there!
Martin Guttenberger
--- End Message ---
