I am running OpenSUSE 11.2 (but I do not suspect that this is distribution-specific).Linux bach 220.127.116.11-0.1-desktop #1 SMP PREEMPT 2009-12-15 23:55:40 +0100 i686 i686 i386 GNU/Linux.I am running in runlevel 3 while trying to sort this out.When smartd runs, it spins up my Western Digital drives from standby, but not my Samsung drive.Anyone know why blkid, edd_id and devkit-disks-pa are reading my standby drives? And are these reads sufficient to make drives spin up? I'm not sure what to look at next.
I want to use smartd for monitoring my hard disk regularly. What is the interaction of smartd with the hard disk driver that is in use. Whether the hard disk driver should be smart enabled or only the hard disk. Will any one help me in this.
I have a PC which I built ~3 years ago which had been running smoothly and silently until recently. Now, the CPU fan likes to spin up to 1200-1500 RPM even when it's idle, which is rather annoying. I have not made any recent changes (software-wise or hardware-wise) to it.
I installed the lm-sensors and hddtemp packages (via apt-get) and configured them. Here's a typical output at steady-state, where the computer's been idle for a while and the fans have been spinning for the same while:
These all seem fairly normal to me, so I'm perplexed as to why the fan continues to run at such a high RPM. What does the ALARM that's reported for in6 mean? Is it important? I've been playing around with the fancontrol daemon, trying to see if I could get better results than with the default fan management. Using the pwmconfig utility, I generated the following /etc/fancontrol file:
# Configuration file generated by pwmconfig, changes will be lost INTERVAL=10 DEVPATH=hwmon0=devices/pci0000:00/0000:00:18.3 hwmon1=devices/platform/it87.552 DEVNAME=hwmon0=k8temp hwmon1=it8718 FCTEMPS= hwmon1/device/pwm1=hwmon0/device/temp1_input FCFANS= hwmon1/device/pwm1=hwmon1/device/fan1_input MINTEMP= hwmon1/device/pwm1=35 MAXTEMP= hwmon1/device/pwm1=60 MINSTART= hwmon1/device/pwm1=180 MINSTOP= hwmon1/device/pwm1=100
This only sort of worksâ€”as soon as I enable the fancontrol daemon, the fan shuts off at first (good), but the temperatures of the 7 different sensors slowly rise, even when everything is idle. Eventually, when the Core0 Temp sensors goes past 35°, the fan comes back on, and then it alternates from being on and off at around 500-700 RPM, as the temperature goes back and forth across the boundary. It's certainly much more pleasant than 1200-1500 RPM, but it's still far from desirable.
Here's an example of the sensors output in that situation: $ sensors k8temp-pci-00c3 Adapter: PCI adapter Core0 Temp: +36.0°C Core0 Temp: +38.0°C Core1 Temp: +34.0°C Core1 Temp: +30.0°C it8718-isa-0228 Adapter: ISA adapter ..... cpu0_vid: +1.100 V
I opened up the case, and the CPU heat sink felt warm but not excessively hot. I tried taking off the heat sink, cleaning off the thermal paste, putting on new thermal paste, and putting the heat sink back on, but that didn't seem to have much of an effect, if any. The two other heat sinksâ€”one on the built-in AMD 780G graphics chipset and the other on the AMD SB700 southbridgeâ€”felt noticeably hotter than the CPU heat sink. So, my question is this: What should I do to get this computer back to the state where the fan is off when it's idle? Can I solve this with a smarter fancontrol configuration?
I cleaned out the heat sink and fan as best I could with compressed air (there wasn't a whole lot of dust, but I got rid of what I could), but still no dice. Rebooting into the BIOS configuration gives me the same resultsâ€”the fan still runs at 1100-1200 RPM, and the system and CPU temperatures are reported as 40-44°C. Should I add another fan? The integrated GPU and the SB heatsinks felt significantly warmer to the tough than the CPU heatsink. The BIOS reports a system fan speed and NB fan speed of 0 rpm (since I don't have more than one fan).
I am using smartd for monitoring disk's status and i am using smartmontools-5.39.1.tar.gz package for compilation. I am able to compile and run it on HP servers(redhat). Now,i need to execute it for IBM RAID SERVERS too on which compilation is done but i need to configure smartd.conf for them so as to monitor all existing disks. (only DEVICESCAN works in conf file). Rest devices to monitor(eg. ata, sda devices) don't work at all. it is possible in IBM raid servers and if yes, then what configurations should i use.
Why after I boot from runlevel 5 and smartd services is started, I've got a black screen. I know that the GUI is exist but it looks like doesn't appear (black screen). I do following actions : 1. First I check /etc/sysconfig/desktop there is no data (empty), then I add to /etc/sysconfig/desktop this line : DESKTOP=GNOME DISPLAYMANAGER=GNOME
So, at the moment I have a 7TB LVM with 1 group and one logical volume. In all honesty I don't back up this information. It is filled with data that I can "afford" to lose, but... would rather not. How do LVMs fail? If I lose a 1.5TB drive that is part of the LVM does that mean at most I could lose 1.5TB of data? Or can files span more than one drive? if so, would it just be one file what would span two drives? or could there be many files that span multiple drives drives? Essentially. I'm just curious, in a general, in a high level sense about LVM safety. What are the risks that are involved?
Edit: what happens if I boot up the computer with a drive missing from the lvm? Is there a first primary drive?
I have hdparm running and see the reading in gkrellm .dev/sda = 36 celcius in messages smartd: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 108 to 107 Where to change that smartd reading?
I need help for analyzing why after I boot from runlevel 5 and smartd services is started, I've got a black screen.I know that the GUI is exist but it looks like doesn't appear (black screen).I do following actions : 1. First I check /etc/sysconfig/desktop there is no data (empty), then I add to /etc/sysconfig/desktop this line :
I'm having some trouble understanding the smartd configuration options which go in /etc/smartd.conf. I've had smartd running for close to a year now, and read the manual page for smartd and smartd.conf several times, and I still can't get my head around it properly. This is what I use in smartd.conf: /dev/sda -H -f -S on -o on -n standby,q -s (O/../.././(00|06|12|18)|S/../.././11|L/../../(3|6)/21) -m <nomailer> -M exec /usr/sbin/smartd_mailer The above works fine (I use a custom script because I use exim). However, I had two failing hard-disks on two different machines (sector pending attribute) - but I would only receive warning emails if I restarted the machines - not when the periodic tests were being performed. I have a number of questions, if any of you would like to share some light on this:
1. It is not clear from the manual page how the monitoring and alerting mode works. Do I get an initial email when I start smartd if something is wrong, and then no other warning email after each scan, even if there is a fault, unless the fault goes worse? 2. Can I force it to send me warning emails after each test (offline, online, short, long etc.) if the fault condition is still there, even if it hasn't gotten worse? 3. There seem to be a variety of parameters monitored. I was thinking that if I monitor bad sectors, and the hdd temperature - it should be enough to warn me when the hard-disk is failing? Would the -a switch in smartd.conf cover these? 4. I don't understand the difference between monitoring and logging in relation to alerts? Do I get alerts only if I log things? 5. Do I understand correctly that the -p and -u switch would warn me of *any* changes in SMART attributes, even if they don't represent risk of failure? 6. Is there a way of finding out if the scheduled tests (offline, long, short etc.) have been performed?
I recently installed two 160Gb hdds, and use these with striped LVM technics.
now I came across /var/log/messages these lines... :-/ Feb 14 16:50:44 centos55 smartd: Device: /dev/sdf, 34 Offline uncorrectable sectors Feb 14 16:50:44 centos55 smartd: Device: /dev/sdg, 14 Offline uncorrectable sectors
To my understanding, this means that the disk is beginning to fail, and should be replaced..
Short story..I have about 35.000 images on these disks... (shared on network, as a samba share with PCs using Picasa) I've doing backup to 2 separate USB disk, and sometimes I connect a third usb disk and transfer to this aswell. I'm worried now that "some" of my image/data might have been lost - due to the 2 lines above. (checking if something is missing, of the 35.000 images is not easy.. and I have not made any txt file with all files/names/size og the images -...I see now that I also should create such a list, and not just take backup)
How critical is this "Offline uncorrectable sectors" and how can I check/do something about it ?
2 months ago, I built a dedicated backup server using 4 2TB SATA drives for software RAID5 (6TB total). A few days ago, smartd sent out mail saying it found an unreadable sector on one of the drives. I ran selftest using smartctl and the error persisted. So far, neither software RAID nor ext4fs running on top of the RAID volume have reported errors.
MOST OPTIMISTIC: It is normal to have a few bad sectors among billions. Software RAID takes care of alternatives. Keep using the system until RAID spits a more serious warning in the future.
MOST PESSIMISTIC: It is a really bad sign to lead a disaster. No good disk drive should have bad sectors especially when it is only 2 months old. The error is simply not detected by software RAID and ext4. Replace the drive immediately and return the bad drive to the supplier.
I think I have found the problem to my Ubuntu laptop locking up, and it is most likely overheating. Is there any way to keep the CPU fan spinning at 100% constantly? I tried setting it up in the BIOS but it is an old laptop and I can't control it from there.
I updated from 9.10 karmic to 10.04 LTS. Everything worked fine until, I restarted. Upon logout there are no splash screen like I had before in the 9.10, and my fan on my gfx are going crazy, spining at 100%. Well then I got to the grub loader, and discovered my boot splash was gone to. The only thing which is displayed on the screen are: mount dev /dev failed device71 Starting up. Then 10 seconds later alot of texts shows up and I get the login screen. I've looked around on the forum and other sites for a solution, but with no luck.
it gets the hdd very warm and keeps the fan on constantly as well generally heating the whole system . was so bad i ended up having to go back to windows anything i can do to get the hdd to go in standy by when in active like windows ???? cause i hate windows and love ubuntu but i dont wanna burn up my machine to keep ubuntu
I am a regular ubuntu user from 7.10 till now. Now I am using 11.04. This problem never happened with previous releases. When I open more than 4 windows in firefox or whenever I open "Ubuntu Software Center" the hard disk keeps spinning, mouse and keyboard are frozen. I tried to reboot from tty1. It takes around 3 minutes to get the command prompt after pressing Ctrl + Alt + F1. I reinstalled 11.04 several times. This problem is not solved. I have applied all the updates. What program is exactly causing this problem?
I have got an Acer 3820T laptop. Among many problems that it seems to have with linux, the most critical one is that when I boot into linux, the fan stops spinning. I have already verified that the relevant modules are loaded into the kernel,
~$ modprobe --first-time -a processor thermal fan acpi-cpufreq coretemp Password: WARNING: Module processor already in kernel (builtin). WARNING: Module thermal already in kernel (builtin).
What I have noticed on several versions of Ubuntu, both 32 and 64 bit (including 9.10, 10.04 b2 and UNR 9.10) is that after the launch of Firefox (including the current 3.6.3 version), I continue to get a spinning cursor for more than 10 seconds after the FF window is present and ready to accept input. Sometimes I get it only when moving the cursor outside the FF window and other times it will be in the window, too. I have even noticed it persist for a short time after quitting FF. I think it's definitely related to FF because I don't see this occur unless FF is launched, not even when another browser (Chromium in this case) is launched. To add to the mystery, I see it in Ubuntu and Mint 8 xfce, but not in Ubuntu-based distros with simpler window managers like Mint 8 fluxbox or CrunchBang 9.04 (openbox). To try to get rid of this, I have tried various FF configuration speedups available from the Net - changes implemented through about:config. These do speed up FF, but they don't get rid of the spinning wheel.As far as I can tell, the spinning wheel has no impact on FF operation - it doesn't stop me from entering a url and accessing it, though perhaps it slows down implementation.
I'm running the latest slackware64-current on my Dell laptop (Inspiron 1420). I rarely run it on battery power, so I don't know when this behavior started, but now it seems when I'm on battery power the hard drive likes to spin down and then spin up. This is not after 5 minutes or so of inactivity. This is 30 seconds of inactivity because I'm reading a web page or something. There is a noticable delay in the response of the system as a whole when the drive is having to spin back up. I'm also using xfce-4.6.2 with the xfce power manager. I've checked the settings, and I don't see anything about spinning down the hard drives. I've also looked through some ACPI rules, but I'm coming up empty.
When I run Ubuntu liveCD (Lucid), even when no programs are running and cpu is 98% idle, the CD Rom continues spinning constantly, even though it apparently isn't accessing any files. At this rate, the motor will burn out prematurely.I don't think this is normal. How can I troubleshoot this and keep it from running?
i am unable to play bbc videos although videos and other videos work fine. i believe i have the latest flash player installed and i installed bbc iplayer from the software center of ubuntu. i am running 64 bit ubuntu 10.10. when i click on a video on bbc i see the photo showing the start of the video but it doesn't progress past that; i just get the hourglass (wheel?) spinning around for a long time.
No matter if it is safe mode or regular the computer stops booting at Starting smartd I installed wine and samaba files (through Yast) before I restarted the computer and I was looking in FSTAB to get my HD's working. I didn't make any changes to FSTAB (I didn't even save the file).
I'm trying to install v10.10 on my Sony Vaio VGN-NS150J, 4gb ram, 2gb core 2 duo, 320 gb HD...to no avail. The live CD boots, but the dvd drive stops spinning after i click the install button...the one that says i can't turn back. Nothing seems affected by quitting the install. I have no idea what to do except to not turn back to VistaOS. I intensely dislike that "operating system".
I've been using Ubuntu 10.x for several months without any major problems. Everything was fine until this week.
In the past few days there's been a strange new problem. When I turn my computer on, it works fine for 10 minutes, and then the hard drive suddenly starts spinning and won't stop. While this happens the computer is virtually unusable. Mouse moves slow and jerky; apps don't respond; and eventually the windows close by themselves, the whole screen goes blank, and the system reboots. The whole process takes a long time, sometimes 30 minutes.
The only change I made just before this problem started was upgrading Firefox Beta 4 version 10 to the latest version 11. So, I deleted it, and went back to the latest stable version 3.6.x. That seemed to fix the problem for a day or so. But then it started happening again. I deleted all signs of Firefox; it still happens. So it's not a browser issue.
I am stumped. Today I started my computer and just let it sit there without opening any programs at all except the system monitor. It ran fine for the usual 10-15 minutes, nothing changed out of the ordinary in terms of computer resources used in the system monitor, and then suddenly the drive started spinning wildly again .....
Right now my computer's been on for 10 minutes and I am typing this message .... but who knows what will happen right now.
First of all I have to say I love Fedora, just switched from openSuSE after the system was kinda sluggish the last 2 or 3 versions. But one thing I always liked was the fact that when the system went into suspend my external harddrive spun down and after resuming it spun up again as soon as I tried to access a file. Now in Fedora the harddrive continues spinning and is unavailable after resuming. There is nothing about the harddrive in dmesg, not during suspending and not even when i unplug it after resuming.