Trouble with boot partition size

[Gianni]

Hello everyone,
I'm new on this forum and I'm new to Tiny Core (pretty new to linux also..). I spent the last days doing a manual install on a very old laptop (48MB ram, 10GB hdd) following this guide: http://tinycorelinux.net/install_manual.html (with some adjustments).
I managed to get things to work. I got to install packages like xorg and openssh and get them to work.
My problem came when I run out of space for extensions, since I create a 100MB partition on the hard drive for the system (I merely followed the guide to keep things simple).
...I wiped everithing and did again the guide, this time making a 1GB boot partition.. Again, it works fine and I'm able to perform stuff, but it seems like there's a problem, since I see the same amount of space avaiable as the first install using df command:

Code: [Select]

tc@box:/$ df
Filesystem                Size      Used Available Use% Mounted on
rootfs                   36.6M     12.7M     23.9M  35% /
tmpfs                    20.4M         0     20.4M   0% /dev/shm
/dev/sda1                87.1M     69.1M     13.3M  84% /mnt/sda1
/dev/loop0              232.0K    232.0K         0 100% /tmp/tcloop/ncurses
/dev/loop1               28.0K     28.0K         0 100% /tmp/tcloop/cfdisk
/dev/loop2              140.0K    140.0K         0 100% /tmp/tcloop/kmaps
/dev/loop3               28.0K     28.0K         0 100% /tmp/tcloop/popt
/dev/loop4                1.8M      1.8M         0 100% /tmp/tcloop/openssl
/dev/loop5               16.0K     16.0K         0 100% /tmp/tcloop/libffi
/dev/loop6              128.0K    128.0K         0 100% /tmp/tcloop/gamin
/dev/loop7                1.4M      1.4M         0 100% /tmp/tcloop/glib2
/dev/loop8              756.0K    756.0K         0 100% /tmp/tcloop/gcc_libs
/dev/loop9               68.0K     68.0K         0 100% /tmp/tcloop/expat2
/dev/loop10             396.0K    396.0K         0 100% /tmp/tcloop/dbus
/dev/loop11             152.0K    152.0K         0 100% /tmp/tcloop/libavahi
/dev/loop12             240.0K    240.0K         0 100% /tmp/tcloop/libcups
/dev/loop13              64.0K     64.0K         0 100% /tmp/tcloop/samba3-libs
/dev/loop14              33.4M     33.4M         0 100% /tmp/tcloop/samba3
/dev/loop15              92.0K     92.0K         0 100% /tmp/tcloop/libedit
/dev/loop16               2.0M      2.0M         0 100% /tmp/tcloop/openssh
/dev/loop17              56.0K     56.0K         0 100% /tmp/tcloop/dosfstools
/dev/sda3                 7.9G    176.9M      7.8G   2% /media/mio

This line:
/dev/sda1                87.1M     69.1M     13.3M  84% /mnt/sda1

...that value is giving me trouble, I need more space in order to install more extensions.
Here's what cfdisk says instead:

Code: [Select]

                           cfdisk (util-linux 2.19.1)

                              Disk Drive: /dev/sda
                        Size: 10056130560 bytes, 10.0 GB
              Heads: 255   Sectors per Track: 63   Cylinders: 1222

    Name        Flags      Part Type  FS Type          [Label]        Size (MB)
 ------------------------------------------------------------------------------
    sda1        Boot        Primary   ext3                              1019.94
    sda2                    Primary   swap                               509.97
    sda3                    Primary   vfat                              8526.23*


...from here it seems alright, from my perspective (during installation I created a swap partition and devolved the remaining to a fat32 partition)
here's fdisk output:

Code: [Select]

Disk /dev/sda: 10.0 GB, 10056130560 bytes
255 heads, 63 sectors/track, 1222 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1   *           1         124      995998+ 83 Linux
/dev/sda2             125         186      498015  82 Linux swap
/dev/sda3             187        1223     8326395   b Win95 FAT32

Any help would be apreciated. Thanks in advance.

[bmarkus]

Do You have a /tce directory in the root of the sda1?

[Gianni]

Do You have a /tce directory in the root of the sda1?

Yes:

Code: [Select]

tc@box:/mnt$ cd sda1
tc@box:/mnt/sda1$ ls
boot/       lost+found/ tce/
tc@box:/mnt/sda1$ ls tce
mydata.tgz   onboot.lst   ondemand/    optional/    provides.db


[curaga]

It sounds like you didn't reformat the partition (with mkfs.ext3), only re-partitioned in cfdisk?

[Gianni]

It sounds like you didn't reformat the partition (with mkfs.ext3), only re-partitioned in cfdisk?

..I can't remember. I guess I could have done a mistake during the installation ( perfectly plausible    ). Is there a way to discover this without repeating the installation? It would be nice to get a little evidence before repeating the manual installation.
If it's not possible I'll go ahead and perform it anyways. Just asking if it's possible to perform some checks.

[bmarkus]

resize2fs /dev/sda1

may help

[Gianni]

I did again the manual install.
Now it looks like it should!
As @curaga mentioned, I must have forgotten to properly format the partition with mkfs.ext3.

After the installation process df gives the expected output:

Code: [Select]

tc@box:~$ df
Filesystem                Size      Used Available Use% Mounted on
rootfs                   36.6M     12.1M     24.5M  33% /
tmpfs                    20.4M         0     20.4M   0% /dev/shm
/dev/sda1               941.3M     16.0M    876.7M   2% /mnt/sda1
/dev/loop0              140.0K    140.0K         0 100% /tmp/tcloop/kmaps
/dev/loop1                1.8M      1.8M         0 100% /tmp/tcloop/openssl
/dev/loop2              232.0K    232.0K         0 100% /tmp/tcloop/ncurses
/dev/loop3               92.0K     92.0K         0 100% /tmp/tcloop/libedit
/dev/loop4                2.0M      2.0M         0 100% /tmp/tcloop/openssh

/dev/sda1               941.3M     16.0M    876.7M   2% /mnt/sda1

Success!!

for the command resize2fs, I tried to look for it in the repository (was missing in the base provided tools) but then everything started to give problems because I finished space on the sda1, so I went for the re-install. Luckily, it was a simple mistake of mine, easily resolved.

Thanks to everyone!

Awesome forum, I never expected such an activity