This is a discussion on target partition has become full ?? within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hello everybody, I've encountered the following situation while installing Slackware 10.0. The setup stops with the message ERROR: TARGET ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello everybody, I've encountered the following situation while installing Slackware 10.0. The setup stops with the message ERROR: TARGET PARTITION FULL At the same time, df -h gives: Filesystem Size Used Avail Use% Mounted on /dev/fd2 6.2M 6.2M 0 100% / /dev/fd0 1.4M 348k 992k 26% /floppy /dev/hda1 384M 64M 320M 17% /mnt /dev/hda3 675M 164M 511M 25% /mnt/usr /dev/hda5 478M 33M 445M 7% /mnt/var /dev/hda6 886M 33M 854M 4% /mnt/home /dev/hda7 157M 33M 124M 21% /mnt/tmp /dev/hdd 651M 652M 0 100% /var/log/mount Thus _none_ of the partitions that seem to be important is full. (fd0 is used to mount a floppy with custom tagfiles. hdd is for the CD-ROM drive. I have no idea about fd2. I expect that this is a virtual fs.) Any ideas what can be wrong? TIA, Mikhail |
| |||
| Mikhail Zotov wrote: > Hello everybody, > > I've encountered the following situation while installing > Slackware 10.0. The setup stops with the message > > ERROR: TARGET PARTITION FULL > > At the same time, df -h gives: > > Filesystem Size Used Avail Use% Mounted on > /dev/fd2 6.2M 6.2M 0 100% / > /dev/fd0 1.4M 348k 992k 26% /floppy > /dev/hda1 384M 64M 320M 17% /mnt > /dev/hda3 675M 164M 511M 25% /mnt/usr > /dev/hda5 478M 33M 445M 7% /mnt/var > /dev/hda6 886M 33M 854M 4% /mnt/home > /dev/hda7 157M 33M 124M 21% /mnt/tmp > /dev/hdd 651M 652M 0 100% /var/log/mount > > Thus _none_ of the partitions that seem to be important is full. > > (fd0 is used to mount a floppy with custom tagfiles. > hdd is for the CD-ROM drive. > I have no idea about fd2. I expect that this is a virtual fs.) > > Any ideas what can be wrong? > > TIA, > Mikhail /dev/fd2 is your root ("/") partition. Maybe you did not mean to use that as your "/" ? DB |
| |||
| DB wrote: > Mikhail Zotov wrote: >> Hello everybody, >> >> I've encountered the following situation while installing >> Slackware 10.0. The setup stops with the message >> >> ERROR: TARGET PARTITION FULL >> >> At the same time, df -h gives: >> >> Filesystem Size Used Avail Use% Mounted on >> /dev/fd2 6.2M 6.2M 0 100% / >> /dev/fd0 1.4M 348k 992k 26% /floppy >> /dev/hda1 384M 64M 320M 17% /mnt >> /dev/hda3 675M 164M 511M 25% /mnt/usr >> /dev/hda5 478M 33M 445M 7% /mnt/var >> /dev/hda6 886M 33M 854M 4% /mnt/home >> /dev/hda7 157M 33M 124M 21% /mnt/tmp >> /dev/hdd 651M 652M 0 100% /var/log/mount >> >> Thus _none_ of the partitions that seem to be important is full. >> >> (fd0 is used to mount a floppy with custom tagfiles. >> hdd is for the CD-ROM drive. >> I have no idea about fd2. I expect that this is a virtual fs.) >> >> Any ideas what can be wrong? >> >> TIA, >> Mikhail > > > /dev/fd2 is your root ("/") partition. Maybe you did not mean to use > that as your "/" ? > He's installing, /dev/fd2 is really an initrd, /mnt and friends are the partitions he's installing to, and /dev/hdd is his slackware install cd. To the op: maybe you've run out of inodes. Try df -i. |
| |||
| MikeyD <m_donaghy50@hotmail.com> wrote in message news:<414718b7$0$55401$ed2619ec@ptn-nntp-reader03.plus.net>... > DB wrote: > > > Mikhail Zotov wrote: > >> I've encountered the following situation while installing > >> Slackware 10.0. The setup stops with the message > >> > >> ERROR: TARGET PARTITION FULL > >> > >> At the same time, df -h gives: > >> > >> Filesystem Size Used Avail Use% Mounted on > >> /dev/fd2 6.2M 6.2M 0 100% / > >> /dev/fd0 1.4M 348k 992k 26% /floppy > >> /dev/hda1 384M 64M 320M 17% /mnt > >> /dev/hda3 675M 164M 511M 25% /mnt/usr > >> /dev/hda5 478M 33M 445M 7% /mnt/var > >> /dev/hda6 886M 33M 854M 4% /mnt/home > >> /dev/hda7 157M 33M 124M 21% /mnt/tmp > >> /dev/hdd 651M 652M 0 100% /var/log/mount > >> .... > >> Any ideas what can be wrong? > >> > >> TIA, > >> Mikhail > > > > > > /dev/fd2 is your root ("/") partition. Maybe you did not mean to use > > that as your "/" ? > > > He's installing, /dev/fd2 is really an initrd, /mnt and friends are the > partitions he's installing to, and /dev/hdd is his slackware install cd. > To the op: maybe you've run out of inodes. Try df -i. Thanks for the reply! At the moment when the error occurs, df -Ti gives Filesystem Type Inodes IUsed IFree IUse% Mounted on /dev/hda# reiserfs 4294967295 0 4294967295 0% /mnt/... for all partitions under /mnt. Surprisingly, it is possible to hit <Enter> and finish the installation process. Nothing really wrong seems to happen. (I thought the the HDD can be bad and tried another one---with _exactly_ the same result!) Regards, Mikhail |
| |||
| Mikhail Zotov wrote: > Hello everybody, > > I've encountered the following situation while installing > Slackware 10.0. The setup stops with the message > > ERROR: TARGET PARTITION FULL > > At the same time, df -h gives: > > Filesystem Size Used Avail Use% Mounted on > /dev/fd2 6.2M 6.2M 0 100% / > /dev/fd0 1.4M 348k 992k 26% /floppy > /dev/hda1 384M 64M 320M 17% /mnt > /dev/hda3 675M 164M 511M 25% /mnt/usr > /dev/hda5 478M 33M 445M 7% /mnt/var > /dev/hda6 886M 33M 854M 4% /mnt/home > /dev/hda7 157M 33M 124M 21% /mnt/tmp > /dev/hdd 651M 652M 0 100% /var/log/mount > > Thus _none_ of the partitions that seem to be important is full. > > (fd0 is used to mount a floppy with custom tagfiles. > hdd is for the CD-ROM drive. > I have no idea about fd2. I expect that this is a virtual fs.) > > Any ideas what can be wrong? > > TIA, > Mikhail Looking over the numbers from above, I see that you are using a disk with about 2.5 Gigs of space. If you are installing everything from the Slackware CD's, then you will need (not including any home directories) at least 3.0 Gigs of contiguous hard drive space. I see problems with your partitioning, like your 'var' partition size of 478 Meg. That is too high by a factor of ten. (My entire var directory tree is about 38.5 Megs on a fully loaded Slackware 10.0 system). With your limited disk size, the var partition robs space from other partitions. Here is what I would recommend, in your case, to get the maximum use out of your hard drive size: First, make your Slackware installation all in one single partition. Second, do not install items that you will not use, such as TeK, (unless you are into type-setting or such.) Third, if you are going to use a window manager, such as KDE or Gnome, choose which one you will use and not install the other. If you will not use either KDE nor Gnome, then by not installing them, you will save a lot of disk space. Fourth: Consider not loading things that you will not use and can access later, such as the 'Many FAQs and HOW-TOs'. (These are accessible on the web.) If you don't do database, don't install them, etc. Hope this suggestion helps you out, some. -- humjohn AT aerosurf DOT net |
| |||
| HJohnson wrote : > If you are installing everything from the Slackware CD's, then you > will need (not including any home directories) at least 3.0 Gigs of > contiguous hard drive space. I finally had the time to install Slackware 10 on my laptop, and a full install only without kdei takes up exactly 2732 Megs. -- Thomas O. This area is designed to become quite warm during normal operation. |
| |||
| HJohnson <HuMJohn@aeroSurf.net> wrote in message news:<2qr4p8F12n0ljU2@uni-berlin.de>... > Mikhail Zotov wrote: > > Hello everybody, > > > > I've encountered the following situation while installing > > Slackware 10.0. The setup stops with the message > > > > ERROR: TARGET PARTITION FULL > > > > At the same time, df -h gives: > > > > Filesystem Size Used Avail Use% Mounted on > > /dev/fd2 6.2M 6.2M 0 100% / > > /dev/fd0 1.4M 348k 992k 26% /floppy > > /dev/hda1 384M 64M 320M 17% /mnt > > /dev/hda3 675M 164M 511M 25% /mnt/usr > > /dev/hda5 478M 33M 445M 7% /mnt/var > > /dev/hda6 886M 33M 854M 4% /mnt/home > > /dev/hda7 157M 33M 124M 21% /mnt/tmp > > /dev/hdd 651M 652M 0 100% /var/log/mount > > > > Thus _none_ of the partitions that seem to be important is full. > > > > (fd0 is used to mount a floppy with custom tagfiles. > > hdd is for the CD-ROM drive. > > I have no idea about fd2. I expect that this is a virtual fs.) > > > > Any ideas what can be wrong? > > > > TIA, > > Mikhail First of all, thanks for the reply! > Looking over the numbers from above, I see that you are using a disk > with about 2.5 Gigs of space. If you are installing everything from the > Slackware CD's, then you will need (not including any home directories) > at least 3.0 Gigs of contiguous hard drive space. Yes, you are quite right about the HDD size. The point is that I am trying to configure a router on an old PC. Thus I need less than 200Mb of Slackware packages to install. Even less space is occupied after I delete docs and international man pages. > I see problems with your partitioning, like your 'var' partition size of > 478 Meg. That is too high by a factor of ten. (My entire var directory > tree is about 38.5 Megs on a fully loaded Slackware 10.0 system). With > your limited disk size, the var partition robs space from other partitions. Thanks for the idea! I have repartitioned the drive. Still, the situation remains mysterious. A similar `bare bones' installation of Slack 9.1 runs smoothly. A full Slack 10.0 installation on a large HDD also runs fine. Thus I expect that something is wrong with the way Slack 10's installer works with small HDDs. I have tried to employ ext3 instead of ReiserFS but with the same result :-( Regards, Mikhail |
| |||
| Hi, 2004-09-14, Mikhail Zotov wrote: > Hello everybody, > > I've encountered the following situation while installing > Slackware 10.0. The setup stops with the message > > ERROR: TARGET PARTITION FULL > > At the same time, df -h gives: > > Filesystem Size Used Avail Use% Mounted on > /dev/fd2 6.2M 6.2M 0 100% / > /dev/fd0 1.4M 348k 992k 26% /floppy > /dev/hda1 384M 64M 320M 17% /mnt > /dev/hda3 675M 164M 511M 25% /mnt/usr > /dev/hda5 478M 33M 445M 7% /mnt/var > /dev/hda6 886M 33M 854M 4% /mnt/home > /dev/hda7 157M 33M 124M 21% /mnt/tmp > /dev/hdd 651M 652M 0 100% /var/log/mount > > Thus _none_ of the partitions that seem to be important is full. [snip] I had similar (?) problems when installing Slack10. I made a 512 MB / and a 3 GB /usr, plus seperate /tmp and /var, /home, /usr/local and /var/spool directories. The installer would put everything on /, which would naturally fill up during install, and the install would fail. I had to make a 4 GB / directory to get slack10 installed. Is there a bug in the installer? -peter |
| |||
| muxaul@lenta.ru (Mikhail Zotov) wrote in message news:<d53a20c7.0409140610.51bde3ee@posting.google. com>... > Hello everybody, > > I've encountered the following situation while installing > Slackware 10.0. The setup stops with the message > > ERROR: TARGET PARTITION FULL > > At the same time, df -h gives: > > Filesystem Size Used Avail Use% Mounted on > /dev/fd2 6.2M 6.2M 0 100% / > /dev/fd0 1.4M 348k 992k 26% /floppy > /dev/hda1 384M 64M 320M 17% /mnt > /dev/hda3 675M 164M 511M 25% /mnt/usr > /dev/hda5 478M 33M 445M 7% /mnt/var > /dev/hda6 886M 33M 854M 4% /mnt/home > /dev/hda7 157M 33M 124M 21% /mnt/tmp > /dev/hdd 651M 652M 0 100% /var/log/mount > > Thus _none_ of the partitions that seem to be important is full. > .... > Any ideas what can be wrong? > > TIA, > Mikhail I have found the reason of such a strange behavior of the installer. During installation, I used the "tagpath" mode with tagfiles written on a floppy. Besides Slackware's a, ap, d, ... directories the floppy contained a couple of folders with names different from those of Slackware series. This caused the installer to make a mistake. Mikhail |
| ||||
| > I have found the reason of such a strange behavior of the installer. > During installation, I used the "tagpath" mode with tagfiles written > on a floppy. Besides Slackware's a, ap, d, ... directories the > floppy contained a couple of folders with names different from > those of Slackware series. This caused the installer to make > a mistake. > The installer probably thought those were infinite disksets, because it relies on the install.end file to tell it where a diskset ends. Remember the installer is still really floppy-oriented. |