Everytime when I shut down the computer in Slitaz. The harddisk makes an awful sound. It sounds like when you disconnet the power supply. It is exectly like the Win98 force shut sound. Is it possible to make a smoon quiet shut down. In this way, it would not damage the hard disk. Thanks!
Shut down bug, need to be fix!(11 posts) (5 voices)
What a harddisk you use? Do you hear any other sounds at shutdown? When? Maybe, anyone can help you.
Oh, my mistake. It's Hitachi harddisk SATA controller. It occurs after I click on power off. On black screen says killing all apps. After that, the harddisk make noise and turn off.
Strange, I always hear a quiet click on IDE/SATA drives. It is automatic heads parking on power off. I have desktop'2004 and netbook'2009 and I never heard any weird sounds.
Have you other system on your hdd (windows, ubuntu, etc.)? Is it completely silent on power off?
If the drive was not properly unmounted before shutdown, it could damage the drive. If this happens, then incorrectly unmounted partition exposed so-called dirty bit. You can see that after power on modern systems, such as Windows & Ubuntu/Mint start checking disks for errors. Have you booted into other system and have you seen this checking? If system such as Windows or Ubuntu, or Mint have booted without disk checking this means that with the disk everything is all right in spite of those unknown sounds.
SliTaz is simple system. It have no this checking behavior, but Linux kernel itself mounted disk in read-only mode if dirty bit is set, and you can not modify/write any files on your hard drive, preventing data loss due to disk checking.
You can check your disk for errors via next commands in the terminal:
Type su to become administrator, then input root's password (by default it password is
Type fdisk -l (here small letter L) to get detailed list of your disks and partitions.
Type e2fsck /dev/sda1 to check
/dev/sda1or other value for your disk. Note that you can check only linux ext filesystems using command e2fsck. You can find utility e2fsck in the e2fsprogs package.
Here is my example:
root@slitaz:/home/tux# e2fsck /dev/sdb1
e2fsck 1.41.14 (22-Dec-2010)
LoveBox has been mounted 93 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
LoveBox: 38017/181424 files (10.7% non-contiguous), 504416/724736 blocks
root@slitaz:/home/tux# e2fsck /dev/sdb2
e2fsck 1.41.14 (22-Dec-2010)
/dev/sdb2 is mounted.
WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.
Do you really want to continue (y/n)? no
root@slitaz:/home/tux# e2fsck /dev/sda6
e2fsck 1.41.14 (22-Dec-2010)
Mint: clean, 428055/1327104 files, 2326455/2622603 blocks
Oh, I forgot to tell you that the drive must be unmounted in order to be able to make check. Therefore, a full scan can only be done by booting from the LiveCD / LiveUSB.
In addition to this, you can check the current status of the hard drive using the utility GSmartControl. Install the package gsmartcontrol (click here if you are now in the SliTaz 4.0). You can see the status of disks enabled for SMART (also, make sure that the BIOS is not disabled SMART).
It is sad, but my hard drive can not meet next year.
Thank you! It might work if my BIOS has smart control. However, my PC some how doesn't have this function. Just find out that Slitaz just got too many bugs. Just can't fix them all at once. This is a very good performance and very fast OS, but I believe it just build for experts. I just can't handle too many things that didn't work.
Thank you for all your help!!!!!!!!!
hi yiumun i believe thats trouble is not software problem, maybe your hard disk its failure and you dont know, try to install slitaz in other hard disk and i believe that all works very fine, and slitaz is a very easy distribution and frendly user. grettings to you.
I Just installed Slitaz 3.0. It does not have this issue. It shutdows so smoon and quiet. Yahoo! I am so happy. Actually, version 3.0 is so stable!!!!!! I am so happy with it.
How come 3.0 is so good, and 4.0 has so many bugs. Aren't 4.0 suppose to be better?
SliTaz 4 was somewhat of a rush release. We didn't release in 2 years since SliTaz 3 came out where we used to release yearly.
The trouble was initially caused with the new build server and then with a whole host of broken packages that needed to be fixed. Add to that the new Linux Kernel and Xorg Daemon we had to learn how to use because they changed from when we used them in SliTaz 3. Not to mention our own changes and updates present with the new tools we added like SliTaz Panel. We also grew about another 1000 packages from the previous release.
Basically, we had a lot of untested systems to learn and fix. We tried to get these bugs sorted out by releasing the RC versions, but none of the users really bothered testing them. Finally we released SliTaz 4 and suddenly everybody got around to testing it and finding the bugs we could have fixed in the RC versions...
Luckily, we've learned from our mistakes and SliTaz Cooking is shaping up to be way more stable than SliTaz 4, which means the SliTaz 5 release next year will be even more so.
yes, but trixar, as you say, we rushed 4.0 out, and did not leave enough time for testing
If we want to reduce the number of problems before the code is released, then we first need to set up a group of beta testers who have to give a go before a version is released; they need to be given time to test, and then give the go; otherwise, most betatesting is to check if the CDROM boots and hw is recognised.
If i am given enough time then I setup my environment to work with it and will effectively do productive work with it (or not, if the beta is too much of an alpha)
I volonteer to be one of beta testers, if this helps, (and if i have the time at that time, so as not to slow the process)
You must log in to post.