Osx 10.6.8 inability to upgrade to OSX 10.8.1

2 of my Mac Pros are unable to upgrade to osx 10.8.1 from 10.6.8. There is absolutely no technical reason give, just a popup indicating they are not eligible for the upgrade. I found some information listed here : http://support.apple.com/kb/ht1159#mac_pro but I am unable to verify if this is the reason as we do not have records of purchase dates for the systems in question. I have upgraded similiar model MBP's, though again without our purchase records I cannot say if they were bought at a different time and if that is the reason some of our MBP's took the update without issue.

You sound like you have a Mac Pro you would have had to know the type of memory, eligible graphics cards, and... come to learn about pre-2008 3,1's having 32-bit EFI instead of 2008 and later having 64-bit EFI (UEFI) firmware... which is the technical reason. That it cannot use 64-bit graphic drivers and kernel mode, and the PCIe 1.1 bus.
http://www.apple.com/support/macpro
http://www.apple.com/osx/how-to-upgrade/
Supported
Models
iMac (Mid 2007 or newer)
MacBook (Late 2008 Aluminum, or Early 2009 or newer)
MacBook Pro (Mid/Late 2007 or newer)
Xserve (Early 2009)
MacBook Air (Late 2008 or newer)
Mac mini (Early 2009 or newer)
Mac Pro (Early 2008 or newer)
This is about Mac Pro, and not about MacBook Pro you realize, which is what this forum is and not about laptops.
MacBook Series Forums
https://discussions.apple.com/community/notebooks?view=discussions
http://www.apple.com/support/macbookpro

Similar Messages

Working browsers for 10.4.11? and / or OS upgrade help?

I stopped being able to update Firefox probably around 2 years ago on my computer, and can't download Google Chrome, all because I am running 10.4.11. I don't need to do so much on my computer...I browse the web, talk to people on skype, listen to music, watch movies, and type things up. So, my computer still is able to do everything I want it to with a good amount of speed, and only has a few periodic "old computer" symptoms. However, the inability to upgrade my browser is becoming a big problem. Gmail and facebook both inform me every time I log in that my browser is old and soon won't be supported anymore. Everything was working okay, but the last two emails I've tried to send out of firefox have not sent. I was able to send them by switching to Safari...but as the same message comes up there, I think it may be a temporary solution. Has anyone else dealt with this problem and found a working browser?
If I really can't get an updated version of any web browser, does anyone know how high I can upgrade my computer's os? I have a macbook 2 GHz Intel Core 2 Duo with 1 GB 667 MHz DDR2 SDRAM. I know I might just have to bite the bullet and get a new computer...but I'm curious to know if I could stretch a little more life out of this one since it is otherwise running pretty well, and I don't need the newest, shiniest stuff.

You need some more RAM, but:
Start by checking if you can run Snow Leopard:
Requirements for OS X 10.6 'Snow Leopard'
http://support.apple.com/kb/SP575
OS 10.6 Snow Leopard is once again available from the Apple Store:
http://store.apple.com/us/product/MC573/mac-os-x-106-snow-leopard
and in the UK:
http://store.apple.com/uk/product/MC573/mac-os-x-106-snow-leopard
but nobody knows for how long it will be available.
To use iCloud you have to upgrade all the way to Mountain Lion:
http://support.apple.com/kb/HT4759
You can also purchase the code to use to download Lion (Lion requires an Intel-based Mac with a Core 2 Duo, i3, i5, i7 or Xeon processor and 2GB of RAM, running the latest version of Snow Leopard), or you can purchase Mountain Lion from the App Store - if you can run that:
http://www.apple.com/osx/specs/
When you have installed it, run Software Update to download and install the latest updates for Snow Leopard.

How much sales does Apple lose by not allowing upgrade of hardware?

I wonder if Apple has ever conducted market research to find out how much sales they lose because of the inability to upgrade components with a mac?
I suspect they haven't done so because they don't wish to find out the answer!
I imagine they have simply assumed that they don't want to affect the bottom line sales of new macs by allowing users to upgarde their older machines.
I believe this is a shortsighted view. If for instance users could upgrade components inside the tower, by being allowed to say buy the motherboard on its own. There would be significant numbers of people who would buy the tower (who now don't) that would offset the reduction in sales of new complete systems in the future.
Wouldn't it be fun to find out?
Instead of having to spend $3000 to upgrade to the latest and greatest by buying a complete system Apple could offer the motherboard to repace the older one thus saving the consumer a lot of money! Is this not what serving the customer is really about? and part of the reason why they only have 5% market share?

Since you asked, and I seem to be in a particularily foul mood today, I'll take some of that action.
I quit the upgrade dance three years ago when I found out I could have a great little Unix workstation that sat on my lap. No longer am I forced to worry what hardware will work with Solaris, or Linux, or FreeBSD. I plunk down my money, and it works. Works so well that all of the machines I've purchased (one per year) are just as relevant as they day I purchased them. Yeah, they don't work so fast as the newest, but so what?
Dell, HP, Gateway; they do not allow you to purchase motherboards in which to upgrade your computer. Not notebooks (never, ever in fact), and only desktops because their crummy form-factor is pretty much the same as everyone else. But that's been changing too.
If you have a question about the Macbook Pro, please ask it. Otherwise, thanks for the opportunity to vent on you. It's been a rather sad day for me and I appreciate the chance to take it out on you.

Upgrade a mid 2010 Mac Mini or buy a new one?

I have a mid 2010 Mac Mini with a 2.4 GHz Intel Core 2 Duo processor, 2 GB SDRAM DDR3, and a 320 GB HDD. I use it primarily as a way to watch movies, TV, and internet videos on my TV. However, lately it has become excruciatingly slow with choppy video playback. I realize upgrading the RAM and/or the HDD to a SSD would offer an improvement. But my question is, would it be better to upgrade a computer that's getting close to 5 years old now, or buy a new Mac Mini, despite the complaints I've heard about the inability to upgrade RAM and/or hard drive.
Thanks

For your use going to the max of 8 GB of memory and an SSD will be fine.

Installation cannot directly upgrade version of iPod Software... Uninstall.

I cannot get iTunes installed! I get an error every time I try... Please uninstall iPod Software but I can't because it's not under program files yet it is still under Add/Remove Programs. When I click uninstall in Add/Remove something quickly pops up that looks like an uninstallation but nothing happens the ipod software is not unsinstalled even if it is there... help?
Windows XP
Windows XP

I have experienced the same problem and am frustrated in not having found a fix yet. I've sent a message to iTunes since the inability to upgrade the iPod software affects my ability to play purchased music on my iPod. In other words, I can't do it now. if I hear back from iTunes on how to fix it, I'll let you know. Can you please do them same if you get an answer?
Thanks

PowerMac G4 Hanging on Shutdown, now won't accept 10.2.4 patch

I have a dual 1.ghz G4 silver door PowerMac. I've been running OS X 10.2.8. Suddenly, my system quit shutting down properly. It would start the shutdown, then hang up at the stage where the screen had the blue desktop background and the clock looking icon was "spinning". The only way to get the system to go past this point was to press and hold the start button.
I tried the disk utitlity and Disk Warrior, but none of those fixes changed the shutdown behavior. So, I reinstalled the OS X 10.2 operating system, using the "archive and replace" option. Then I began patching the 10.2.0 OS to bring it back to 10.2.8. The "combo" 10.2.8 patch wouldn't run. It would start prepping, then abort with the cryptic message that there was an error, please try again.
After a couple of tries, I gave up and started applying the patches one at a time. I got as far as trying to apply the 10.2.4 patch. For that patch, the installer tells me it cannot apply the patch to my system because it doesn't meet the requirements for this patch.
I can't tell whether the shutdown problem I had earlier is related to the inability to upgrade my OS to the most recent patch, but I am wondering whether there might be some hardware issue at the bottom of this series of events.
Any help, hints or clues would be appreciated.
Nikki
PowerMac G4 Dual 1 GHz Mac OS X (10.2.x)

Hi, biosmell -
I am considering pulling the internal battery in hopes it will kill the boot memory and perhaps default back to the OSX disks again.
That should work to reset PRAM, which contains the boot volume selection. Be sure to also pull the power cord, and to wait long enough; about a half hour should be fine.
After replacing the battery and reconnecting the power cord, wait another couple of minutes and then boot it - by default it should boot to the first OS it finds on a local (i.e., internal) hard drive.

Parallels on 11.6 Air

Hi there,
I'm just about to take the plunge on a new Air, but have a dilemma. I don't know whether to go for 2gb or 4gb of RAM. Obviously, if possible, i'd like to save some money, but not at the detriment of performance. My main concern is regarding Parallels. I will definitely want to run Windows 7 via Parallels on it. I would constantly be switching between Parallels running and OSX for various things so performance in both OS's simultaneously would have to be pretty good. In my old Macbook with 2gb RAM, it really struggled at this whereas my current Macbook with 4gb RAM works like a dream with little to no lag. The current Macbook is going to help fund the Air so it is imperative that it runs Parallels to a decent level.
Anyone out there with the 11.6, 1.4ghz, 2gb RAM model currently using Parallels? If so, i'd be extremely grateful for your opinion on how it runs.
Many thanks in advance

I really couldn't say, if you can I'd recommend dropping by an Apple Store many have Parallels already installed so you can get a pretty good idea. Then you can see for yourself if a 2GB configuration provides adequate performance for your needs. My point is very simple, the cost difference isn't great however the ramifications are potentially dramatic because of the inability to upgrade RAM.

Can't Export to iTunes

After finishing a GarageBand file, my iMac G5 won't export into iTunes. It's gets to the end of the slidebar and then just sits there. Nothing.
Also, I have been unable to install any iTunes upgrades since the horrible 7.0 or 7.01 version. The installer opens and it won't go past the "preparing" window. I get the following in the Installer Log window:
Package Authoring Warning: The installer script defines but doesn't use (and can't install) package id manual version 8.0.2.2230000.1687.
I've tried removing the prefs files from both GarageBand and iTunes and I still have the export problem and the inability to upgrade iTunes.
Any solution besides a clean install (which I had just done a month prior to the problems beginning)?
Thanks!
--Ted

Try repairing your permissions, then restart your computer.

Continued SSD Corruption

I have a Shuttlebox XS35V2 with Corsair SSD (V4-CT032V4SSD2) and Archlinux. I seem to be getting continued (although intermittent) disk corruption issues which only become apparent after a reboot. I have the system always running (as it's acting as a traffic monitoring gateway between 2 LAN's) so when I do reboot it, it's usually been running perfectly well for weeks, if not months, on end. Last time led to this issue: https://bbs.archlinux.org/viewtopic.php?id=159351, and this time has led to a number of issues, including MYSQL corruption another inability to upgrade/update packages.
The corruption typically stops the system booting (often refering to a corrupt journal before giving me a cut-down/limited shell), but booting with a LiveUSB & running fsck with automated options to clear the corruptions, has so far allowed me to at least reboot the full Archlinux system again (albeit with the corruptions mentioned above).
Latest update attempt following corruption:
[root@shuttlebox ~]# pacman -Syu
:: Synchronising package databases...
core 104.8 KiB 633K/s 00:00 [#######################################################################################] 100%
extra 1426.1 KiB 784K/s 00:02 [#######################################################################################] 100%
community 1950.1 KiB 795K/s 00:02 [#######################################################################################] 100%
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n]
resolving dependencies...
looking for inter-conflicts...
error: could not open file /var/lib/pacman/local/psmisc-22.19-1/desc: No such file or directory
Targets (1): pacman-4.1.1-1
Total Download Size: 0.61 MiB
Total Installed Size: 3.97 MiB
Net Upgrade Size: 0.43 MiB
Proceed with installation? [Y/n]
:: Retrieving packages from core...
pacman-4.1.1-1-x86_64 622.9 KiB 764K/s 00:01 [#######################################################################################] 100%
(1/1) checking package integrity [#######################################################################################] 100%
(1/1) loading package files [#######################################################################################] 100%
(1/1) checking for file conflicts [#######################################################################################] 100%
(1/1) checking available disk space [#######################################################################################] 100%
(1/1) upgrading pacman [#######################################################################################] 100%
[root@shuttlebox ~]# pacman -Syu
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
error: could not open file /var/lib/pacman/local/psmisc-22.19-1/desc: No such file or directory
resolving dependencies...
warning: dependency cycle detected:
warning: libsasl will be installed before its krb5 dependency
looking for inter-conflicts...
Packages (74): alsa-lib-1.0.27-2 archlinux-keyring-20130406-1 bash-4.2.045-1 ca-certificates-20130119-2 cifs-utils-6.0-2 cracklib-2.8.22-2 cryptsetup-1.6.1-1 curl-7.30.0-1 dbus-1.6.10-1 dhcpcd-5.6.8-1 diffutils-3.3-1
dirmngr-1.1.1-1 dnsmasq-2.66-1 dnssec-anchors-20130320-1 dnsutils-9.9.2.P2-1 expat-2.1.0-2 file-5.14-1 filesystem-2013.03-2 freetype2-2.4.12-1 gcc-libs-4.8.0-4 gettext-0.18.2.1-1 glib2-2.36.2-1 glibc-2.17-5
gnupg-2.0.20-2 gpgme-1.4.1-1 groff-1.22.2-3 hwids-20130512-1 inetutils-1.9.1-5 iproute2-3.9.0-1 iptables-1.4.18-1 iputils-20121221-2 keyutils-1.5.5-4 kmod-13-1 krb5-1.11.2-3 less-458-1 libassuan-2.1.0-1
libbsd-0.4.2-1 libcap-2.22-5 libffi-3.0.13-1 libgcrypt-1.5.2-1 libksba-1.3.0-1 libldap-2.4.35-3 libltdl-2.4.2-8 libpcap-1.4.0-1 libpipeline-1.2.3-1 libpng-1.6.2-3 libsasl-2.1.26-2 libtirpc-0.2.3-1
libusbx-1.0.15-1 libwbclient-4.0.5-3 linux-3.9.2-1 linux-api-headers-3.8.4-1 linux-firmware-20130430-1 logrotate-3.8.4-2 man-pages-3.51-1 mkinitcpio-0.14.0-1 ncurses-5.9-5 ntp-4.2.6.p5-14 openssh-6.2p1-1
pacman-mirrorlist-20130323-1 pam-1.1.6-3 pciutils-3.2.0-2 pcmciautils-018-7 perl-5.16.3-3 pinentry-0.8.3-1 procps-ng-3.3.7-1 psmisc-22.20-1 shadow-4.1.5.1-5 sox-14.4.1-2 systemd-204-1 tcpdump-4.4.0-1
tzdata-2013c-1 util-linux-2.23-2 zlib-1.2.8-1
Total Download Size: 116.22 MiB
Total Installed Size: 338.05 MiB
Net Upgrade Size: -21.46 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages ...
linux-api-headers-3.8.4-1-x86_64 618.6 KiB 771K/s 00:01 [#######################################################################################] 100%
tzdata-2013c-1-any 251.7 KiB 812K/s 00:00 [#######################################################################################] 100%
filesystem-2013.03-2-x86_64 5.9 KiB 836K/s 00:00 [#######################################################################################] 100%
glibc-2.17-5-x86_64 7.9 MiB 808K/s 00:10 [#######################################################################################] 100%
archlinux-keyring-20130406-1-any 364.4 KiB 716K/s 00:01 [#######################################################################################] 100%
bash-4.2.045-1-x86_64 789.1 KiB 811K/s 00:01 [#######################################################################################] 100%
ca-certificates-20130119-2-any 146.9 KiB 816K/s 00:00 [#######################################################################################] 100%
keyutils-1.5.5-4-x86_64 57.6 KiB 834K/s 00:00 [#######################################################################################] 100%
libsasl-2.1.26-2-x86_64 143.0 KiB 822K/s 00:00 [#######################################################################################] 100%
libldap-2.4.35-3-x86_64 396.2 KiB 815K/s 00:00 [#######################################################################################] 100%
krb5-1.11.2-3-x86_64 1073.0 KiB 810K/s 00:01 [#######################################################################################] 100%
zlib-1.2.8-1-x86_64 80.0 KiB 825K/s 00:00 [#######################################################################################] 100%
cracklib-2.8.22-2-x86_64 244.2 KiB 811K/s 00:00 [#######################################################################################] 100%
libgcrypt-1.5.2-1-x86_64 309.1 KiB 813K/s 00:00 [#######################################################################################] 100%
libtirpc-0.2.3-1-x86_64 176.6 KiB 814K/s 00:00 [#######################################################################################] 100%
pam-1.1.6-3-x86_64 659.9 KiB 810K/s 00:01 [#######################################################################################] 100%
shadow-4.1.5.1-5-x86_64 1021.7 KiB 812K/s 00:01 [#######################################################################################] 100%
util-linux-2.23-2-x86_64 1694.3 KiB 810K/s 00:02 [#######################################################################################] 100%
cryptsetup-1.6.1-1-x86_64 180.2 KiB 819K/s 00:00 [#######################################################################################] 100%
curl-7.30.0-1-x86_64 520.5 KiB 813K/s 00:01 [#######################################################################################] 100%
expat-2.1.0-2-x86_64 103.5 KiB 828K/s 00:00 [#######################################################################################] 100%
dbus-1.6.10-1-x86_64 421.0 KiB 814K/s 00:01 [#######################################################################################] 100%
dhcpcd-5.6.8-1-x86_64 76.7 KiB 825K/s 00:00 [#######################################################################################] 100%
diffutils-3.3-1-x86_64 173.7 KiB 819K/s 00:00 [#######################################################################################] 100%
libksba-1.3.0-1-x86_64 111.3 KiB 813K/s 00:00 [#######################################################################################] 100%
libassuan-2.1.0-1-x86_64 77.8 KiB 828K/s 00:00 [#######################################################################################] 100%
dirmngr-1.1.1-1-x86_64 169.0 KiB 816K/s 00:00 [#######################################################################################] 100%
dnssec-anchors-20130320-1-any 980.0 B 0.00B/s 00:00 [#######################################################################################] 100%
file-5.14-1-x86_64 190.5 KiB 821K/s 00:00 [#######################################################################################] 100%
gcc-libs-4.8.0-4-x86_64 930.1 KiB 800K/s 00:01 [#######################################################################################] 100%
libffi-3.0.13-1-x86_64 27.7 KiB 839K/s 00:00 [#######################################################################################] 100%
glib2-2.36.2-1-x86_64 1987.6 KiB 809K/s 00:02 [#######################################################################################] 100%
gettext-0.18.2.1-1-x86_64 2.1 MiB 810K/s 00:03 [#######################################################################################] 100%
ncurses-5.9-5-x86_64 965.4 KiB 811K/s 00:01 [#######################################################################################] 100%
libcap-2.22-5-x86_64 36.3 KiB 844K/s 00:00 [#######################################################################################] 100%
pinentry-0.8.3-1-x86_64 96.2 KiB 745K/s 00:00 [#######################################################################################] 100%
gnupg-2.0.20-2-x86_64 1514.7 KiB 808K/s 00:02 [#######################################################################################] 100%
gpgme-1.4.1-1-x86_64 202.9 KiB 681K/s 00:00 [#######################################################################################] 100%
perl-5.16.3-3-x86_64 12.7 MiB 809K/s 00:16 [#######################################################################################] 100%
groff-1.22.2-3-x86_64 1915.1 KiB 810K/s 00:02 [#######################################################################################] 100%
hwids-20130512-1-any 287.6 KiB 812K/s 00:00 [#######################################################################################] 100%
inetutils-1.9.1-5-x86_64 247.4 KiB 816K/s 00:00 [#######################################################################################] 100%
iptables-1.4.18-1-x86_64 234.3 KiB 814K/s 00:00 [#######################################################################################] 100%
iproute2-3.9.0-1-x86_64 462.6 KiB 795K/s 00:01 [#######################################################################################] 100%
iputils-20121221-2-x86_64 73.7 KiB 819K/s 00:00 [#######################################################################################] 100%
kmod-13-1-x86_64 95.8 KiB 818K/s 00:00 [#######################################################################################] 100%
less-458-1-x86_64 90.2 KiB 828K/s 00:00 [#######################################################################################] 100%
libltdl-2.4.2-8-x86_64 150.6 KiB 823K/s 00:00 [#######################################################################################] 100%
libusbx-1.0.15-1-x86_64 40.9 KiB 835K/s 00:00 [#######################################################################################] 100%
libpcap-1.4.0-1-x86_64 198.0 KiB 815K/s 00:00 [#######################################################################################] 100%
libpipeline-1.2.3-1-x86_64 34.2 KiB 876K/s 00:00 [#######################################################################################] 100%
linux-firmware-20130430-1-any 17.9 MiB 809K/s 00:23 [#######################################################################################] 100%
systemd-204-1-x86_64 2.2 MiB 809K/s 00:03 [#######################################################################################] 100%
mkinitcpio-0.14.0-1-any 33.8 KiB 844K/s 00:00 [#######################################################################################] 100%
linux-3.9.2-1-x86_64 45.5 MiB 808K/s 00:58 [#######################################################################################] 100%
logrotate-3.8.4-2-x86_64 30.6 KiB 875K/s 00:00 [#######################################################################################] 100%
man-pages-3.51-1-any 4.7 MiB 808K/s 00:06 [#######################################################################################] 100%
openssh-6.2p1-1-x86_64 564.5 KiB 813K/s 00:01 [#######################################################################################] 100%
pacman-mirrorlist-20130323-1-any 2.3 KiB 2.29M/s 00:00 [#######################################################################################] 100%
pciutils-3.2.0-2-x86_64 82.8 KiB 505K/s 00:00 [#######################################################################################] 100%
pcmciautils-018-7-x86_64 19.7 KiB 895K/s 00:00 [#######################################################################################] 100%
procps-ng-3.3.7-1-x86_64 232.2 KiB 812K/s 00:00 [#######################################################################################] 100%
psmisc-22.20-1-x86_64 90.3 KiB 821K/s 00:00 [#######################################################################################] 100%
alsa-lib-1.0.27-2-x86_64 399.9 KiB 813K/s 00:00 [#######################################################################################] 100%
libbsd-0.4.2-1-x86_64 105.3 KiB 829K/s 00:00 [#######################################################################################] 100%
libwbclient-4.0.5-3-x86_64 28.7 KiB 870K/s 00:00 [#######################################################################################] 100%
cifs-utils-6.0-2-x86_64 67.4 KiB 832K/s 00:00 [#######################################################################################] 100%
dnsmasq-2.66-1-x86_64 156.6 KiB 820K/s 00:00 [#######################################################################################] 100%
dnsutils-9.9.2.P2-1-x86_64 378.9 KiB 813K/s 00:00 [#######################################################################################] 100%
freetype2-2.4.12-1-x86_64 515.0 KiB 812K/s 00:01 [#######################################################################################] 100%
libpng-1.6.2-3-x86_64 254.6 KiB 679K/s 00:00 [#######################################################################################] 100%
ntp-4.2.6.p5-14-x86_64 464.2 KiB 814K/s 00:01 [#######################################################################################] 100%
sox-14.4.1-2-x86_64 512.6 KiB 812K/s 00:01 [#######################################################################################] 100%
tcpdump-4.4.0-1-x86_64 290.2 KiB 820K/s 00:00 [#######################################################################################] 100%
(74/74) checking keys in keyring [#######################################################################################] 100%
(74/74) checking package integrity [#######################################################################################] 100%
(74/74) loading package files [#######################################################################################] 100%
(74/74) checking for file conflicts [#######################################################################################] 100%
error: failed to commit transaction (conflicting files)
psmisc: /usr/bin/fuser exists in filesystem
psmisc: /usr/bin/killall exists in filesystem
psmisc: /usr/bin/peekfd exists in filesystem
psmisc: /usr/bin/prtstat exists in filesystem
psmisc: /usr/bin/pstree exists in filesystem
psmisc: /usr/bin/pstree.x11 exists in filesystem
psmisc: /usr/share/locale/bg/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/ca/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/cs/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/da/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/de/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/el/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/eo/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/eu/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/fi/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/fr/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/hu/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/id/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/it/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/ja/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/nb/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/nl/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/pl/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/pt/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/pt_BR/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/ro/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/ru/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/sr/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/sv/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/uk/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/vi/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/zh_CN/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/locale/zh_TW/LC_MESSAGES/psmisc.mo exists in filesystem
psmisc: /usr/share/man/man1/fuser.1.gz exists in filesystem
psmisc: /usr/share/man/man1/killall.1.gz exists in filesystem
psmisc: /usr/share/man/man1/peekfd.1.gz exists in filesystem
psmisc: /usr/share/man/man1/prtstat.1.gz exists in filesystem
psmisc: /usr/share/man/man1/pstree.1.gz exists in filesystem
Errors occurred, no packages were upgraded.
I have no idea how to fix this psmisc issue, but I am more concerned about the continued corruption of the SSD. I have just disabled ext4 journaling, as I have read that can help with SSD performance, but I don't think that will solve the issue. If anyone has the time to point me in the right direction, I would be very grateful. If any further info is required, just ask...
SMART info:
[root@shuttlebox ~]# smartctl --all /dev/sda
smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.7.10-1-ARCH] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: V4-CT032V4SSD2
Serial Number: 200001657
LU WWN Device Id: 5 00a075 60bebc879
Firmware Version: S5FAMM22
User Capacity: 32,017,047,552 bytes [32.0 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Sun May 19 12:49:16 2013 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 255) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 2) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 65535
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 3920
12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 50
33 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 160
168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0
177 Wear_Leveling_Count 0x0003 100 100 010 Pre-fail Always - 446
181 Program_Fail_Cnt_Total 0x0003 100 100 000 Pre-fail Always - 0
182 Erase_Fail_Count_Total 0x0003 100 100 000 Pre-fail Always - 0
192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 28
170 Unknown_Attribute 0x0003 067 067 010 Pre-fail Always - 790273982473
173 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 109001417
218 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0
231 Temperature_Celsius 0x000b 100 100 000 Pre-fail Always - 44
232 Available_Reservd_Space 0x000b 100 100 000 Pre-fail Always - 184
233 Media_Wearout_Indicator 0x000b 100 100 000 Pre-fail Always - 8025
241 Total_LBAs_Written 0x0013 100 100 000 Pre-fail Always - 108
242 Total_LBAs_Read 0x0013 100 100 000 Pre-fail Always - 4
246 Unknown_Attribute 0x0002 100 100 050 Old_age Always - 27258900
SMART Error Log Version: 1
Warning: ATA error count 65535 inconsistent with error log pointer 3
ATA Error Count: 65535 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 65535 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 08 f8 42 04 e2 Error: UNC 8 sectors at LBA = 0x020442f8 = 33833720
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 f8 42 04 e2 08 00:29:27.000 READ DMA
27 00 00 00 00 00 e0 08 00:29:27.000 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 08 00:29:27.000 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 08 00:29:27.000 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 00:29:27.000 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 65534 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 08 f0 42 04 e2 Error: UNC 8 sectors at LBA = 0x020442f0 = 33833712
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 f0 42 04 e2 08 00:29:26.750 READ DMA
27 00 00 00 00 00 e0 08 00:29:26.500 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 08 00:29:26.500 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 08 00:29:26.500 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 00:29:26.500 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 65533 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 08 c8 7f 44 e1 Error: UNC 8 sectors at LBA = 0x01447fc8 = 21266376
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 c8 7f 44 e1 08 00:29:26.250 READ DMA
27 00 00 00 00 00 e0 08 00:29:26.250 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 08 00:29:26.250 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 08 00:29:26.250 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 00:29:26.250 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 65532 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 08 c0 7f 44 e1 Error: UNC 8 sectors at LBA = 0x01447fc0 = 21266368
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 c0 7f 44 e1 08 00:29:25.750 READ DMA
27 00 00 00 00 00 e0 08 00:29:25.750 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 08 00:29:25.750 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 08 00:29:25.750 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 00:29:25.750 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 65531 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 08 98 b0 0f e0 Error: UNC 8 sectors at LBA = 0x000fb098 = 1028248
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 98 b0 0f e0 08 00:29:25.500 READ DMA
27 00 00 00 00 00 e0 08 00:29:25.500 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 08 00:29:25.500 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 08 00:29:25.500 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 00:29:25.500 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 0 -
# 2 Extended offline Completed without error 00% 1 -
# 3 Short offline Completed without error 00% 1 -
# 4 Extended offline Completed without error 00% 0 -
Selective Self-tests/Logging not supported
# journalctl | tail -2000:
May 04 20:00:12 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 04 20:00:33 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 04 20:00:33 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 04 20:00:37 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 04 20:00:40 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 04 20:43:35 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 04 20:43:35 shuttlebox kernel: UDP: bad checksum. From 78.147.115.127:1187 to 192.168.1.5:11998 ulen 73
May 04 20:44:01 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 04 20:44:01 shuttlebox kernel: UDP: bad checksum. From 78.147.115.127:1187 to 192.168.1.5:11998 ulen 64
May 04 23:07:01 shuttlebox dhcpcd[374]: eth0: renewing lease of 192.168.1.5
May 04 23:07:01 shuttlebox dhcpcd[374]: eth0: acknowledged 192.168.1.5 from 192.168.1.1
May 04 23:07:01 shuttlebox dhcpcd[374]: eth0: leased 192.168.1.5 for 259200 seconds
May 05 11:21:50 shuttlebox systemd[1]: Starting Cleanup of Temporary Directories...
May 05 11:21:50 shuttlebox systemd[1]: Started Cleanup of Temporary Directories.
May 06 11:07:01 shuttlebox dhcpcd[374]: eth0: renewing lease of 192.168.1.5
May 06 11:07:01 shuttlebox dhcpcd[374]: eth0: acknowledged 192.168.1.5 from 192.168.1.1
May 06 11:07:01 shuttlebox dhcpcd[374]: eth0: leased 192.168.1.5 for 259200 seconds
May 06 11:21:50 shuttlebox systemd[1]: Starting Cleanup of Temporary Directories...
May 06 11:21:50 shuttlebox systemd[1]: Started Cleanup of Temporary Directories.
May 06 13:52:47 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 14:10:53 shuttlebox kernel: jme 0000:02:00.5 eth0: TCP Checksum error
May 06 17:57:47 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 17:58:07 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 18:07:31 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 18:16:54 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 18:17:46 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 18:33:53 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 18:40:24 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 19:11:47 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 19:12:07 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 19:19:50 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 19:39:39 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 20:59:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 20:59:29 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 06 21:03:51 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 07 11:21:50 shuttlebox systemd[1]: Starting Cleanup of Temporary Directories...
May 07 11:21:50 shuttlebox systemd[1]: Started Cleanup of Temporary Directories.
May 07 23:07:01 shuttlebox dhcpcd[374]: eth0: renewing lease of 192.168.1.5
May 07 23:07:01 shuttlebox dhcpcd[374]: eth0: acknowledged 192.168.1.5 from 192.168.1.1
May 07 23:07:01 shuttlebox dhcpcd[374]: eth0: leased 192.168.1.5 for 259200 seconds
May 08 11:21:50 shuttlebox systemd[1]: Starting Cleanup of Temporary Directories...
May 08 11:21:50 shuttlebox systemd[1]: Started Cleanup of Temporary Directories.
May 08 17:44:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:45:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:45:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:45:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:46:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:46:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:46:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:47:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:47:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:47:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:48:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:48:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:48:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:49:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:49:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:49:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:50:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:50:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:50:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:51:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:51:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:51:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:52:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:52:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:52:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:53:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:53:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:53:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:54:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:54:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:54:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:55:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:55:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:55:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:56:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:56:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:56:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:57:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:57:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:57:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:58:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:58:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:58:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:59:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:59:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 17:59:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:00:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:00:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:00:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:01:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:01:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:01:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:02:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:02:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:02:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:03:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:03:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:03:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:04:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:04:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:04:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:05:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:05:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:05:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:06:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:06:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:06:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:07:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:07:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:07:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:08:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:08:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:08:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:09:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:09:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:09:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:10:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:10:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:10:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:11:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:11:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:11:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:12:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:12:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:12:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:13:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:13:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:13:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:14:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:14:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:14:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:15:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:15:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:15:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:16:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:16:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:16:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:17:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:17:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:17:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:18:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:18:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:18:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:19:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:19:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:19:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:20:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:20:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:20:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:21:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:21:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:21:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:22:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:22:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:22:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:23:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:23:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:23:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:24:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:24:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:24:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:25:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:25:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:25:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:26:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:26:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:26:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:27:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:27:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:27:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:28:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:28:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:28:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:29:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:29:37 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:29:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:30:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:30:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:30:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:31:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:31:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:31:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:32:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:32:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:32:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:33:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:33:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:33:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:34:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:34:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:34:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:35:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:35:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:35:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:36:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:36:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:36:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:37:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:37:37 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:37:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:38:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:38:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:38:57 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:39:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:39:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:39:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:40:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:40:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:40:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:41:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:41:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:41:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:42:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:42:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:42:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:43:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:43:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:43:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:44:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:44:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:44:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:45:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:45:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:45:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:46:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:46:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:46:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:47:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:47:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:47:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:48:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:48:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:48:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:49:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:49:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:49:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:50:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:50:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:50:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:51:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:51:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:51:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:52:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:52:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:52:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:53:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:53:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:53:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:54:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:54:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:54:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:55:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:55:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:55:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:56:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:56:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:56:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:57:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:57:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:57:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:58:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:58:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:58:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:59:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:59:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 18:59:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:00:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:00:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:00:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:01:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:01:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:01:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:02:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:02:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:02:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:03:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:03:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:03:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:04:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:04:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:04:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:05:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:05:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:05:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:06:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:06:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:06:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:07:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:07:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:07:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:08:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:08:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:08:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:09:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:09:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:09:58 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:10:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:10:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:10:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:11:17 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:11:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:11:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:12:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:12:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:12:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:13:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:13:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:13:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:14:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:14:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:14:57 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:15:17 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:15:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:15:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:16:17 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:16:40 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:16:58 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:17:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:17:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:17:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:18:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:18:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:18:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:19:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:19:39 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:19:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:20:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:20:37 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:20:58 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:21:18 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:21:42 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:21:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:22:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:22:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:22:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:23:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:23:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:23:56 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:24:16 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:24:36 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:24:58 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 19:25:00 shuttlebox kernel: jme 0000:02:00.5 eth0: UDP Checksum error
May 08 21:08:09 shuttlebox kernel: jme 0000:02:00.5 eth0: TCP Checksum error
May 08 21:08:44 shuttlebox kernel: jme 0000:02:00.5 eth0: TCP Checksum error
May 09 08:33:20 shuttlebox dhcpcd[374]: eth0: carrier lost
May 09 08:33:20 shuttlebox kernel: jme: Disable TX engine timeout
May 09 08:33:20 shuttlebox kernel: jme 0000:02:00.5 eth0: Link is down
May 09 08:33:23 shuttlebox dnsmasq[445]: no servers found in /etc/resolv.conf, will retry
May 09 08:33:33 shuttlebox dhcpcd[374]: eth0: carrier acquired
May 09 08:33:33 shuttlebox kernel: jme 0000:02:00.5 eth0: Link is up at ANed: 1000 Mbps, Full-Duplex, MDI-X
May 09 08:33:33 shuttlebox dhcpcd[374]: eth0: sending IPv6 Router Solicitation
May 09 08:33:33 shuttlebox dhcpcd[374]: eth0: rebinding lease of 192.168.1.5
May 09 08:33:33 shuttlebox dhcpcd[374]: eth0: acknowledged 192.168.1.5 from 192.168.1.1
May 09 08:33:33 shuttlebox dhcpcd[374]: eth0: checking for 192.168.1.5
May 09 08:33:37 shuttlebox dnsmasq-dhcp[445]: DHCP packet received on eth0 which has no address
May 09 08:33:37 shuttlebox dhcpcd[374]: eth0: sending IPv6 Router Solicitation
May 09 08:33:38 shuttlebox dhcpcd[374]: eth0: leased 192.168.1.5 for 259

Cheers folks.
The drive (http://www.amazon.co.uk/gp/product/B00826WCL4) was purchased about 6 months ago and has only ever been used in this setup. Is there anyway to prove that the disk really is rubbish, and could its condition be as a result of my poor system configuration?
Incidentally, whenever I have performed SMART tests on the disk, its show no errors - whys that?
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 0 -
# 2 Extended offline Completed without error 00% 1 -
# 3 Short offline Completed without error 00% 1 -
# 4 Extended offline Completed without error 00% 0 -
Thanks again
Last edited by jm82 (2013-05-20 15:20:22)

[svn] 2594: For the following:

Revision: 2594 Author: [email protected] Date: 2008-07-23 11:41:51 -0700 (Wed, 23 Jul 2008) Log Message: ----------- For the following: <?xml version="1.0" encoding="utf-8"?> <mx:Application xmlns="http://ns.adobe.com/mxml/2009" xmlns:mx="library:adobe/flex/halo"> <Graphic > <Model/> </Graphic> </mx:Application> Two initializers were being created. One for the top level variable, created via ModelBuilder's registerModel() call. The other for the Graphic.content default property. Both initializers were creating a RHS initializer function, which was causing a duplicate function error. This fix just suppresses the creation of the top level variable and it's associated initializer, if the Model isn't toplevel. I suspect no one has run into this before, because most visual components don't have an untyped property, which is set to a Model. Very rare edge case. tests Passed: checkintests Needs QA: YES Needs DOC: NO Bug fixes: SDK-16039 API Change: NO Reviewer: clucier Code-level description of changes: DocumentBuilder.java Modified ModelBuilder constructor call to pass in null for the parent. ModelBuilder.java Added parent variable and modified constructor to set it. Modified analyze(ModelNode) to pass in (parent == null) for the toplevel param of registerModel(). AbstractBuilder.java Modified ModelBuilder constructor call to pass in model for the parent. Ticket Links: ------------ http://bugs.adobe.com/jira/browse/utf-8 http://bugs.adobe.com/jira/browse/SDK-16039 Modified Paths: -------------- flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AbstractBuilder.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBuilder.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ModelBuilder.java

Based on the current benchmarks and reviews, I would say the MBA could +in theory+ do all that, but I think you would be highly disappointed with its performance. You may be ok if you did only one of the things you listed at a time, but I'm getting the feeling that this isn't the way you would like to use your notebook.
The biggest weakness of the MBA is the inability to upgrade the RAM beyond 2GB, as well as the slower parallel ATA interface the HDD uses. Bottom line - the MBA wasn't really designed for anything beyond light use (writing, note taking, email, web browsing) But if portability>performance (for you), then I'd suggest seeing how the MBA fares by heading down to an Apple Store and putting one through its paces before committing to buying one.
I just see so many posts here where people with a laundry list of expectations from a notebook are ready to drop ~$1800 for an MBA when from a practical standpoint, that kind of money would be better spent on a higher performing MB or MBP. (IMO)
Message was edited by: Shaggywerewolf

Academic version of Aperature, Same as Standard?

I have the ability to purchase the Academic version of Aperature which affords substantial savings over the regular version. Is it the same version as the regular and can it be updated. I have heard remarks about an inability to upgrade the Academic version.

By normal patterns of upgrade pricing, the Academic version saves money through two or three major upgrades. ($150 * 3 < $300 + $100 + $100. But of course there are no guarantees what the upgrade prices will be.)
But this moment is special: with Leopard out there seems to be reason to expect version 2 within months if not weeks. Not a good time for the one-shot deal of the Academic version. That's what I bought, and I'll have to pay out the same $150 (presumably) when v2 comes out. But meanwhile I've had about a year with version 1 (1.1, 1.5, 1.5.6), and I will expect to get at least two to four years out of the next one, so I'm not losing money until perhaps 2011--too far off to worry about.
So if you can wait, go for the Academic when v2 hits the stands. It might possibly be so close that for new purchasers of 1.5 would be a free upgrade, though I wouldn't count on that.

Please Fix Credit Auth. in App Store -- PLEASE

This inability to upgrade apps on my iPhone 4 from my iPhone 3 is just stupid! Sometimes I can enter a different credit card (PLEASE EXPLAIN YOUR POOR PROGRAMMING TO MY ACCOUNTANT) and other times I can not.
I have entered two different credit card numbers and their codes and dates so many times that I now give up. The crooks have won, the honest Apple customers have lost, and my apps want to be upgraded.
Just make it simple.
Otherwise, let's tell prospective buyers to hold off on their upgrades until some junior programmer gets their poop together!!!

This is a user-based forum. Your feedback will reach Apple's ears at the link below:
http://www.apple.com/feedback/iphone.html

I can't install WebOS Doctor on my mac.

I have an iMac running 10.5.8 and I have tried to install WebOS doctor several times. When it is loading and the Box switches from saying "Downloading" to "Verifying" it suddenly stops running and then restarts the whole process again. Any help?
Post relates to: Centro (AT&T)

Same OS, Same issue... never followed up on it as it turns out my inability to upgrade to 2.1.0 was a two fold Rogers issue (Canada). First they had the 3G network down for several hours in my area, then the WebOS update would time out on their site. Let me know if you get it to work.

MBR vs MBP w/ SSD

Hey guys,
A new computer has been looming in my horizon for a few months, and the time is very close. I'm deciding between a 15" MBR w/ 256GB storage or a 15" MBP. If I put a SSD in the MBP (let's say a Samsung 840 Pro 256 GB), is there really any difference in the speed comparison test? The MBR is so nice but the inability to upgrade is a pretty big turnoff for me.
Any input is greatly appreciated.
Thanks,
Ryan

It's up to you, but I suggest you to choose the MacBook Pro with a SSD. First of all, you may get a better performance of the SSD with the MacBook Pro without Retina display depending on the SSD you install, and also, it's much more customizable: on the MacBook Pro without Retina display, you can add more RAM and a hard drive without voiding warranty. Finally, repairs are less expensive because there are less parts soldered.
The SSD you want to install, a Samsung 840 Pro, sometimes gives problems and users complain about failures. I recommend you to go for another SSD

2.3 or 2.6 Ghz

What to buy? The new Macbook Pro 15" with 2.3 GHz and 256 Gb memory or Pro with 2.6 Ghz and 500 GB memory. Have planed to use the Mac with Parallels and Windows. I have also planned to buy the 16 GB RAM version. What is the advantage of buying the most powerful computer?

I went and looked at them after work today and the screen is awesome and a game changer in the laptop arena. I didn't put it through any serious enough test to tell whether 2.3 or 2.6 are much different. For me, as a photographer I know that since ram isn't upgradable (a dissapointment that I don't appreciate on Apple's part) I would get 16GB. Also a disappointment is a current inability to upgrade the drive.
So as I was toying with the different models, I found myself trying to sort out my strategy of trying to save 600 USD. I checked out my iMac at home. The surprising news to me is that with all the apps I have and that includes CS5 , CS3 plus Lightroom and Aperture, iPhoto and FCPX, Office and a bunch of other little apps, I only use about a little over 22GBs. I have 170 GBs of photographs and the library uses about 36GB. I also have a couple of USB/Firewire portable drives but they are only USB 2. Not to mention several TB of other external HD storage hooked to an iMac. Or kept seperately.
I went on line to check out TB external drives and there are very few currently and seem overly expensive a little prohibitive now but should mature as the market developes. USB 3.0 is better price wise it seems. So I think my strategy will be to get the 2.3, 16GB and an external drives for data etc. With 256 flash drive I would have more than enough room to store my music (not huge) and a few sets of current photo projects. I would just have to move them off and back-up much more quickly than with a 500 GB drive. I think with the cost of these flash drives, I would prefer to save the money. The CPU isn't that much of a performance difference, ram will be more important as time goes buy. You may come up with different conclusions.
I probably will wait a couple of months to do this. I like to wait till production kinks are flowing smoothly and may even wait to the refresh. My late MBP really is still pretty sweet and the screen is still pretty good, not nearly what the big iMac is for critical work, but quite good enough for field work. However, these Retina screens are really a big deal for visual content creation. This brings me to a couple of questions for people, not to hijack this thread, but has anyone seen anything about color calibration with the current pucks on the market? Colors looked pretty accurate to me at the store but I would still want to calibrate the monitor for color accuracy. Also has anyone seen a TBolt to either FW or eSata adaptor?
Thanks

Osx 10.6.8 inability to upgrade to OSX 10.8.1

Similar Messages

Maybe you are looking for