df can't see size and usage of rootfs - MSI Wind U100 - TC 6.2 x86

[gerald_clark]

Linux does not know what bootloader was used, nor what it booted off of.
Unless you are using the exact same kernel, initrd, tce directory, home, opt, and boot codes the two bootups are not the same.
I suspect you are loading something that causing your problem.

[Misalf]

Well, what could be a little weird boot method from my side, is that I have syslinux on sda1 which loads Windows or chainloads to extlinux on sda3 where I have my Linux stuff.
I wasn't able to boot Linux directly from sda1 so I have this weird setup.
I now chainload from Syslinux on sda1 to Grub4DOS on sda1 which in turn boot Linux on sda3.

O.o

I can assure you that "kernel, initrd, tce directory, home, opt" are in fact the exact same.
"and boot codes" may have slight differences, though. However, even with only the necessary boot codes I got the same result.

Code: [Select]

LABEL core62test
MENU LABEL Tiny Core 6.2
KERNEL /tce-6.x/boot/vmlinuz
APPEND root=/dev/sda3 initrd=/tce-6.x/boot/core62.gz,/tce-6.x/boot/more-test-62.gz,/tce-6.x/boot/fonts-test.gz,/tce-6.x/boot/xorg.gz,/tce-6.x/boot/intel.gz  vga=788 video=vesafb:ywrap,mtrr:3  logo.nologo  quiet loglevel=4  mydata=myxorg  kmap=qwertz/de-latin1  noutc tz=CET-1CEST,M3.5.0,M10.5.0/3  tce=UUID="cb6f8b98-91fd-4c96-b115-3d2bb9cb3e57"/tce-6.x  laptop  nodhcp  desktop=openbox  blacklist=pcmcia,ssb,b43,bcma,rt2860sta,bluetooth,btusb 


Code: [Select]

timeout 0
default 0

title Tiny Core Linux
find --set-root /tce-6.x/boot/vmlinuz
kernel /tce-6.x/boot/vmlinuz  logo.nologo  quiet loglevel=3  vga=788 video=vesafb:ywrap,mtrr:3  blacklist=pcmcia,ssb,b43,bcma,rt2860sta,bluetooth,btusb  kmap=qwertz/de-latin1  noutc tz=CET-1CEST,M3.5.0,M10.5.0/3  tce=UUID="cb6f8b98-91fd-4c96-b115-3d2bb9cb3e57"/tce-6.x  mydata=myxorg  laptop  nodhcp  desktop=openbox 
initrd /tce-6.x/boot/core62.gz /tce-6.x/boot/more-test-62.gz /tce-6.x/boot/fonts-test.gz /tce-6.x/boot/xorg.gz /tce-6.x/boot/intel.gz 


Also, if changing back and fourth from syslinux to grub4dos and back to syslinux (I didn't plan this - was an accident (: ), then booting Linux, Linux thinks I have only 1GB of RAM instead of 2GB.
So, even if Linux doesn't know about any of this, maybe the bootloaders do some memory hacks which don't work as expected or getting wrong information from the BIOS?
It's not the most expensive netbook. Plop Boot Manager is known to have problems booting off of USB on some laptops apparently because the BIOSes don't always stick to the standards.

[gerald_clark]

You have something messed up in one of your initrds.
As I stated before. Boot STOCK initrd only.  We can't troubleshoot your custom initrds.

[Misalf]

You probably missed my reply?

You are not running a standard core system.  You are loading multiple initrds

True, yet it works on other computers.

Boot a stock core and see if the problem persists.

The problem does persist. I freshly downloaded the 6.2 versions of core.gz and vmlinuz booted from /tce/boot/ without any extensions using this boot stanza via grub4dos

Code: [Select]

LABEL core62def
MENU LABEL Tiny Core 6.2 Default
KERNEL /tce/boot/vmlinuz
APPEND root=/dev/sda3 initrd=/tce/boot/core.gz  noutc tz=CET-1CEST,M3.5.0,M10.5.0/3  tce=UUID="cb6f8b98-91fd-4c96-b115-3d2bb9cb3e57"/tce  laptop  nodhcp 


Anyway, the issue can be worked around quite easily. As long as nobody else suffers from this, whether if it's a configuration incompatibility or a bug, I consider it solved for myself. Even when I boot stock Core, my boot setup might be unusual.

[gerald_clark]

I have no idea what you have in your tce directory, or what is in your onboot.lst.
Add "base norestore" to your boot options.  That will limit it it "Tiny Core Base" issues.  Otherwise it belongs in the extension bugs forum, and you can start checking extensions one-by-one.

[gerald_clark]

Another thing ... make sure you do not have any .gz files in your tce directory, or they will be loaded over the top of the root file system.

[Misalf]

Thanks Gerald, I know you're trying to help and also trying to make sure it's not Core's fault.
But really, I have already made sure it's not because of any modifications I did, nor any extensions, by booting stock Core, just core.gz and vmlinuz, which gives same results.

The problem does persist. I freshly downloaded the 6.2 versions of core.gz and vmlinuz booted from /tce/boot/ without any extensions

[...]
It's just my box that's acting strange. Kinda old MSI Wind U100 netbook.
This is also true If I boot with  base norestore  boot codes.
[...]

It's 100% reproducible:
Syslinux -> Extlinux -> Core Linux = size of rootfs displayed incorrectly.
Grub2 -> Core Linux = size of rootfs displayed OK.
Syslinux -> Grub4DOS -> Core Linux = size of rootfs displayed OK.

Without having much knowledge about this topic, I'd guess it's either this particular netbook which gives values unexpected by Syslinux, or my Syslinux config needs to be changed, since everything works as expected when I use another bootloader.

[Misalf]

I have also fsck'ed the partition that holds Extlinux. Seems to be alright.

[Misalf]

I have no idea what you have in your tce directory

While testing stock Core, nothing was stored in my tce directory.
Except one folder  /boot  which contains  core.gz  and  vmlinuz .

Code: [Select]

/tce/
    /boot/
        core.gz
        vmlinuz
Should be enough, right?

[coreplayer2]

I've always placed boot alongside tce at the drive level, can't say I've ever seen boot inside of tce before,
tce is for extensions..

Normally I install like this

sda1
    /boot
    /tce

[gerald_clark]

TC-install creates /tce/boot/ on the boot drive.

[coreplayer2]

OK thanks

[curaga]

If you could test the latest extlinux, I'm sure the syslinux project would like to hear if the bug still applies.