Strange hdd remounting entries in journal

Hi, Im getting this in my journal every now and again:
*Edit
The "Found device" and remounting and fscking specifically
Apr 03 20:24:15 russell-server systemd[1]: Reloading.
Apr 03 20:24:15 russell-server systemd[1]: Started CUPS Printing Service.
Apr 03 20:24:15 russell-server systemd[1]: Mounted /storage.
Apr 03 20:24:15 russell-server systemd[1]: Mounted /.
Apr 03 20:24:15 russell-server systemd[1]: Reached target Local File Systems (Pre).
Apr 03 20:24:15 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:15 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:15 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:15 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:15 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:15 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:15 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:15 russell-server systemd[1]: Starting File System Check on /dev/disk/by-uuid/a628b153-4f97-45f7-b8b1-23c3557cdd72...
Apr 03 20:24:15 russell-server sudo[15149]: pam_unix(sudo:session): session closed for user root
Apr 03 20:24:16 russell-server systemd[1]: Started File System Check on /dev/disk/by-uuid/a628b153-4f97-45f7-b8b1-23c3557cdd72.
Apr 03 20:24:25 russell-server sudo[15176]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/vim /etc/conf.d/plexmediaserver
Apr 03 20:24:25 russell-server sudo[15176]: pam_unix(sudo:session): session opened for user root by admin(uid=0)
Apr 03 20:24:33 russell-server sudo[15176]: pam_unix(sudo:session): session closed for user root
Apr 03 20:24:41 russell-server sudo[15178]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/systemctl --system daemon-reload
Apr 03 20:24:41 russell-server sudo[15178]: pam_unix(sudo:session): session opened for user root by admin(uid=0)
Apr 03 20:24:41 russell-server systemd[1]: Reloading.
Apr 03 20:24:41 russell-server systemd[1]: Started CUPS Printing Service.
Apr 03 20:24:41 russell-server systemd[1]: Mounted /storage.
Apr 03 20:24:41 russell-server systemd[1]: Mounted /.
Apr 03 20:24:41 russell-server systemd[1]: Reached target Local File Systems (Pre).
Apr 03 20:24:41 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:41 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:41 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:41 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:41 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:41 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:41 russell-server systemd[1]: Found device WDC_WD20EARX-00PASB0.
Apr 03 20:24:41 russell-server systemd[1]: Starting File System Check on /dev/disk/by-uuid/a628b153-4f97-45f7-b8b1-23c3557cdd72...
Apr 03 20:24:41 russell-server sudo[15178]: pam_unix(sudo:session): session closed for user root
Apr 03 20:24:41 russell-server systemd[1]: Started File System Check on /dev/disk/by-uuid/a628b153-4f97-45f7-b8b1-23c3557cdd72.
Apr 03 20:24:50 russell-server sudo[15213]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/systemctl start plexmediaserver.service
Apr 03 20:24:50 russell-server sudo[15213]: pam_unix(sudo:session): session opened for user root by admin(uid=0)
Apr 03 20:24:50 russell-server systemd[1]: Starting Plex Media Server for Linux...
Apr 03 20:24:51 russell-server su[15221]: (to plexmediaserver) root on none
I have no idea that its doing, its not after or before a reboot, any ideas?
Last edited by jrussell (2013-04-03 21:33:15)

@WonderWoofy,
I know smartmon tools works but when I've used them on an SSD I've got bizarre results which I suspect would imply the disk died a few decades ago if they were accurate. I'm not sure if the tools are reliable for SSDs though I suspect it depends on the particular model.
@OP,
You'd need to look at the detailed report for the disk. That it passed does not mean much. I've had a hard drive pass despite clearly being in the last death throes. The more detailed report clearly showed something was very, very wrong but the overall health check still reckoned the disk was just fine. I would therefore never trust the overall passed report and only ever look at the detailed report.
You can also have smartmon tools run tests on the disk if you do not do this as a routine. The detailed report will show what is available for your particular disk.
Just for clarity: is WDC_WD20EARX-00PASB0 a628b153-4f97-45f7-b8b1-23c3557cdd72? And is a628b153-4f97-45f7-b8b1-23c3557cdd72 sdb?

Similar Messages

Strange empty NAT entry

Hi All,
What's causing some work stations to create this strange NAT entry with no protocol defined and no Outside local and Outside global.
core2#sh ip nat trans | inc 172.16.75.139
Pro Inside global Inside local Outside local Outside global
--- 210.15.240.9 172.16.75.139 --- ---
tcp 210.15.240.9:5380 172.16.75.139:5380 61.137.191.125:80 61.137.191.125:80
Any ideas?
Thanks.
Andy

Hi Roman,
Thanks for the reply.
There is no static nat configured which is why I'm puzzled by that entry.
core2#sh run | inc nat
nat server
nat server
nat server
nat server
nat server
ip nat outside
ip nat inside
ip nat inside
ip nat outside
ip nat inside
ip nat translation timeout 300
ip nat pool NAT-POOL 210.15.240.6 210.15.240.9 netmask 255.255.255.224
ip nat inside source route-map nonat pool NAT-POOL overload
route-map nonat permit 10
That's the whole config and you can see that there is no static nat configured anywhere.
I have a few dhcp clients doing this on the network.
Look for example at the dhcp clients of 172.16.75.23 and 172.16.75.239.
core2#sh ip nat trans
Pro Inside global Inside local Outside local Outside global
tcp 210.15.240.9:1024 172.16.75.239:49796 210.15.254.237:443 210.15.254.237:443
--- 210.15.240.8 172.16.75.23 --- ---
--- 210.15.240.9 172.16.75.239 --- ---
tcp 210.15.240.6:1024 172.16.75.26:49240 207.46.61.90:80 207.46.61.90:80
tcp 210.15.240.6:1025 172.16.75.243:50811 202.45.127.78:993 202.45.127.78:993
tcp 210.15.240.6:1032 172.16.75.232:51226 66.102.11.164:80 66.102.11.164:80
tcp 210.15.240.6:1026 172.16.75.232:51526 72.167.82.19:993 72.167.82.19:993
tcp 210.15.240.6:1027 172.16.75.241:49982 209.85.129.111:993 209.85.129.111:993
tcp 210.15.240.8:54775 172.16.75.23:54775 89.149.236.104:80 89.149.236.104:80
Thanks.
Andy

Strange Calendar Event Entry

Some days ago I found a birthday greeting in my calendar as title of a "whole day" event. Obviously, if this isn't automatically done by the system, someone from outside must have created it. Because there is no birthday field in my contacts I doubt that my system has knowledge of my birthday for an automated message. Therefore, someone else seems to be the sender.
In the detail screen of the event the title text is also shown in the note field. Furthermore "Contacts" is shown as participant. When I try to delete the event the system refuses to do so with a message that Birthday events of my contacts can only be deleted by the calendar administrator. This is strange because I'm able to delete all other calender events and it's my private system with no other administrator than myself.
Does someone know what can be the source of that event i.e. how someone from outside my system can create an event entry in my calender?

Am I the only one? Help.

Strange system.log entries. Have I been compromised? Related to ARD

Every two minutes my system.log posts a new entry that I am having a UDP WritePacket error 65 and it looks as if its trying to connect to a range of IP's that are hosted by pacbell. I do not have any systems outside my network on my ARD so not sure what the heck is going on. Here is a copy of the messages:
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.33
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.64
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.95
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.174
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.27
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.161
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.98
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.126
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.61
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.130
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.67
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.51
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.92
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.74
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.57
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.179
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.45
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.90
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.14
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.48
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.88
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.229
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.69
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.37
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.54
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.84
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.23
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.79
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.173
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.149
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.80
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.53
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.21
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.86
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.111
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.168
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.44
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.40
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.124
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.29
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.166
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.133
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.56
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.33
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.64
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.95
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.174
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.27
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.161
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.98
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.126
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.61
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.130
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.67
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.51
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.92
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.74
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.57
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.179
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.45
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.90
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.14
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.48
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.88
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.229
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.69
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.37
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.54
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.84
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.23
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.79
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.173
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.149
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.80
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.53
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.21
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.86
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.111
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.168
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.44
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.40
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.124
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.29
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.166
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.133
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.56

There is another post about this about a couple of months ago. The poster figured out that the first number -64 actually could be translated into 192. etc.
and that the computers were not online at the time (laptops etc).
Here is the link..
http://discussions.apple.com/thread.jspa?messageID=2608312&#2608312

Strange HDD problem in Windows 7

Have a A660 laptop for 10 months. HDD died, no boot, no recovery, nothing, and no restore discs. Sent in to Toshiba for warrantee repair. They sent it back with new HDD. We started it up, and ran as a new install, like a new laptop. Everything loaded properly, or so it looked like.
When checking the new HDD, instead of showing 500GB, windows said drive "C" was only 136GB total. Went to computer management, storage section. It said on the top part, that HDD "0" partition "C" was 136 GB total. Below that, there are 3 blocks that show all 3 partitions. The 2 small ones were correct. The large one showed 450GB in size, and all of it was allocated to the C drive. If you checked the C drive, it said it was 136GB. I am pretty well versed in Windows 7, but have never seen this before. We went to re-boot, and all we got was the bios screen, and then a flashing cursor in the upper left corner. Tried to reset everything, using "0" on startup, but there was no screen asking us if we wanted to erase everything. Weiredest thing I have ever seen Windows do. I looked all over, but could not find anything in any forums or boards about this. I am sending the unit back. Am waiting for a new warrantee return box with the FedEx slip.

Did you install Win 7, and that's all? If so, you're missing a lot of drivers in Windows so it will recognize the Mac hardware.
Boot to Win 7. Put the OS X installation disk in the drive. It will automatically install basic drivers for Windows. It will tell you when it's finished, and to restart. After that, you'll find an Apple Software Update icon in the Windows start menu. Run that to install updated Boot Camp drivers and other updates from Apple.

Strange apache2 error_log entry

Every few seconds an entry "/var/empty/server-status" appears in the apache2 error_log (Mac OS X Server 10.6.7). What is the meaning of this? Also, I do not know what instance is writing to this log since each website writes to its own error log. Is it apache2 itself?

I solved my problem by creating a (empty) folder in /var/empty/ named "server-status". The error log no longer gets populated with the error entries. However, I ask myself, isn't this solution equally empty-headed?

Strange HDD error, couldn't repair.

Hi!
Yesterday turned off my Macbook normally, when today tried to start it, it started very long time - desktop and dash came up quickly as usual, but clock, airport indicator, bluetooth, battery etc didn't came up and i needed to wait about 20 minutes, and all this time i couldn't do anything.
After i started Disk Utility and checked my volume - it needed to be repaired.
But when i tried to do this, an error occured:
"Error: The underlying task reported failure on exit"
(screenshot is here http://bestpics.ru/full/Picture-1.png )
I tried to start my macbook in a target drive mode, then connected it to another Mac using FireWire, but the same error occurs while trying to repair a disk.
S.M.A.R.T.status for the HDD is OK.
I also tried to use fsck command (ater taking root's privileges, of course) but nothing doing
Please, can anyone suggest, what should I do now?

Guys! Found a solution - just booted in a single-user-mode, then fsck with -fy option. That's all!

Strange HDD behavior, activity all the time?

Hi,
I just reinstalled arch on my tp x23 on a new seagate momentus hard drive. The installation went fine and I must say I'm very pleased with the performance so far.. except for the fact that the hard drive is almost constantly doing something and I have no idea what it is? The activity led turns off only to turn back on in a while.
Any ideas?
Sakari

Zer0 wrote:
Hmm now that you mention power saving features.. I wonder if it's the hard drive going in "sleep mode" when theres little/no activity and the HDD LED lights up during spin down and spin up.. Maybe check the BIOS and disable the hard drive powerdown crap or change the timeframe.. if it works then you know where the problem lies..
then again you are on a laptop so I'm not sure the solution outweighs the LED problem (as spinning down the hard drive will help prolong your battery life)
It sure seems to be something like that. I also fount this thread which is (was) discussing the issue, but didn't really find a solution. Anyway, I know now what the probable cause is and if I want to change the behavior one day, I know how to do it. So a lesson learned, great!
About the battery, I actually don't even have one at the moment, so I'm always AC-powered. But I think I'll get back to this one once I get a new battery and have a chance to test different settings. What I don't understand is that my system seems to run cooler now the power saving is turned off or at least as cool without the fan blowing all of my papers off the table Maybe it's a bug in the hd's firmware, don't know? It seems like the heads won't park properly and keep on going on and off.. That would explain the constantly lit activity led.

Strange HDD issue.

I decided to upgrade my HDD on my PB when I purchased 10.5 and have had a lot of trouble with it since. I previously had a stock Hitachi 80GB drive and wanted to increase storage to simplify software djing.
The first new drive I tried was a Western Digital 250GB drive (http://westerndigital.com/en/products/products.asp?driveid=346). It immediately had a problem where it clunked audibly every 1-3 minutes when the drive idled, but was functional. It formatted, installed and ran fine except for this bizarre clunking. I returned it, because clunking sounds usually indicate imminent failure.
Second I installed another drive of the same type, also brand new, and had exactly the same problem. Operationally perfect except that it clunked every 1-3 minutes while the drive was idle. I also returned this drive.
Third I installed a new Seagate 160GB drive (http://www.seagate.com/ww/v/index.jsp?vgnextoid=b26addfc7816e010VgnVCM100000dd04 090aRCRD&locale=en-US) which has been also operationally perfect except that when idle every 1-3 minutes it makes a sound like the head is resetting.
All 3 of these drives passed Apple Hardware Test that came with the Powerbook and passed Disk Utility checks. The problem persists after zapping the PRAM (which i did immediately after the disk was installed) and after resetting the PMU. It also persists when the Powerbook is allowed to idle and go to sleep or closing the lid, but stops if you actually go into the apple menu and choose sleep. Unchecking "Put the hard disk(s) to sleep when possible" in the power settings has no effect.
It seems like it's possible that 10.5 just has a problem with this PowerBook, like something may be wrong with power management in general. I notice also that whenever i go to shutdown umount fails before powering down.
I'm stumped and frustrated, my question is where do I go from here to fix this issue: Is there another type of hardware test that may help? Have I damaged the hdd cable? Does this drive require more power than the mainboard provides? Did I just get 3 dud drives? Is this sound normal or is this a known issue with Leopard on PPC? Is a firmware update required?

First of all, sleep mode should generally spin down the hard drive, no matter whether it is entered automatically after a certain idle time, by closing the lid or explicitly through the menu.
The 'clunking' sounds may be normal behaviour. Many modern hard drives have advanced power management with several steps of power saving in idle mode, including one which audibly unloads the read/write heads. In conjunction with some system task or application which periodically accesses the drive this may cause regular annoying clicks or clunks.
It may be possible to fix the problem by configuring or disabling the hard drive's APM with [hdapm|http://mckinlay.net.nz/hdapm>.

No entries in journal for ufw

Hi, is there something that need to be done to enable logging in ufw? I have enabled the fw, and put logging in ufw to a high level.
Trouble is that I get no entires when I do a journalctl -f as priviledge user. However, when I do a dmesg, I see all the entries?
I'm a bit new to systemd, but is it somehow possible to redirect the log to either journalctl or perhaps even to a separate file?
ty

Sorry for the delayed response...
Are you sure didn't change any logging rules in /etc/systemd/journalctl.conf or enable syslog integration or something odd? I don't even have increased logging levels for ufw.
$ sudo systemctl is-enabled ufw.service
enabled
$ sudo systemctl is-active ufw.service
active
$ sudo ufw status verbose
Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing)
New profiles: skip
To Action From
<rules edited out>
$ dmesg|grep -i ufw|wc -l
108
$ sudo journalctl -b --no-page|grep -i ufw|wc -l
105
Scott

Strange HDD behavior only on Arch

Just Arch (no Gentoo, no Ubuntu nor Windows) make HDD do a sound, even with
$ sudo hdparm -B /dev/sda
/dev/sda:
APM_level = off
$ sudo smartctl -A /dev/sda |grep Load_Cycle
193 Load_Cycle_Count 0x0032 094 094 000 Old_age Always - 67469
// and growing..
I don't understand this...
System freezes while making "HDD head moving and spin up sound". I have laptop-mode-tools off
If you need any command or log to help me, I'll paste on pastebin.
Thanks
Last edited by kismet010 (2010-11-26 06:56:30)

but why only on Arch? Ubuntu let me set APM off and just work, I stop hearing this.
$ hdparm -M 0
HDIO_DRIVE_CMD:ACOUSTIC failed: Input/output error
/dev/sda:
setting acoustic management to 0
acoustic = not supported
$ smartctl -i /dev/sda
=== START OF INFORMATION SECTION ===
Device Model: TOSHIBA MK3265GSX
Serial Number: 10M3S343S
Firmware Version: GJ002H
User Capacity: 320,072,933,376 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Nov 26 07:45:56 2010 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
I'm looking for a tool but I don't see anything.
I know that could destroy my data, I promise to do a backup in case there is a small earthquake but at this rate for parking every 5 seconds, are about 2000 cycles per day, then I have less than 300 days... so I prefer do backups.
And thanks for the correction, I'm not English
Last edited by kismet010 (2010-11-26 07:55:24)

Strange hdd capacity on 865PE Neo3

my friend just purchased msi neo3 865PE for his p4 660 LGA775. Everything run ok, but the system just can detect 130gb of his hdd (it is seagate 200gb). How to fix this? Everything is ok when using 865PE neo2.

What size is detected in the bios?

Strange FTP log entry - FTP LOGIN REFUSED: getpwnam returned null

At the systems log file, I get entries like the following since a few days:
FTP LOGIN REFUSED: getpwnam returned null
Over and over again (three or four per second). System performance is not harmed, anything working in normal parameters.
There are several xftpd processes there causing this behavior - stopping ftp, killing them, restarting ftp solves the problem - and after one day, same situation.
I searched this forum, but haven't found much information. Others seemed to have the problem as well, but either got no reply or have decided to use a different ftp server instead of Apple's one (which is no choice for us).
Any advise would be appreciated.

Others seemed to have the problem as well, but either got no reply or have decided to use a different ftp server instead of Apple's one
Using a different server won't make any difference.
Your machine is being attacked by a hacker trying to get into your FTP server.
Don't be surprised by this. Just about any service that is open to the public internet is going to get probed at some point. All that's happened here is that some bot has detected a FTP server running on your machine and is trying a number of username/password combinations to see if they can log in.
Whether they will or not depends on the number of accounts you have on your server and the strength of their passwords.
Having a different FTP server isn't going to make a difference because the bot doesn't (yet) know what server you're running, it's just opening FTP connections and trying to log in. Any FTP server would respond in the same way.
The solution is to decide whether you really need FTP exposed to the outside world. It really isn't a secure protocol and can be the vector through which other hacks occur. If you don't need it I'd turn it off. If you do need it, consider some way of limiting access (e.g. make it available to LAN clients only and not to the whole internet, or use a VPN.

Strange System Log Entry

The following sequence keeps repeating every few seconds in the System Log. Does anyone have any ideas as to what it is all about? It appears to be referring to a Python script, but we have not "knowingly" executed any.
Dec 13 13:15:06 host1 com.apple.wikid[28950]: Traceback (most recent call last):
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/bin/twistd", line 21, in <module>
Dec 13 13:15:06 host1 com.apple.wikid[28950]: run()
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/scripts/twistd.py", line 27, in run
Dec 13 13:15:06 host1 com.apple.wikid[28950]: app.run(runApp, ServerOptions)
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/application/app.py", line 379, in run
Dec 13 13:15:06 host1 com.apple.wikid[28950]: runApp(config)
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/scripts/twistd.py", line 23, in runApp
Dec 13 13:15:06 host1 com.apple.wikid[28950]: _SomeApplicationRunner(config).run()
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/application/app.py", line 156, in run
Dec 13 13:15:06 host1 com.apple.wikid[28950]: self.preApplication()
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/scripts/twistdunix.py", line 203, in preApplication
Dec 13 13:15:06 host1 com.apple.wikid[28950]: self.config['prefix'], self.config['nodaemon'])
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/scripts/twistdunix.py", line 113, in startLogging
Dec 13 13:15:06 host1 com.apple.wikid[28950]: logFile = app.getLogFile(logfilename or 'twistd.log')
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/application/app.py", line 410, in getLogFile
Dec 13 13:15:06 host1 com.apple.wikid[28950]: os.path.dirname(logPath))
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/python/logfile.py", line 113, in _init_
Dec 13 13:15:06 host1 com.apple.wikid[28950]: BaseLogFile._init_(self, name, directory, defaultMode)
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/python/logfile.py", line 26, in _init_
Dec 13 13:15:06 host1 com.apple.wikid[28950]: assert os.path.isdir(self.directory)
Dec 13 13:15:06 host1 com.apple.wikid[28950]: AssertionError
Dec 13 13:15:06 host1 com.apple.launchd[1] (com.apple.wikid[28950]): Exited with exit code: 1
Dec 13 13:15:06 host1 com.apple.launchd[1] (com.apple.wikid): Throttling respawn: Will start in 8 seconds

Okay - I also noticed this same issue as propably many others - did little study and found out the reason.
First of all - these should be standard locations, but let's make sure. I found out that wikid keeps it settings in /etc/wikid/wikid.conf - From error messages I checked source of last mention before process ended. Not pasting anything to here, I usually use PHP or C and try to stay away from python but I was able to make something out. Assert is a function that makes a test agains something, if this test's result is true (if I remember my studies right, I rarely use assert) it exits process. Why? Sometimes when programs start they need to make certain checks to avoid crashing - crashing isn't nice..
Anyway, test was for existency of directory where logfile(s) are kept. From same or another source file I also found out about location /etc/wikid, I ofcourse could had checked it from there in the first place, but I liked to follow the code a bit.. There I found file wikid.plist, opened it - a long conf file and finally there it was - logfile(s) are kept in location:
/Library/Logs/wikid
I created this directory and restarted, everything wasn't okay yet, as rights for that directory were incorrect. So I checked com.apple.wikid in LaunchDaemons and found out it runs as user _teamsserver and gid _teamsserver. So I changed rights for that uid and gid and everything was working after that.
Here's what you need to do in terminal to get it working:
#sudo mkdir /Library/Logs/wikid
#sudo chown -R teamsserver:teamsserver /Library/Logs/wikid
Then just restart wikid, there you go. This was my first post and I just created account for this.
Can be marked as SOLVED but 10.5.2 should make sure this directory gets created - either when ever it's missing and wikid is started, or just a empty dir created while upgrading to 10.5.2

Strange Repair Permission Entry

My friend has just purchased a new iMac and is running Snow Leopard.
She could not get an ftp program to run (Cyberduck) so I thought I would try a permission repair.
I got the following message .... any ideas how I fix this?
http://i35.tinypic.com/339rncw.png
I was sharing her screen using iChat at the time, would that be the problem?

Jaymz wrote:
Thank you.
I can't believe you answered exactly the same question from two different posts 6 minutes apart!
yes. i just had to copy and paste .

Strange hdd remounting entries in journal

Similar Messages

Maybe you are looking for