Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: AbNoRMiS on September 28, 2012, 01:48:56 AM
-
since tc 4.6 i get this message twice during each pc shutdown or reboot
according a few info that i found about this i'm not sure that it is mistake
but in earlier tc versions this message was not displayed on screen
-
I have noted such as well - suspecting it happens with umount...
-
but i did not find info where someone explain why this happens exactly twice but not another number
i found only questions with assumptions but don't found oficial explanation from busybox developers
more interested how it happened starting from tc 4.6 but not from tc 4.5.5 when was last busybox update
-
I have observed same with 4.5.4
-
it is also very strange because for me it happened after updating to tc4.6
and first i thought that the end has come for my pendrive :D
-
hi friends,
i've heard that this message is nothing serious, even no error message...
... more something like a feature of the recent kernels.
dig in the web and you will get some more answers about that.
-
Yes, not a serious warning. A feature of busybox umount.
-
I have observed same with 4.5.4
it is also very strange because for me it happened after updating to tc4.6
and first i thought that the end has come for my pendrive :D
only through curiosity want to ask whether anyone opinions why may be such difference between tinycore versions when this messages was manifested?
-
ezremaster.cfg
cd_location = /mnt/sda7/ISOS/Core-4.6.1.iso
temp_dir = /tmp/ezremaster
mydata = /mnt/sda5/core2/tce/mydata.tgz
app_inside_initrd_onboot = firmware-iwlwifi.tcz
app_inside_initrd_onboot = wifi.tcz
app_inside_initrd_onboot = Xprogs.tcz
app_inside_initrd_onboot = wbar.tcz
app_inside_initrd_onboot = jwm.tcz
app_inside_initrd_onboot = xf86-video-v4l.tcz
app_inside_initrd_onboot = xf86-video-nv.tcz
app_inside_initrd_onboot = Xorg-7.6.tcz
app_inside_initrd_onboot = flash11.tcz
app_inside_initrd_onboot = ossxmix.tcz
app_inside_initrd_onboot = OSS_alsa.tcz
app_inside_initrd_onboot = ememoa.tcz
app_inside_initrd_onboot = ipv6-3.0.21-tinycore.tcz
app_inside_initrd_onboot = curl.tcz
app_inside_initrd_onboot = hicolor-icon-theme.tcz
app_inside_initrd_onboot = dejavu-fonts-ttf.tcz
app_inside_initrd_onboot = ttf-bitstream-vera.tcz
app_inside_initrd_onboot = Mplayer-xorg.tcz
app_inside_initrd_onboot = chromium-browser.tcz
app_inside_initrd_onboot = emelfm.tcz
app_inside_initrd_onboot = epdfview.tcz
app_inside_initrd_onboot = flpicsee.tcz
ññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññ
tc@box:~$ dmesg
~~~~~~~~~
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
umount: sending ioctl 4c01 to a partition!
umount: sending ioctl 4c01 to a partition!
EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
umount: sending ioctl 4c01 to a partition!
umount: sending ioctl 4c01 to a partition!
EXT4-fs (sda6): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
umount: sending ioctl 4c01 to a partition!
umount: sending ioctl 4c01 to a partition!
umount: sending ioctl 4c01 to a partition!
umount: sending ioctl 4c01 to a partition!
EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
umount: sending ioctl 4c01 to a partition!
umount: sending ioctl 4c01 to a partition!
~~~~~~~~~~~~~
ññññññññññññññññññññññññññññññññññññññññññññññññññññññññ
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1807 14512096+ 83 Linux
/dev/sda2 2068 12161 81079993 5 Extended
/dev/sda3 1807 2067 2091008 82 Linux swap
/dev/sda5 10244 11037 6375424 83 Linux
/dev/sda6 11038 11552 4136706 83 Linux
/dev/sda7 11553 12161 4891761 b Win95 FAT32
/dev/sda8 2068 10243 65673657 83 Linux
ñññññññññññññññññññññññññññññññññññ
-
I have observed same with 4.5.4
it is also very strange because for me it happened after updating to tc4.6
and first i thought that the end has come for my pendrive :D
only through curiosity want to ask whether anyone opinions why may be such difference between tinycore versions when this messages was manifested?
Specific setup may play a role, i.e. causing an umount while running on boot/shutdown console.
-
yes, seems i can to believe in this looking at previous post :)
thanks everyone for your responses