Beiträge von VinPropane

Same thing this evening

Same error happening this morning.

apt clean gave me the same error:

W: Failed to fetch http://security.debian.org/dists/wheezy/updates/Release  Unable to find expected entry 'deb/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)


E: Some index files failed to download. They have been ignored, or old ones used instead.

Will try again later.

Getting the following:

Error #4000:
exception 'OMVException' with message 'Failed to execute command 'export LANG=C; apt-get update 2>&1': Ign file:  Release.gpg
Ign file:  Release
Ign file:  Translation-en
Hit http://ppa.launchpad.net precise Release.gpg
Hit http://ppa.launchpad.net precise Release
Ign http://dh2k.omv-extras.org stoneburner-miller Release.gpg
Hit http://packages.openmediavault.org stoneburner Release.gpg
Hit http://ppa.launchpad.net precise/main amd64 Packages
Hit http://ppa.launchpad.net precise/main Translation-en
Ign http://dh2k.omv-extras.org stoneburner-vpn Release.gpg
Hit http://packages.openmediavault.org stoneburner Release
Hit http://dh2k.omv-extras.org stoneburner-miller Release
Hit http://packages.omv-extras.org stoneburner Release.gpg
Hit http://packages.openmediavault.org stoneburner/main amd64 Packages
Hit http://dh2k.omv-extras.org stoneburner-vpn Release
Hit http://packages.omv-extras.org stoneburner Release
Hit http://packages.omv-extras.org stoneburner/main amd64 Packages
Ign http://dh2k.omv-extras.org stoneburner-miller/main amd64 Packages/DiffIndex
Ign http://dh2k.omv-extras.org stoneburner-vpn/main amd64 Packages/DiffIndex
Ign http://packages.omv-extras.org stoneburner/main Translation-en
Ign http://packages.openmediavault.org stoneburner/main Translation-en
Hit http://dh2k.omv-extras.org stoneburner-miller/main amd64 Packages
Ign http://dh2k.omv-extras.org stoneburner-miller/main Translation-en
Hit http://dh2k.omv-extras.org stoneburner-vpn/main amd64 Packages
Ign http://dh2k.omv-extras.org stoneburner-vpn/main Translation-en
Hit http://debian.mirrors.tds.net wheezy Release.gpg
Hit http://security.debian.org wheezy/updates Release.gpg
Get:1 http://debian.mirrors.tds.net wheezy-updates Release.gpg [1554 B]
Hit http://security.debian.org wheezy/updates Release
Hit http://debian.mirrors.tds.net wheezy Release
Hit http://security.debian.org wheezy/updates/main Sources
Get:2 http://debian.mirrors.tds.net wheezy-updates Release [151 kB]
Hit http://security.debian.org wheezy/updates/non-free Sources
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit ftp://ftp.us.debian.org wheezy Release.gpg
Hit http://security.debian.org wheezy/updates/non-free amd64 Packages
Hit ftp://ftp.us.debian.org wheezy Release
Hit ftp://ftp.us.debian.org wheezy/non-free amd64 Packages
Hit http://debian.mirrors.tds.net wheezy/main Sources
Hit http://debian.mirrors.tds.net wheezy/main amd64 Packages
Hit ftp://ftp.us.debian.org wheezy/non-free Translation-en
Hit http://debian.mirrors.tds.net wheezy/main Translation-en
Get:3 http://debian.mirrors.tds.net wheezy-updates/main Sources [5515 B]
Get:4 http://debian.mirrors.tds.net wheezy-updates/non-free Sources [929 B]
Hit http://debian.mirrors.tds.net wheezy-updates/main amd64 Packages/DiffIndex
Hit http://debian.mirrors.tds.net wheezy-updates/non-free amd64 Packages/DiffIndex
Hit http://debian.mirrors.tds.net wheezy-updates/main Translation-en/DiffIndex
Hit http://debian.mirrors.tds.net wheezy-updates/non-free Translation-en/DiffIndex
Fetched 159 kB in 7s (21.5 kB/s)
W: Failed to fetch http://security.debian.org/dists/wheezy/updates/Release  Unable to find expected entry 'deb/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)


E: Some index files failed to download. They have been ignored, or old ones used instead.' in /usr/share/openmediavault/engined/rpc/apt.inc:277
Stack trace:
#0 [internal function]: OMVRpcServiceApt->update(NULL, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('update', NULL, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('Apt', 'update', NULL, Array, 1)
#4 {main}

Thanks. I've started the RMA process.

So is this something I should be concerned about? The drive is brand new. The only activity it's been involved in is being added to a RAID group on my NAS.

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 13
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
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 13 [12] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 01 00 00 00 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 02:56:04.234 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e0 00 08 02:56:04.234 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 02:56:04.234 SMART READ LOG
60 04 00 00 80 00 00 9a 21 82 a0 40 08 02:56:04.164 READ FPDMA QUEUED
60 04 00 00 78 00 00 9a 21 7e a0 40 08 02:56:04.164 READ FPDMA QUEUED

Error 12 [11] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 01 00 00 00 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 02:49:53.145 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 02:49:53.145 SMART READ LOG
60 04 00 00 c8 00 00 94 ec 03 38 40 08 02:49:53.078 READ FPDMA QUEUED
60 04 00 00 c0 00 00 94 eb ff 38 40 08 02:49:53.078 READ FPDMA QUEUED
60 04 00 00 b8 00 00 94 eb fb 38 40 08 02:49:53.078 READ FPDMA QUEUED

Error 11 [10] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 01 00 00 00 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 02:39:19.292 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 02:39:19.292 SMART READ LOG
60 04 00 00 28 00 00 8b ea fb 38 40 08 02:39:19.216 READ FPDMA QUEUED
60 04 00 00 20 00 00 8b ea f7 38 40 08 02:39:19.216 READ FPDMA QUEUED
60 04 00 00 18 00 00 8b ea f3 38 40 08 02:39:19.216 READ FPDMA QUEUED

Error 10 [9] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 01 00 00 00 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 02:37:20.637 SMART READ LOG
60 04 00 00 a8 00 00 8a 38 5b 38 40 08 02:37:20.562 READ FPDMA QUEUED
60 04 00 00 a0 00 00 8a 38 57 38 40 08 02:37:20.562 READ FPDMA QUEUED
60 04 00 00 98 00 00 8a 38 53 38 40 08 02:37:20.562 READ FPDMA QUEUED
60 04 00 00 90 00 00 8a 38 4f 38 40 08 02:37:20.562 READ FPDMA QUEUED

Error 9 [8] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 01 00 00 00 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 02:00:23.541 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 02:00:23.541 SMART READ LOG
60 02 20 00 70 00 00 6a 14 bc 40 40 08 02:00:23.456 READ FPDMA QUEUED
60 04 00 00 68 00 00 6a 14 b8 40 40 08 02:00:23.456 READ FPDMA QUEUED
60 04 00 00 60 00 00 6a 14 b4 40 40 08 02:00:23.456 READ FPDMA QUEUED

Error 8 [7] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 01 00 00 00 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 01:58:53.165 SMART READ LOG
60 03 68 00 e0 00 00 68 b8 36 60 40 08 01:58:53.120 READ FPDMA QUEUED
60 04 00 00 d8 00 00 68 b8 32 60 40 08 01:58:53.120 READ FPDMA QUEUED
60 04 00 00 d0 00 00 68 b8 2e 60 40 08 01:58:53.120 READ FPDMA QUEUED
60 04 00 00 c8 00 00 68 b8 2a 60 40 08 01:58:53.120 READ FPDMA QUEUED

Error 7 [6] occurred at disk power-on lifetime: 1 hours (0 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 01 00 00 00 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 01:50:16.776 SMART READ LOG
60 01 a0 00 28 00 00 60 df 92 60 40 08 01:50:16.729 READ FPDMA QUEUED
60 04 00 00 20 00 00 60 df 8e 60 40 08 01:50:16.729 READ FPDMA QUEUED
60 04 00 00 18 00 00 60 df 8a 60 40 08 01:50:16.729 READ FPDMA QUEUED
60 04 00 00 10 00 00 60 df 86 60 40 08 01:50:16.729 READ FPDMA QUEUED

Error 6 [5] occurred at disk power-on lifetime: 1 hours (0 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 01 00 00 00 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 01:49:42.193 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e0 00 08 01:49:42.193 SMART READ LOG
60 03 68 00 e0 00 00 60 58 32 f8 40 08 01:49:42.129 READ FPDMA QUEUED
60 04 00 00 d8 00 00 60 58 2e f8 40 08 01:49:42.129 READ FPDMA QUEUED
60 04 00 00 d0 00 00 60 58 2a f8 40 08 01:49:42.129 READ FPDMA QUEUED

Brand new to OMV. Fresh install on all brand new hardware and I have a drive showing as bad. The SMART info says it passed though.

SMART data:

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 200 200 051 - 1
3 Spin_Up_Time POS--K 100 253 021 - 0
4 Start_Stop_Count -O--CK 100 100 000 - 3
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 100 253 000 - 0
9 Power_On_Hours -O--CK 100 100 000 - 2
10 Spin_Retry_Count -O--CK 100 253 000 - 0
11 Calibration_Retry_Count -O--CK 100 253 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 2
192 Power-Off_Retract_Count -O--CK 200 200 000 - 1
193 Load_Cycle_Count -O--CK 200 200 000 - 0
194 Temperature_Celsius -O---K 123 116 000 - 27
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 1
198 Offline_Uncorrectable ----CK 100 253 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
200 Multi_Zone_Error_Rate ---R-- 100 253 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning