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)
Similar Messages
-
Macbook Pro early 2011 often ssd corruption
As i installed Drive Geniuou Pro 3 on my macbook early 2011 equipped with 128 GB SSD i noticed that every month i've got some check failing on the hard disk (in drive geniuos -> verification failed -> must run repair) and this reflects in a little performance slow down and i think i always had this problem, even before installing drive geniuos, bacause i noticed those performance issues in the past. Booting from the drive geniuos cd and running repair solves the problem but it becomes frustrating because it happens so often. Is there a way to run some checks or procedure to keep in health my disk? Or maybe it is an ssd probelm and there is a patch?
gavabri wrote:
SSD disk is an apple TS128C and unfortunately i cannot take it in assistance because i need it for work.
What i cannot understand is why disk corrupts because macbook never freezed and never had probelm saving, moving, copying files!
You have a Toshiba SSD in your Macbook.
It sounds more like a software issue rather than a hardware issue - do you have a USB external drive handy with no files in them? I was going to suggest you clone your SSD to the external drive and once that's done - boot from your external drive - open disk utility and do a format/erase on your ssd using a secure erase - once that's done, clone your external drive to your internal drive - restart your macbook and see if problem continues.
more than likely however, you still might have the issue since you're just doing a clone but it's worth a try.
a clean install is a much better solution but you have to do a backup of your contents so you can restore after. -
I have an external OWC SSD that I use to store my iTunes library. Three times now the filesystem on the SSD has become corrupted while TimeMachine was backing it up. I am open to the idea of this being an issue with the drive itself, but all three times this has happened, I plug the drive into a Win machine, format it, and run a disk check and it always reports that there are no issues; after which I put the drive back into my mac, format it, and throw my iTunes library back on it.
Has anyone else experienced anything like this before? After the ssd becomes corrupt, plugging it back into a mac will lock-up Finder.You probably have a bad controller in the enclosure. Purchase another and see if the SSD will work (they're very inexpensive and some are simply better than others - I use OWC enclosures for all of my clone drives).
Good luck,
Clinton -
Folio 13-2000 unable to create recovery media due to known SSD corruption bug
My folio has been freezing and periodically showing the 'no boot drive' message. I tracked it down to the critical Softpaq sp60976. I tried to create recovery media (USB flash drive), but it fails at about 19% completion and says it cannot continue. The SSD firmware update requires a secure wipe of the drive, but I won't have anything to put back on it.
My computer is out of warranty by a year. Is there really no recovery media, even for purchase, from HP? I'll take DVD, as I can attach an external DVD drive.
This question was solved.
View Solution.Phone your nearest HP Support to order Recovery Media. Worldwide contact info can be accessed here>Contact HP
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others** -
Why do i continuously get corrupted content message after installing newest updates?
I use Project Free TV quite a bit. It was working great, but after I installed new updates for Firefox, most of the links don't work and gives me Corrupted Content message. The links work fine through Explorer.
For example:
'''Corrupted Content Error'''
The page you are trying to view cannot be shown because an error in the data transmission was detected.
The page you are trying to view cannot be shown because an error in the data transmission was detected.Please contact the website owners to inform them of this problem.''I use Project Free TV quite a bit. It was working great, but after I installed new updates for Firefox, most of the links don't work and gives me Corrupted Content message. The links work fine through Explorer.
For example:
'''Corrupted Content Error'''
The page you are trying to view cannot be shown because an error in the data transmission was detected.
The page you are trying to view cannot be shown because an error in the data transmission was detected.Please contact the website owners to inform them of this problem.'' -
Corrupted CPD file in RH7 (again)
I've had this ongoing problem that rears its ugly head every
two months. My CPD file continues to corrupt when it reaches 1500
KB. This project was originally built in X5 and then we upgraded to
RH7. I initially would compress this file using MS Access. Then
when it grew to 1500 KB it would corrupt again. So two months ago I
deleted the CPD file and reopened the project using the XPJ file.
All the links were broken. I painstakingly fixed all the links over
a two-day period- thinking this would fix it once and for all. Now
it's corrupted again. What can I do to fix this permanently? Why is
it continuing to corrupt? Is it necessary to compress this file
periodically?
I also tried renaming the the CPD and XPJ files and then
opening the project using the HHP file. This also leaves the
project with many broken links- but maybe these links are broken
because RH is not seeing the folders for these topics in RH but
they exist in Windows Explorer (I have Peter's instructions on
remedying this). Again, my main objective is to find a permanent
solution to this problem- if one exists. Thanks-
Cheers
RichGEWB,
Well, the folder I deleted was a user-created one that my
boss had made. But here is an example: the project had a folder
called "Authorizations" in Project Manager. But when I opened the
project folder in Explorer, there was the Authorizations folder,
but then another duplicate folder with that name was inside a
folder called "Online Help". This Online Help folder had just odds
and ends thrown in it. What it would do though is cause RH to break
the links to the legitimate topics in the Authorizations folder and
this folder would not appear when I rebuilt the project. Because
this folder existed on two levels, it seemed to confuse RH so it
would leave it out all together. When I deleted this unnecessary
folder, the project rebuilt without any problems. So I think it's
important if you inherit a project to make sure there aren't any
residual folders that might conflict with existing ones. Hope this
helps-
All the best,
Rich -
Here I am back 2 yrs later with the same problem that has never been solved and is only worse now. i photo continues to corrupt photos and they become only available as little thumbnails. Trying to rebuild is impossible because of individual Alert msg. that orig item cannot be found. This becomes daunting because there are probably 1200 to 1500 lost. Trying to create and populate a new library takes immense patience too because there are over 500 rolls some with only one photo in them. 2/3's of original photos are on DVD but many aren't. I use Super Duper to an external hard drive and have found out that the backup has just replicated the latest corruption every time I backup "newer files". I should mention that if I ever search via spotlight or search window in iphoto6 for a photo that has been corrupted that once it starts it makes me go through individually searching for every photo and won't let me out until I finally have to shut down the hard drive. TD was helping me b4. Anybody have any new ideas? Thanks
I'm sorry but you're not explaining how iPhoto is corrupting photos. What you're describing is how the database file is damaged and it's too long to fix?
The solution to the problem is one of the problem regardless of the time it takes:
Try these in order - from best option on down...
1. Do you have an up-to-date back up? If so, try copy the library6.iphoto file from the back up to the iPhoto Library allowing it to overwrite the damaged file.
2. Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
3. If neither of these work then you'll need to create and populate a new library.
To create and populate a new *iPhoto 6* library:
Note this will give you a working library with the same Rolls and pictures as before, however, you will lose your albums, keywords, modified versions, books, calendars etc.
Move the iPhoto Library to the desktop
Launch iPhoto. It will ask if you wish to create a new Library. Say Yes.
Go into the iPhoto Library on your desktop and find the Originals folder. From the Originals folder drag the individual Roll Folders to the iPhoto Window and it will recreate them in the new library.
When you're sure all is well you can delete the iPhoto Library on your desktop.
In the future, in addition to your usual back up routine, you might like to make a copy of the library6.iPhoto file whenever you have made changes to the library as protection against database corruption.
Regards
TD -
For some reason my 5th Gen iPod has become corrupt.
When connected to iTunes I get a message to restore it which I have done several times.
Is there a file on my Mac that is also corrupt causing the iPod to be restored which continues to corrupt it?
Once I connected it to another Mac and gave it a different name it has behaved so far. If I change the name to what it had been the silliness starts all over again.
I'm wondering if anyone else has had this issue?
Thanks,See here: What to do if iPod can't be updated because the firmware file was corrupt or not found
B-rock -
MacBook Pro - not liking new ssd
Hello,
I am having a slight problem with my Macbook Pro 13" Early 2011
My old ssd corrupted, used as a primary disk with 500gb storage (Samsung 840 500gb)
So I decided it was time for an upgrade anyway and ordered a Samsung 500gb 840EVO as after using Samsung's SSDs throughtout my household and only this time have I had an issue (this is much better than OCZ and other companies)
I managed to recover the files on my 840, and put them on my spare backup drive, and I can run from there like a dream.
However with my new ssd, whenever it is in the main HDD slot I cannot boot from it, and when I run it through where the disk drive used to be, I get the same issue (I cannot take my mac back to apple due to having the disk drive removed), however if I connect my new ssd via usb I can boot it up perfectly (I am writting this via it) but this is not very practical for day to day use, does anyone know how I could fix this so I can connect my ssd inside my mac (either in the main drive or via where the disk drive is (I dont mind!))
Thanks in advance,
Kind Regards,
˜Maxcan you confirm if this is ok to buy:
http://www.ebay.ca/itm/New-HDD-Hard-Drvie-Cable-for-13-MacBook-Pro-A1278-MD101-M D102-821-1480-A-2012-/181269577616?pt=LH_DefaultDomain_0&hash=item2a34823f90&_u h b=1
or
http://www.ebay.ca/itm/NEW-MacBook-Pro-Unibody-13-A1278-2012-md101-102-HDD-Hard- Drvie-Cable-821-1480-A-/121183868039?pt=LH_DefaultDomain_0&hash=item1c371f1487& _ uhb=1
or this one..??
http://www.ebay.ca/itm/for-APPLE-MacBook-Pro-13-A1278-HDD-Hard-Drvie-Cable-MD101 -MD102-821-1480-A-2012-/331060187298?pt=LH_DefaultDomain_0&hash=item4d14b990a2& _ uhb=1
i guess i aint gotta buy those brackets again..?
Thanks
Anjillan -
IPad Air with iOS 8.02 freezes and blue screen appears. What should be done ? Why is this happening ?
If nothing else works, you might try this one. It has worked for many others ...
Use iTunes to do a reset to factory default condition. Always be sure to do your backups before fiddling with your iPad. You might do both the iCloud and the iTunes backup, just to be sure!
Back up and Restore your iOS Device with iCloud or iTunes
http://support.apple.com/kb/ht1766
iTunes: About iOS Backups
http://support.apple.com/kb/ht4946
Use iTunes to Restore your iOS Device to Factory Settings
http://support.apple.com/kb/ht1414
Various issues from many different users have been solved by this. I've lost count on how many have been helped by this, so far. But, it doesn't mean EVERYONE will be helped, but I've seen a whole lot. You can only try and see ...
iPad 2 and iOS 8.0.2 Problems
For all iPad 2 owners, this is an important solution for you! These problems result from long-term use, continuous upgrades, corrupted files and various glitches that happen over this long term use. You just need to get your iPad 2 back to FACTORY FRESH CONDITION to start out clean!
Here's one person's solution which will help a lot of iPad 2 users!
keithfrommariettaOct 12, 2014 3:25 PM Re: IPAD2 very slow after IOS 8 upgrade
Re: IPAD2 very slow after IOS 8 upgradein response to pacoKAS
SOLVED: IOS 8 Issues on iPad 2:
I just returned home from a visit to the Genius Bar. Like you and many others, when I upgraded my iPad 2 to IOS 8, it became practically unusable. It was VERY slow, lagged whenever trying to to do anything. Lots of screen freezes and apps spontaneously crashing. I was convinced that the processor on the iPad 2 just couldn't handle the new IOS and I went in to see about restoring to IOS 7.
Thankfully, I was hooked up with a very sharp guy at the bar. The problem is not with the OS, it is with it being an *upgraded* OS. He used the analogy of when you had an older Windows computer and how over time (and over upgrades), they just tended to get slower and slower because of all of the garbage that was carried forward in the upgrades. At those times (and if you've ever had a Windows computer, you get this), the only thing that would speed it up would be to wipe the machine and do a fresh install of the current OS and then reload your apps, and the viola, everything would be fast again. Well, it turns out that IOS can suffer the same problems.
THE FIX: FIRST, be sure you have a current iCloud backup of your device. Connect your iPad to a computer that has a clean fresh copy of IOS 8 on iTunes (this is best done with a computer other than the one that you sync your device to because you DO NOT want to restore it from a back up just yet). Ideally, if you do this at an Apple store you'll be assured of the right version there and someone to answer any questions you might have along the way. You then hold the power and home button down to hard-reset the device and continue to hold them down until it reboots into recovery mode. You then follow the instructions on the computer to reinstall the OS on the device (which wipes everything from it and then reinstalls a clean copy of it). Once this is done (which only takes about 15 minutes), your device will reboot and ask you to set it up. Answer the questions about language, location, etc. and continue until it asks you to log into your iTunes account. Once you do that, it will ask if you want to either 1) Set it up as a new device, 2) Restore from iCloud, or 3) Restore from iTunes. Choose (2), restore from iCloud. This will ensure that it brings down "clean" copies of all of your apps and preferences rather than the potentially corrupted ones that might reside in your iTunes backup. That's it! It will take a few hours depending on how much data and apps you have, but I am happy to report that my iPad 2 is now running IOS 8 and it's running as fast as it ever did when it was brand new!
To sum it up, this process 1) Wipes your device and the garbage causing your problems, 2) Loads a clean and bug-free version of IOS 8 to your device, and 3) restores your apps and data so that it looks just like it did before the wipe, with the exception that it works now! :-)
Note also that by following this process you don't have to go through the painful and laborious process of reloading all of your apps, data and/or settings. iCloud takes care of all of that for you. -
Query networking into hostile windows environment
I have been getting kernel panics on shutdown of my new Imac 24 since i got it out of the box.
Additionally I have had a disintegrating experience with Airport.
At first was working fine and i could connect to net etc.
Then problems connectng, etc.
To the point where i cannot even see the hardware in system profile anymore.
The crash reports after the KPs implicate the Airport kexts.
I did a archive and install - no love.
I used pacifist and extracted and installed airport drivers etc. Restarted.
Voila I could see Airport ... yay. shutdown - no KP. Yay.
Restart, no Airport, and KPs again.
My theory
I am in an area thick with wireless networks.
Something i did trying to connect to something has corrupted and continues to corrupt my Airport drivers every startup.
Is this a possibility?
I am fine using the ethernet into the network.
I am contemplating taking the machine back to apple when i have finished the job i am doing here.
regards
PStrangest thing!
2 months after this problem occurring everyday
to the point where I dont even think about it
I noticed that the crash reports were no longer appearing at startup
and the hard shutdown was no longer required
and voila the airport card is visible again
IT HAS FIXED ITSELF
I have no idea how this could be
the machine has not been online, I had stopped doing diagnostic/repair attempts some weeks ago.
could repeated startups work their way through the OS and eventually repair the code?
I do think it is still the hardware behaving erratically
any thoughts
P -
LV 8.5 on XP Pro
I have a project with the build specifications for an executable. The problem is that the startup VI's that are designated in the properties keep coming up missing. The ICON is still in the project, but when I go into the "source files" they do not seem to save. The problem is intermittent. I have tried entering the properties, saving and then closing and reopening LV and had no problems but then the next time I go to do a build I receive error "You did not specify any Startup VI's."
Also the installer properties continually are corrupted and I have to re-create the installer.
Any suggestions?
~goldHey Gold,
Thank you for contacting National Instruments. I'm not exactly sure if I understand your problem, so I do want to clarify what you have going on.
If I understand you correctly, you have a project with VI, documentation, etc, to create an exe as well as an installer. All files appear in the project explorer, and there does not appear to be any problems with the files there. When you go to build an exe, you select your startup VIs, and move them into the Startup VI's section of the build page. When you go to click build, you get an error that you have not selected any startup VI's. Is this correct? Are there any details you would like to add to that?
Also, can you please explain what you mean when you say the installer seems to be corrupted? Can you give any error messages, or a better description of what is going on?
Thanks,
Kevin H
National Instruments
WSN/Wireless DAQ Product Support Engineer -
This is weird... My iPod nano spontaneously reset while I was using it, and after that I noticed that the display quality seems to have gone down. Pictures that previously had smooth color transitions now appear dithered. It almost looks as if the bit depth of the display decreased. Has anybody seen anything like this?? Am I going nuts here??
Resetting the iPod didn't fix this. Replacing the images did not fix this. Help?Agreed, reset the Nano but use the iPod updater to get fresh code back in. A clickwheel+button reset continues reusing corrupted code.
-
Bridge or Lightroom wrecks my NEFs; How? Why?
I cannot tell if it is happening in Bridge or Lightroom2 but I am continually getting corrupted NEFs. Suddenly the files are only icons, unusable. Usually a "-1" alternate version is being created.
What gives? The files show 0 kb content in finder
Also posted in Lightroom.
Mac OSX.4.11; bridge 3.0.0.464 CS4; LR2.1
G5 2.5 4 gb ram 70%
Also this subscribe by email NEVER works.If you develop raw in lightroom you have to use the option 'Save metadata to file' in order to let Bridge read the changes.
Bridge is more a browser for files whilst Lightroom has a database structure of its own were it stores the settings, both applications can work together when you set the options to do so. It should also be in the manual btw :-) -
Lightroom 2 or Bridge CS4 wreck my NEFs. How? Why?
I cannot tell if it is happening in Bridge or Lightroom2 but I am continually getting corrupted NEFs. Suddenly the files are only icons, unusable. Usually a "-1" alternate version is being created.
What gives? The files show 0 kb content in finder
Also posted in bridge foirum.
Mac OSX.4.11; bridge 3.0.0.464 CS4; LR2.1
G5 2.5 4 gb ram 70&
Also this subscribe by email NEVER works.Hi Steve,
I work on the Lightroom team. Please contact me at jkmoch at adobe dot com. We'd like to see some of these files.
Maybe you are looking for
-
My Macbook pro 13 mid 2010 with yosemite not installing window thru bootcamp
Hi...I have Macbook pro 13 mid 2010... runnig os x yosemite, but on this os x i m unable to install windows 7 through bootcamp ! what to do?? plz help???
-
For some reason when I am playing games in fullscreen mode a random frame rate drop will occur. A typical scenario from world of warcraft is as follows. I am in a zone of the game levelling where the graphics are not too demanding. I am getting a smo
-
Guid Partition or Apple Partition?
Hey there, my goal is to set up several Hard Drives to be daisy chained for using them to organize Pictures using Lightroom and backing it up. Just one HD I want to be connected via FireWire 800 to the iMac. Before I start adding the Files to the new
-
Merge query error in Where clause
Following error is coming when i execute the merge query. Anything wrong with this? I am using Oracle 9.2.0.1. Query: MERGE INTO incompletekalls ic USING live_small ls ON ((ls.callid = ic.callid) AND (ls.sdate = ic.sdate) AND
-
Retained Earnings Statement (Financial Statement Version) Issues
1. If I post any thing, will it update Retained earnings account automatically or can I create any formula? 2. The requirement is how the Retained Earnings Beginning of year will update from P&L statement? 3. How the Retained Earnings P+L result w