iSCSI Target

IDEEN, WÜNSCHE, FEEDBACK

Moderator: ModTeam

drachen1000
Posts: 44
Joined: Mon Mar 03, 2008 20:33
Location: Lübeck

iSCSI Target

Postby drachen1000 » Sat Jun 13, 2009 8:54

Hallo,
wäre es denkbar, ein iSCSI Target auf dem sblan/ams zu implementieren.
Das Feature ist auf einigen NAS, wie z.B. QNAP möglich.
Gibt es hier schon Ansätze oder macht dieses aufgrund der Performance keinen Sinn.

Gruss
drachen1000

User avatar
Brevheart
Posts: 461
Joined: Wed Feb 21, 2007 9:23
Product(s): Synology DS211j

Re: iSCSI Target

Postby Brevheart » Mon Jun 15, 2009 21:10

Ich weiß nicht mal was ISCSI sein soll! Ein paar Zusatzinfo's mehr müßten es schon sein um was in dieser Richtung zu unternehmen.

Gruß Brevheart

User avatar
lochness
Posts: 3224
Joined: Sat Feb 04, 2006 20:42
Product(s): Myrica TV P42-2H
AMC 570 SAT (3.2.419 + VZD2)
AMC 370 SAT (1.6.115+VZD2)
AMP 150 (1.03.28eu)
3 x AMS 150 (V2.00 + NExt V2.0.06)
SBLAN2 R1.0 (V2.00 + NExt V2.0.06)
SBLAN2 R1.1 (V2.00 + NExt V2.0.06)
Storagebird DUO 35-LR (V1.03)
SB-L V1 (80GB, NetHDD007-0802)
Celvin Q800 4x2TB
Celvin Q700 2x1TB
Celvin Q600 1x2TB
Location: Bad Lippspringe

Re: iSCSI Target

Postby lochness » Mon Jun 15, 2009 22:37

iSCSI kenn ich :). Tja, wie soll ich das erklären :? ... Ist das SCSI Protokoll über LAN umgesetzt. Die Platten werden vom "iSCSI Target" bereitgestellt, der Rechner, der diese verwendet ist der "iSCSI Initiator". Damit sollte man was finden.

Ich gehe mal davon aus, dass man dazu Kernel Module braucht und ob der AMS das von der Leistung her kann, müsste man schauen. Ich habe auch noch keine Implementierung gesucht.

Generell wäre es hilfreich, wenn bei Wünschen ein Referenzprodukt für Linux benannt werden könnte, was genau den Funktionsumfang hat/haben sollte, denn wir kennen auch nicht alle Software für Linux.

drachen1000
Posts: 44
Joined: Mon Mar 03, 2008 20:33
Location: Lübeck

Re: iSCSI Target

Postby drachen1000 » Tue Jun 16, 2009 18:39

Hallo,

iSCSI wird von einigen NAS und auch dem Projekt freenas unterstützt.
Wenn ich es richtig verstanden habe, wird die Festplatte dabei transparent (blockorientiert) über TCP/IP eingebunden und ist damit unabhängig vom Filesystem. Es verhält sich damit praktisch wie ein lokales Laufwerk im eigenen Rechner.
Ein Vorteil ist wohl die Performance, da sehr wenig Overhead (nicht wie smb/cifs).
Ich dachte es wäre vielleicht bekannt, da einige NAS dieses unterstützen.
Ob der AMS/SBLAN Kernel dieses unterstützt, kann ich jedoch nicht sagen.

Gruss
drachen1000

User avatar
Brevheart
Posts: 461
Joined: Wed Feb 21, 2007 9:23
Product(s): Synology DS211j

Re: iSCSI Target

Postby Brevheart » Wed Jun 17, 2009 10:25

So, habe mich ein paar Stunden damit rumgeschlagen und werde nicht weiter machen! Das Problem ist der Kernel 2.4.32. Ab dem 2.6'er ist device-mapping mit drin bei uns nicht! Da ich keinen patch für den 2.4.32 Kernel (der einwandfrei läuft) gefunden habe, muß ich das Thema ISCSI leider zu den Akten legen.

Gruß Brevheart

drachen1000
Posts: 44
Joined: Mon Mar 03, 2008 20:33
Location: Lübeck

Re: iSCSI Target

Postby drachen1000 » Wed Jun 17, 2009 15:48

Hallo Brevheart,

trotzdem vielen Dank für Deine Bemühungen und die Zeit die Du investiert hast.
Ich habe es auch schon vermutet, dass unser Kernel dieses nicht supported.

Ich habe noch einmal eine Bitte.
Gibt es aus Deiner Sicht die Möglichkeit smartmontools zur Überprüfung der Festplatte auf dem sblan/ams zu installieren?
Ich habe nämlich immer Probleme, das mein lighttpd nur nach einem check der Festplatte startet. Nach einem rebbot jedoch nicht mehr. So könnte ich den Zustand der Platte überprüfen.

http://smartmontools.sourceforge.net/
http://smartmontools.wiki.sourceforge.net/NAS

Lt. Beschreibung könnte dieses vielleicht funktionieren:
http://smartmontools.cvs.sourceforge.ne ... iew=markup

Code: Select all

  A) Linux
   30
   31     Any Linux distribution will support smartmontools if it has a
   32     kernel version greater than or equal to 2.2.14. So any recent
   33     Linux distribution should support smartmontools.
   34
   35     There are two parts of smartmontools that may require a patched or
   36     nonstandard kernel:
   37
   38     (1) To get the ATA RETURN SMART STATUS command, the kernel needs
   39     to support the HDIO_DRIVE_TASK ioctl().
   40
   41     (2) To run Selective Self-tests, the kernel needs to support the
   42     HDIO_DRIVE_TASKFILE ioctl().
   43
   44     If your kernel does not support one or both of these ioctls, then
   45     smartmontools will "mostly" work.  The things that don't work will
   46     give you harmless warning messages.
   47
   48     Although "not officially supported" by the developers, smartmontools
   49     has also been successfully build and run on a legacy Linux system
   50     with kernel 2.0.33 and libc.so.5. On such systems, the restrictions
   51     above apply.
   52
   53     For item (1) above, any 2.4 or 2.6 series kernel will provide
   54     HDIO_DRIVE_TASK support.  Some 2.2.20 and later kernels also
   55     provide this support IF they're properly patched and
   56     configured. [Andre Hedrick's IDE patches may be found at
   57     http://www.funet.fi/pub/linux/kernel/people/hedrick/ide-2.2.20/ or
   58     are available from your local kernel.org mirror.  They are not
   59     updated for 2.2.21 or later, and may contain a few bugs.].
   60     If the configuration option CONFIG_IDE_TASK_IOCTL
   61     exists in your 2.2.X kernel source code tree, then your 2.2.X
   62     kernel will probably support this ioctl. [Note that this kernel
   63     configuration option does NOT need to be enabled. Its presence
   64     merely indicates that the required HDIO_DRIVE_TASK ioctl() is
   65     supported.]
   66
   67     For item (2) above, your kernel must be configured with the kernel
   68     configuration option CONFIG_IDE_TASKFILE_IO enabled.  This
   69     configuration option is present in all 2.4 and 2.6 series
   70     kernels. Some 2.2.20 and later kernels also provide this support
   71     IF they're properly patched and configured as described above.
   72
   73     Please see FAQ section of the URL above for additional details.
   74
   75     If you are using 3ware controllers, for full functionality you
   76     must either use version 1.02.00.037 or greater of the 3w-xxxx
   77     driver, or patch earlier 3ware 3w-xxxx drivers.  See
   78     http://smartmontools.sourceforge.net/3w-xxxx.txt
   79     for the patch.  The version 1.02.00.037 3w-xxxx.c driver was
   80     incorporated into kernel 2.4.23-bk2 on 3 December 2003 and into
   81     kernel 2.6.0-test5-bk11 on 23 September 2003.


Gruss
drachen1000

User avatar
Brevheart
Posts: 461
Joined: Wed Feb 21, 2007 9:23
Product(s): Synology DS211j

Re: iSCSI Target

Postby Brevheart » Wed Jun 17, 2009 21:08

smartmontools version 5.38 habe ich compiliert, laufen auch. Ich werde aber nicht so schnell das tools Paket updaten, daher biete ich dir an, die smartmontools per email zu schicken. Bitte per pn.

Gruß Brevheart

drachen1000
Posts: 44
Joined: Mon Mar 03, 2008 20:33
Location: Lübeck

Re: iSCSI Target

Postby drachen1000 » Sun Jun 21, 2009 8:52

Hallo Brevheart,
ich habe ein wenig mit smartmontools ausprobiert, bin jedoch mit meinem Problem leider noch nicht weitergekommen. Ich bin mir nicht sicher, ob die Werte normal sind. Vielleicht könntest Du Dir diese einmal ansehen.

Code: Select all

smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.10 family
Device Model:     ST3500630AS
Serial Number:    9QG63VC7
Firmware Version: 3.AAD
User Capacity:    500,107,862,016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu Jun 29 22:35:51 2006 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

SMART Disabled. Use option -s with argument 'on' to enable it.
smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.10 family
Device Model:     ST3500630AS
Serial Number:    9QG63VC7
Firmware Version: 3.AAD
User Capacity:    500,107,862,016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu Jun 29 22:36:29 2006 UTC
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:  (0x82)   Offline data collection activity
               was completed without error.
               Auto Offline Data Collection: Enabled.
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:        ( 430) seconds.
Offline data collection
capabilities:           (0x5b) 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.
               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:     ( 163) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   120   099   006    Pre-fail  Always       -       237852909
  3 Spin_Up_Time            0x0003   093   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       125
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       835679
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       32
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       147
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       359
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   069   055   045    Old_age   Always       -       31 (Lifetime Min/Max 26/32)
194 Temperature_Celsius     0x0022   031   045   000    Old_age   Always       -       31 (0 21 0 0)
195 Hardware_ECC_Recovered  0x001a   113   067   000    Old_age   Always       -       200181446
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 TA_Increase_Count       0x0032   099   252   000    Old_age   Always       -       1

SMART Error Log Version: 1
ATA Error Count: 840 (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 840 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 b9 00 54 e0 00      00:46:32.199  READ DMA EXT
  25 00 08 b1 00 54 e0 00      00:46:32.196  READ DMA EXT
  25 00 08 a9 00 54 e0 00      00:46:32.193  READ DMA EXT
  25 00 08 a1 00 54 e0 00      00:46:32.188  READ DMA EXT
  25 00 08 99 00 54 e0 00      00:46:32.188  READ DMA EXT

Error 839 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 40 b9 00 54 e0 00      00:46:27.675  READ DMA EXT
  25 00 48 b1 00 54 e0 00      00:46:25.456  READ DMA EXT
  25 00 50 a9 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 58 a1 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:18.807  READ DMA EXT

Error 838 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 48 b1 00 54 e0 00      00:46:27.675  READ DMA EXT
  25 00 50 a9 00 54 e0 00      00:46:25.456  READ DMA EXT
  25 00 58 a1 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 68 91 00 54 e0 00      00:46:18.807  READ DMA EXT

Error 837 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 50 a9 00 54 e0 00      00:46:05.509  READ DMA EXT
  25 00 58 a1 00 54 e0 00      00:46:25.456  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 68 91 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 70 89 00 54 e0 00      00:46:18.807  READ DMA EXT

Error 836 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 58 a1 00 54 e0 00      00:46:05.509  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:05.493  READ DMA EXT
  25 00 68 91 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 70 89 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 78 81 00 54 e0 00      00:46:18.807  READ DMA EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%        32         -
# 2  Short offline       Completed without error       00%        31         -
# 3  Short offline       Completed without error       00%        31         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

SMART Disabled. Use option -s with argument 'on' to enable it.
smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
General SMART Values:
Offline data collection status:  (0x82)   Offline data collection activity
               was completed without error.
               Auto Offline Data Collection: Enabled.
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:        ( 430) seconds.
Offline data collection
capabilities:           (0x5b) 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.
               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:     ( 163) minutes.

smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Thu Jun 29 22:39:32 2006

Use smartctl -X to abort test.
smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%        32         -
# 2  Short offline       Aborted by host               60%        32         -
# 3  Short offline       Completed without error       00%        32         -
# 4  Short offline       Completed without error       00%        31         -
# 5  Short offline       Completed without error       00%        31         -

smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 840 (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 840 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 b9 00 54 e0 00      00:46:32.199  READ DMA EXT
  25 00 08 b1 00 54 e0 00      00:46:32.196  READ DMA EXT
  25 00 08 a9 00 54 e0 00      00:46:32.193  READ DMA EXT
  25 00 08 a1 00 54 e0 00      00:46:32.188  READ DMA EXT
  25 00 08 99 00 54 e0 00      00:46:32.188  READ DMA EXT

Error 839 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 40 b9 00 54 e0 00      00:46:27.675  READ DMA EXT
  25 00 48 b1 00 54 e0 00      00:46:25.456  READ DMA EXT
  25 00 50 a9 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 58 a1 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:18.807  READ DMA EXT

Error 838 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 48 b1 00 54 e0 00      00:46:27.675  READ DMA EXT
  25 00 50 a9 00 54 e0 00      00:46:25.456  READ DMA EXT
  25 00 58 a1 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 68 91 00 54 e0 00      00:46:18.807  READ DMA EXT

Error 837 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 50 a9 00 54 e0 00      00:46:05.509  READ DMA EXT
  25 00 58 a1 00 54 e0 00      00:46:25.456  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 68 91 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 70 89 00 54 e0 00      00:46:18.807  READ DMA EXT

Error 836 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 58 a1 00 54 e0 00      00:46:05.509  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:05.493  READ DMA EXT
  25 00 68 91 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 70 89 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 78 81 00 54 e0 00      00:46:18.807  READ DMA EXT

smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   120   099   006    Pre-fail  Always       -       237852909
  3 Spin_Up_Time            0x0003   093   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       125
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       849329
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       32
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       147
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       359
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   063   055   045    Old_age   Always       -       37 (Lifetime Min/Max 26/37)
194 Temperature_Celsius     0x0022   037   045   000    Old_age   Always       -       37 (0 21 0 0)
195 Hardware_ECC_Recovered  0x001a   080   067   000    Old_age   Always       -       208371120
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 TA_Increase_Count       0x0032   099   252   000    Old_age   Always       -       1



Anschließend habe ich daher noch einmal folgendes gemacht:
-Einspielen der FSC Firmware
-Rücksetzen auf Defaultzustand
-Formatierung der Platte
-Einspielen der neuesten NEXT Pakete

Anschließend liefen alle Anwendungen auch lighttpd.
Nach einem Neustart wieder das gleiche Problem, dass lighttpd wieder nicht gestartet wird und sich auch nicht starten lässt. Zusätzlich wurde diesmal auch mysql nicht gestartet.

Wenn ich das Poblem nicht lösen kann, muss ich mich wohl nach einem neuen NAS umsehen.
Eigentlich schade :(. Eigenartig ist jedoch, dass die Standardanwendungen von FSC nie betroffen sind.
Diese laufen immer ohne Pobleme. Verstehe ich auch nicht. :?:

Vielleicht noch eine abschließende Frage.
Nach jedem NEXT Paket wird ja ein Neustart durchgeführt.
Kann ich nicht mehrere Pakete ins Verzeichnis /mnt kopieren (telnet muss dafür natürlich schon vorhanden sein).
Pakete von /mnt/Share nach /mnt kopieren, diese mit tar auspacken und anschließend ein Neustart duchführen.
So könnte man sich evtl. nach jedem Paket ein Neustart sparen.

Gruss
drachen1000

User avatar
Brevheart
Posts: 461
Joined: Wed Feb 21, 2007 9:23
Product(s): Synology DS211j

Re: iSCSI Target

Postby Brevheart » Mon Jun 22, 2009 6:59

Hi drachen1000, du hast ne pn zu smartmontools!

Die mir bekannte schnellste installation von mehrereren Paketen ist die:
Erstelle ein neues Verzeichnis unter /mnt/Share mkdir NExtAddons (oder von Windows aus), kopiere dort deine Pakete rein die du installieren möchtest, dann mußt noch die Datei !install im Verzeichnis NExtAddons erstellt werden (touch !install) oder kopiere irgendeine Datei mit dem Namen !install in das gleiche Verzeichnis und mach ein reboot! Nach dem Neustart werden alle Pakete installiert die du vorher rein kopiert hast!

Gruß Brevheart

User avatar
lochness
Posts: 3224
Joined: Sat Feb 04, 2006 20:42
Product(s): Myrica TV P42-2H
AMC 570 SAT (3.2.419 + VZD2)
AMC 370 SAT (1.6.115+VZD2)
AMP 150 (1.03.28eu)
3 x AMS 150 (V2.00 + NExt V2.0.06)
SBLAN2 R1.0 (V2.00 + NExt V2.0.06)
SBLAN2 R1.1 (V2.00 + NExt V2.0.06)
Storagebird DUO 35-LR (V1.03)
SB-L V1 (80GB, NetHDD007-0802)
Celvin Q800 4x2TB
Celvin Q700 2x1TB
Celvin Q600 1x2TB
Location: Bad Lippspringe

Re: iSCSI Target

Postby lochness » Mon Jun 22, 2009 16:36

Drachen1000, es wäre schade, wenn Du deswegen Dein AMS abschaffen würdest. Wäre doch gut, wenn wir den Fehler finden würden. Kannst Du nicht versuchen, mal den lighttpd + php über webadmin zu stoppen, und schauen, ob der Fehler dann noch da ist? Wenn es ein Fehler im Stop-Vorgang ist, sollte das ja helfen.

drachen1000
Posts: 44
Joined: Mon Mar 03, 2008 20:33
Location: Lübeck

Re: iSCSI Target

Postby drachen1000 » Tue Jun 23, 2009 7:34

Hallo Brevheart, hallo lochness,
vielen Dank für die wertvollen Hinweise.

@brevheart
Ich habe noch einmal die Tests mit smartmontools durchgeführt. Bei mir treten aber offensichtlich Fehler auf. Die Ergebnisse sehen jedenfalls anders aus als bei Dir.

Code: Select all

smartctl -t short -d ata /dev/sda

smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Thu Jun 29 23:14:15 2006

Use smartctl -X to abort test.

smartctl -l error -d ata /dev/sda

smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 840 (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 840 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 b9 00 54 e0 00      00:46:32.199  READ DMA EXT
  25 00 08 b1 00 54 e0 00      00:46:32.196  READ DMA EXT
  25 00 08 a9 00 54 e0 00      00:46:32.193  READ DMA EXT
  25 00 08 a1 00 54 e0 00      00:46:32.188  READ DMA EXT
  25 00 08 99 00 54 e0 00      00:46:32.188  READ DMA EXT

Error 839 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 40 b9 00 54 e0 00      00:46:27.675  READ DMA EXT
  25 00 48 b1 00 54 e0 00      00:46:25.456  READ DMA EXT
  25 00 50 a9 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 58 a1 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:18.807  READ DMA EXT

Error 838 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 48 b1 00 54 e0 00      00:46:27.675  READ DMA EXT
  25 00 50 a9 00 54 e0 00      00:46:25.456  READ DMA EXT
  25 00 58 a1 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 68 91 00 54 e0 00      00:46:18.807  READ DMA EXT

Error 837 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 50 a9 00 54 e0 00      00:46:05.509  READ DMA EXT
  25 00 58 a1 00 54 e0 00      00:46:25.456  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 68 91 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 70 89 00 54 e0 00      00:46:18.807  READ DMA EXT

Error 836 occurred at disk power-on lifetime: 25 hours (1 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 be 00 54 e0  Error: UNC at LBA = 0x005400be = 5505214

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 58 a1 00 54 e0 00      00:46:05.509  READ DMA EXT
  25 00 60 99 00 54 e0 00      00:46:05.493  READ DMA EXT
  25 00 68 91 00 54 e0 00      00:46:23.245  READ DMA EXT
  25 00 70 89 00 54 e0 00      00:46:21.026  READ DMA EXT
  25 00 78 81 00 54 e0 00      00:46:18.807  READ DMA EXT


smartctl -l selftest -d ata /dev/sda


smartctl version 5.38 [powerpc-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%        34         -
# 2  Short offline       Completed without error       00%        34         -
# 3  Short offline       Completed without error       00%        32         -
# 4  Short offline       Completed without error       00%        32         -
# 5  Short offline       Aborted by host                      60%        32         -
# 6  Short offline       Completed without error       00%        32         -
# 7  Short offline       Completed without error       00%        31         -
# 8  Short offline       Completed without error       00%        31         -



Vielen Dank auch noch für den Hinweis, wie man mehrere Pakete gleichzeitig installieren kann. Wenn ich es richtig verstanden habe, kann die Datei !install leer sein.
Interessant wie ihr das gelöst habt.

@lochness
Ich würde mein sblan auch nur sehr ungern aufgeben wollen. Ich bekomme es jedoch einfach nicht hin, dass er stabil läuft. Nach diversen Neuaufsetzen immer noch die Probleme und keine Besserung in Sicht. Das führt irgendwann einfach dazu, das man aufgibt. Aber noch habe ich die Hoffnung noch nicht ganz aufgegeben. :)
Z.Zt. kann ich so jedenfalls nicht "produktiv" mit ihm arbeiten. Das Risiko z.B. Datenverlust ist mir einfach zu hoch.
Vielleicht noch zum lighttpd. Er startet erst gar nicht, so das ich ihn auch nicht über webadmin beenden kann.

Gruss
drachen1000

User avatar
Brevheart
Posts: 461
Joined: Wed Feb 21, 2007 9:23
Product(s): Synology DS211j

Re: iSCSI Target

Postby Brevheart » Tue Jun 23, 2009 22:46

Das sieht nicht so dolle aus mit der Festplatte! Hast du noch Garantie? Sonst würde ich die Festplatte nochmal extern mit Hersteller Tool checken! Und neue Festplatten sind ja heute nicht mehr so teuer :)

Gruß Brevheart

drachen1000
Posts: 44
Joined: Mon Mar 03, 2008 20:33
Location: Lübeck

Re: iSCSI Target

Postby drachen1000 » Wed Jun 24, 2009 17:16

Ich habe mir eine neue Festplatte gekauft, diese eingebaut und anschließend noch einmal smartmontools drüber laufen lassen.
Jetzt erhalte ich auch keine Fehlermeldung mehr. :)
lighttpd startet z.Zt. auch noch, dafür startet jedoch jetzt mysql nicht, weder über console noch über webadmin.
Dieses Verhalten ist doch nicht normal oder?

In der console erhalte ich folgende Meldungen:
amsadmin# ./mysql.sh status
./mysql.sh: not running.
amsadmin# ./mysql.sh restart
./mysql.sh: mysqld stop.
./mysql.sh: mysqld started.
amsadmin# ./mysql.sh status
./mysql.sh: not running.

Es ist zum Verzweifeln. Ich glaube mein Gerät hat irgendeine Macke.
Habt ihr dazu noch weitere Ideen.
Ich glaube, ich werde jetzt erst einmal das schöne Wetter genießen.
Noch eine letzte Frage:
Welches Skript übernimmt eigentlich die Abfrage des Ordners "NExtAddons" und deren Pakete !install?
Ist das Paket NEXT_base hierfür zuständig?

drachen1000

User avatar
lochness
Posts: 3224
Joined: Sat Feb 04, 2006 20:42
Product(s): Myrica TV P42-2H
AMC 570 SAT (3.2.419 + VZD2)
AMC 370 SAT (1.6.115+VZD2)
AMP 150 (1.03.28eu)
3 x AMS 150 (V2.00 + NExt V2.0.06)
SBLAN2 R1.0 (V2.00 + NExt V2.0.06)
SBLAN2 R1.1 (V2.00 + NExt V2.0.06)
Storagebird DUO 35-LR (V1.03)
SB-L V1 (80GB, NetHDD007-0802)
Celvin Q800 4x2TB
Celvin Q700 2x1TB
Celvin Q600 1x2TB
Location: Bad Lippspringe

Re: iSCSI Target

Postby lochness » Wed Jun 24, 2009 18:18

Drachen1000, ich werde Dir die technischen Fragen im Detail beantworten, wenn ich aus dem Urlaub wieder da bin (ca. ab Sonntag). Vielleicht machen wir dann noch mal eine Chat-Session zur Diagnose?

drachen1000
Posts: 44
Joined: Mon Mar 03, 2008 20:33
Location: Lübeck

Re: iSCSI Target

Postby drachen1000 » Wed Jun 24, 2009 19:48

Hallo lochness,

vielen Dank für Dein Angebot. Ich komme darauf gerne zurück, wenn Du Deinen Urlaub beendet hast.
Du solltest jetzt aber erst einmal Deinen Urlaub genießen und Dich etwas von uns hier erholen :D !
So etwas hat auf jedenfall Priorität!!

Gruss
drachen1000


Return to “Ideas, Wishes, Feedback”

Who is online

Users browsing this forum: No registered users and 2 guests