SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hello
when I'm typing "reboot" my computer (linux slackware-current, 2.6.6) display messages on screen - this is ok !
but when (the last one is) Rebooting.....
I have two more messages: !
when you reboot, all hardware resets.. thats why it's called reboot.
the 2.6.6 kernel has a new way of flushing the IDE devices at shutdown or reboot, that's why you didn't see this before whit earlier kernels
when you reboot, all hardware resets.. thats why it's called reboot.
the 2.6.6 kernel has a new way of flushing the IDE devices at shutdown or reboot, that's why you didn't see this before whit earlier kernels
The only thing that happens is the cache of the disk is flushed, and then the drive suspends.
This does not damage your drive
It would be another story when the disk was actally powered down, but that isn't happening here. It only suspends, meaning it goes into a 'low-power mode'.
Originally posted by EyesOnly I don't get your problem really
The only thing that happens is the cache of the disk is flushed, and then the drive suspends.
This does not damage your drive
It would be another story when the disk was actally powered down, but that isn't happening here. It only suspends, meaning it goes into a 'low-power mode'.
Originally posted by ringwraith and you tested this with a meter?
lol !!!!!!!!!!!!!!!
I hear that disc switches itself off totally !!!!!
After restart, in moment of detecting of discs - My disc starts just and fly to wait 5 seconds to he took speeds
sorry for English !
but I tell you - my disc(s) isn't in any "suspend mode", "sleep mode"
or somethings else !
Distribution: Mainly Slackware, but test run various different distros.
Posts: 77
Rep:
Quote:
Originally posted by zulik this isn't normal !!
this is shit !!
this is bad for harddisk !!
is any change to set this back ? (2.6.5)
Actually, that is normal.
its not sh!$, its supposed to happen that way.
Its not bad for harddisks at all..
Back in Winblowz world when you reboot your machine, the cache is flushed then all hardware activity is stopped and then restarted.
Even in the older kernels your drives stopped and then restarted, you just didnt get a message that they did that. Im not sure why you would want your drives to stay active on a reboot. are you getting errors on restart, which cause your excited concern?
I think you probably just notice it now because you are paying attention due to the messages. My system has always basically halted completely then restart. Don't worry, be happy :-)
I have the same problem, but I'm using Fedora Core 2 (Kernel 2.6.5, older kernel in Core 1 didn't have this problem). From the menu bar, I select log out->restart computer, everything is normal, and the very last 2 lines before the restart are:
shutdown hda
shutdown hdb
Then the computer restarts. This actually spins down the drive, fully, not lower power or anything. The computer then promptly reboots, BUT in my case, while both drives are spinning up, the bios is searching for them, they don't spin up fast enough and the bios startup complains and says something like "primary master and slave not found, press f1 to continue..." etc etc and then waits indefinitely.
Now this is very bad since I have to be manually at the keyboard to reboot again (not to mention the damage caused to the drives every single restart). I sometimes restart my computer through VNC, not that isn't possible. I also have a dual boot setup between XP and Fedora, I don't boot into XP often, but now if I do, I'll be damaging my drives everytime.
Don't believe me? it's a known kernel bug (for IDE drives, SCSI drives are fine):
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.