Flashing cursor when rebooting / Blackscreen

    • OMV 1.0
    • Flashing cursor when rebooting / Blackscreen

      Hello OMV-Community!
      I have a problem with my NAS. When I reboot over GUI/CLI, the NAS will get stuck most of the time (after the reboot), when GRUB should show up and pick the default kernel. The only thing I get is the somewhat known flashing cursor and nothing else. Sometimes I also get a dark screen without output to the monitor, directly after it halted the server and stopped all services - no HDD activity (only spinning) and the server LED wont turn off and it doesnt react anymore (directly after shutting down everything). It just won't do anything, no activity on the drives. In this case, I have to hard reset the server. Sometimes the reboots work fine multiple times in a row. Shutdown + WoL works fine every time.

      Specs:
      geizhals.de/?cat=WL-490313
      + Apacer 1,8" SATA1 SSD 32GB as system drive -> mouser.de/ProductDetail/Apacer…a%252bvpz4b%2FxsA6w%3D%3D / -> digchip.com/datasheets/parts/d…AP-SAFD18BQA032GS-EML.php
      + 4GB Corsair SODIMM DDR3 -> corsair.com/en-us/vengeance-4g…ade-kit-cmsx4gx3m1a1600c9

      Installed UEFI is 1.40 (newest version)
      Legacy Mode is ON
      AHCI Mode is ON
      (any HDD/SSD power management options are disabled, also in OMV itself)
      C7 State
      Suspend to RAM OFF
      Bootdevice #1 is the SSD
      Bootdevice #2 is DISABLED
      Some other devices are also disabled (HDMI-Audio/Serial Ports etc.)

      System version: 1.6

      Currently used kernel: Backports 3.16-0.bpo.2-amd64
      (Same problems occur under the 3.2.0-4-amd64 kernel)

      Currently installed Backupsystems over the Backup Plugin: Clonezilla and GParted Live (GRUB entries set)

      Support Info: pastebin.com/pyuPdw8r

      Thank you in advance!
      OpenMediaVault 1.12 on Debian Wheezy 7.8 64bit | 3.16 Backport Kernel | OMV-Extras.org 1.10
      ASRock Q1900-ITX | 1x4GB Corsair Vengeance SODIMM DDR3 | 1xWD Red 3TB | 1xApacer 1,8" SATA1 SSD 32GB as system drive | be quiet! Pure Power L8 350W | SilverStone Milo ML04 Black

      The post was edited 3 times, last by Nyctophilia ().

    • Had this problem since the very beginning - Yes it is new. You know my problem already, I'm "ImHereForTheLulz" from the #openmediavault IRC-Chan :P
      OpenMediaVault 1.12 on Debian Wheezy 7.8 64bit | 3.16 Backport Kernel | OMV-Extras.org 1.10
      ASRock Q1900-ITX | 1x4GB Corsair Vengeance SODIMM DDR3 | 1xWD Red 3TB | 1xApacer 1,8" SATA1 SSD 32GB as system drive | be quiet! Pure Power L8 350W | SilverStone Milo ML04 Black
    • Good idea, but thats not possible for the moment - I would have to backup the whole OS, write ubuntu or another distro to it and test it out - my stepfather would not be pleased, if he couldnt access his files anymore. lol
      OpenMediaVault 1.12 on Debian Wheezy 7.8 64bit | 3.16 Backport Kernel | OMV-Extras.org 1.10
      ASRock Q1900-ITX | 1x4GB Corsair Vengeance SODIMM DDR3 | 1xWD Red 3TB | 1xApacer 1,8" SATA1 SSD 32GB as system drive | be quiet! Pure Power L8 350W | SilverStone Milo ML04 Black
    • I have seen such behaviour (allthough not reproduceable) on a system without UEFI too. I think the Mainboard mixes up something with the boot order or so...

      Greetigs
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Do you mean how old it is (usage time) or when it was released?
      See the links in the first post for the specs - I dont really know when it was released actually, but I got it from a friend and he said it was in a industrial tablet with XP - and the tablet is now about 6 years old. It was used in a company somewhere and he got it from eBay, but didnt use it. (I use it for ca. 2 weeks)

      I can post you some smartlogs if you want - Something is also weird with the SSD. I get SMART erros sometimes when i have to force shutdown the system (reboot fail for example) but it always resets back to 0 when the next error comes. Examples:

      This email was generated by the smartd daemon running on:

      host name: NAS
      DNS domain: local
      NIS domain: (none)

      The following warning/error was logged by the smartd daemon:

      Device: /dev/disk/by-id/wwn-0x50014ee604ffa8c2 [SAT], ATA error count increased from 0 to 2

      For details see host's SYSLOG.

      You can also use the smartctl utility for further investigation.
      Another email message will be sent in 24 hours if the problem persists.

      This email was generated by the smartd daemon running on:

      host name: NAS
      DNS domain: local
      NIS domain: (none)

      The following warning/error was logged by the smartd daemon:

      Device: /dev/disk/by-id/scsi-SATA_32G_SATA_Flash_C00910300113X697001F [SAT], ATA error count increased from 0 to 33

      For details see host's SYSLOG.

      You can also use the smartctl utility for further investigation.
      The original email about this issue was sent at Sun Dec 7 12:39:44 2014 CET
      Another email message will be sent in 24 hours if the problem persists.

      This email was generated by the smartd daemon running on:

      host name: NAS
      DNS domain: local
      NIS domain: (none)

      The following warning/error was logged by the smartd daemon:

      Device: /dev/disk/by-id/scsi-SATA_32G_SATA_Flash_C00910300113X697001F [SAT], Self-Test Log error count increased from 0 to 21

      For details see host's SYSLOG.

      You can also use the smartctl utility for further investigation.
      The original email about this issue was sent at Sun Dec 7 19:41:48 2014 CET
      Another email message will be sent in 24 hours if the problem persists.

      This email was generated by the smartd daemon running on:

      host name: NAS
      DNS domain: local
      NIS domain: (none)

      The following warning/error was logged by the smartd daemon:

      Device: /dev/disk/by-id/scsi-SATA_32G_SATA_Flash_C00910300113X697001F [SAT], ATA error count increased from 0 to 1246

      For details see host's SYSLOG.

      You can also use the smartctl utility for further investigation.
      The original email about this issue was sent at Sun Dec 7 12:39:44 2014 CET
      Another email message will be sent in 24 hours if the problem persists.

      This email was generated by the smartd daemon running on:

      host name: NAS
      DNS domain: local
      NIS domain: (none)

      The following warning/error was logged by the smartd daemon:

      Device: /dev/disk/by-id/scsi-SATA_32G_SATA_Flash_C00910300113X697001F [SAT], Self-Test Log error count increased from 0 to 21

      For details see host's SYSLOG.

      You can also use the smartctl utility for further investigation.
      The original email about this issue was sent at Sun Dec 7 19:41:48 2014 CET
      Another email message will be sent in 24 hours if the problem persists.

      This email was generated by the smartd daemon running on:

      host name: NAS
      DNS domain: local
      NIS domain: (none)

      The following warning/error was logged by the smartd daemon:

      Device: /dev/disk/by-id/scsi-SATA_32G_SATA_Flash_C00910300113X697001F [SAT], ATA error count increased from 0 to 18456

      For details see host's SYSLOG.

      You can also use the smartctl utility for further investigation.
      The original email about this issue was sent at Sun Dec 7 12:39:44 2014 CET
      Another email message will be sent in 24 hours if the problem persists.

      [IMG:http://puu.sh/dzIyM/0683af9d55.png]
      smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.16-0.bpo.2-amd64] (local build)
      Copyright (C) 2002-11 by Bruce Allen, smartmontools.sourceforge.net

      === START OF INFORMATION SECTION ===
      Device Model: 32G SATA Flash Drive
      Serial Number: C00910300113X697001F
      Firmware Version: SFDB003E
      User Capacity: 32,296,140,800 bytes [32.2 GB]
      Sector Size: 512 bytes logical/physical
      Device is: Not in smartctl database [for details use: -P showall]
      ATA Version is: 7
      ATA Standard is: Exact ATA specification draft version not indicated
      Local Time is: Thu Dec 18 15:07:06 2014 CET
      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.
      Total time to complete Offline
      data collection: ( 0) seconds.
      Offline data collection
      capabilities: (0x00) Offline data collection not supported.
      SMART capabilities: (0x0003) Saves SMART data before entering
      power-saving mode.
      Supports SMART auto save timer.
      Error logging capability: (0x00) Error logging NOT supported.
      No General Purpose Logging support.

      SMART Attributes Data Structure revision number: 1280
      (Edit: Inserted this screenshot, because the layout was not correctly shown anymore when posting it here)
      [IMG:http://puu.sh/dzIVB/83279b8740.png]

      ATA_READ_LOG_EXT (addr=0x00:0x00, page=0, n=1) failed: scsi error aborted command
      Read GP Log Directory failed.

      SMART Log Directory Version 16
      SMART Log at address 0x00 has 1 sectors [Log Directory]
      SMART Log at address 0x01 has 12 sectors [Summary SMART error log]
      SMART Log at address 0x07 has 9 sectors [Extended self-test log]
      SMART Log at address 0x0d has 194 sectors [LPS Mis-alignment log]
      SMART Log at address 0x13 has 229 sectors [Reserved for Serial ATA]
      SMART Log at address 0x19 has 232 sectors [Reserved]
      SMART Log at address 0x1f has 233 sectors [Reserved]
      SMART Log at address 0x25 has 234 sectors [Reserved]
      SMART Log at address 0x2b has 235 sectors [Reserved]

      SMART Extended Comprehensive Error Log (GP Log 0x03) not supported
      SMART Error Log Version: 16
      No Errors Logged

      SMART Extended Self-test Log (GP Log 0x07) not supported
      SMART Self-test Log not supported
      Device does not support Selective Self Tests/Logging
      Warning: device does not support SCT Commands
      SATA Phy Event Counters (GP Log 0x11) not supported


      1 more information: The SSD (SATA1) is currently at a SATA3 port but I think this doesnt make any difference? But I think I will try a native SATA2 port soon - The SATA3 ports are from a ASMedia Chipset. I will also try it with ubuntu/kubuntu soon.

      "- 2 x SATA2 3.0 Gb/s Connectors, support NCQ, AHCI and Hot Plug
      - 2 x SATA3 6.0 Gb/s Connectors by ASMedia ASM1061, support NCQ, AHCI and Hot Plug"

      Thanks for your help.
      OpenMediaVault 1.12 on Debian Wheezy 7.8 64bit | 3.16 Backport Kernel | OMV-Extras.org 1.10
      ASRock Q1900-ITX | 1x4GB Corsair Vengeance SODIMM DDR3 | 1xWD Red 3TB | 1xApacer 1,8" SATA1 SSD 32GB as system drive | be quiet! Pure Power L8 350W | SilverStone Milo ML04 Black
    • Yeah, i have plenty of hardware here - Will try a 2,5" SATA(1?) HDD drive soon.

      Edit: I think the SSD is not defect as I said and shown, the SMART errors reset always to 0, it is probably a compatibility issue with UEFI.
      OpenMediaVault 1.12 on Debian Wheezy 7.8 64bit | 3.16 Backport Kernel | OMV-Extras.org 1.10
      ASRock Q1900-ITX | 1x4GB Corsair Vengeance SODIMM DDR3 | 1xWD Red 3TB | 1xApacer 1,8" SATA1 SSD 32GB as system drive | be quiet! Pure Power L8 350W | SilverStone Milo ML04 Black
    • Update: Cloned the installation to a 80GB 2,5" HDD with clonezilla. The problem remains. Blinking cursor when OMV should reboot...
      [IMG:http://puu.sh/dLBzV/5ffc0f4c32.png]

      Source Code

      1. /dev/sda
      2. FUJITSU MHV2080BH
      3. 892C


      [IMG:http://puu.sh/dLBla/b8a0cf9f92.png]
      [IMG:http://puu.sh/dLBnS/6a04d45ea6.png]

      Source Code

      1. smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.16-0.bpo.2-amd64] (local build)
      2. Copyright (C) 2002-11 by Bruce Allen, [url]http://smartmontools.sourceforge.net[/url]
      3. === START OF INFORMATION SECTION ===
      4. Model Family: Fujitsu MHV
      5. Device Model: FUJITSU MHV2080BH
      6. Serial Number: NW13T682ET5T
      7. Firmware Version: 892C
      8. User Capacity: 80,026,361,856 bytes [80.0 GB]
      9. Sector Size: 512 bytes logical/physical
      10. Device is: In smartctl database [for details use: -P show]
      11. ATA Version is: 7
      12. ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a
      13. Local Time is: Sat Dec 27 21:24:40 2014 CET
      14. SMART support is: Available - device has SMART capability.
      15. SMART support is: Enabled
      16. === START OF READ SMART DATA SECTION ===
      17. SMART overall-health self-assessment test result: PASSED
      18. General SMART Values:
      19. Offline data collection status: (0x80) Offline data collection activity
      20. was never started.
      21. Auto Offline Data Collection: Enabled.
      22. Self-test execution status: ( 0) The previous self-test routine completed
      23. without error or no self-test has ever
      24. been run.
      25. Total time to complete Offline
      26. data collection: ( 471) seconds.
      27. Offline data collection
      28. capabilities: (0x5b) SMART execute Offline immediate.
      29. Auto Offline data collection on/off support.
      30. Suspend Offline collection upon new
      31. command.
      32. Offline surface scan supported.
      33. Self-test supported.
      34. No Conveyance Self-test supported.
      35. Selective Self-test supported.
      36. SMART capabilities: (0x0003) Saves SMART data before entering
      37. power-saving mode.
      38. Supports SMART auto save timer.
      39. Error logging capability: (0x01) Error logging supported.
      40. General Purpose Logging supported.
      41. Short self-test routine
      42. recommended polling time: ( 2) minutes.
      43. Extended self-test routine
      44. recommended polling time: ( 55) minutes.
      45. SCT capabilities: (0x003d) SCT Status supported.
      46. SCT Error Recovery Control supported.
      47. SCT Feature Control supported.
      48. SCT Data Table supported.
      49. [url]http://puu.sh/dLBqn/58a61f7014.png[/url]
      50. SMART Log Directory Version 1 [multi-sector log support]
      51. GP/S Log at address 0x00 has 1 sectors [Log Directory]
      52. GP/S Log at address 0x01 has 1 sectors [Summary SMART error log]
      53. GP/S Log at address 0x02 has 51 sectors [Comprehensive SMART error log]
      54. GP/S Log at address 0x03 has 64 sectors [Ext. Comprehensive SMART error log]
      55. GP/S Log at address 0x06 has 1 sectors [SMART self-test log]
      56. GP/S Log at address 0x07 has 2 sectors [Extended self-test log]
      57. GP/S Log at address 0x09 has 1 sectors [Selective self-test log]
      58. GP/S Log at address 0x11 has 1 sectors [SATA Phy Event Counters]
      59. GP/S Log at address 0x80 has 16 sectors [Host vendor specific log]
      60. GP/S Log at address 0x81 has 16 sectors [Host vendor specific log]
      61. GP/S Log at address 0x82 has 16 sectors [Host vendor specific log]
      62. GP/S Log at address 0x83 has 16 sectors [Host vendor specific log]
      63. GP/S Log at address 0x84 has 16 sectors [Host vendor specific log]
      64. GP/S Log at address 0x85 has 16 sectors [Host vendor specific log]
      65. GP/S Log at address 0x86 has 16 sectors [Host vendor specific log]
      66. GP/S Log at address 0x87 has 16 sectors [Host vendor specific log]
      67. GP/S Log at address 0x88 has 16 sectors [Host vendor specific log]
      68. GP/S Log at address 0x89 has 16 sectors [Host vendor specific log]
      69. GP/S Log at address 0x8a has 16 sectors [Host vendor specific log]
      70. GP/S Log at address 0x8b has 16 sectors [Host vendor specific log]
      71. GP/S Log at address 0x8c has 16 sectors [Host vendor specific log]
      72. GP/S Log at address 0x8d has 16 sectors [Host vendor specific log]
      73. GP/S Log at address 0x8e has 16 sectors [Host vendor specific log]
      74. GP/S Log at address 0x8f has 16 sectors [Host vendor specific log]
      75. GP/S Log at address 0x90 has 16 sectors [Host vendor specific log]
      76. GP/S Log at address 0x91 has 16 sectors [Host vendor specific log]
      77. GP/S Log at address 0x92 has 16 sectors [Host vendor specific log]
      78. GP/S Log at address 0x93 has 16 sectors [Host vendor specific log]
      79. GP/S Log at address 0x94 has 16 sectors [Host vendor specific log]
      80. GP/S Log at address 0x95 has 16 sectors [Host vendor specific log]
      81. GP/S Log at address 0x96 has 16 sectors [Host vendor specific log]
      82. GP/S Log at address 0x97 has 16 sectors [Host vendor specific log]
      83. GP/S Log at address 0x98 has 16 sectors [Host vendor specific log]
      84. GP/S Log at address 0x99 has 16 sectors [Host vendor specific log]
      85. GP/S Log at address 0x9a has 16 sectors [Host vendor specific log]
      86. GP/S Log at address 0x9b has 16 sectors [Host vendor specific log]
      87. GP/S Log at address 0x9c has 16 sectors [Host vendor specific log]
      88. GP/S Log at address 0x9d has 16 sectors [Host vendor specific log]
      89. GP/S Log at address 0x9e has 16 sectors [Host vendor specific log]
      90. GP/S Log at address 0x9f has 16 sectors [Host vendor specific log]
      91. GP/S Log at address 0xa1 has 1 sectors [Device vendor specific log]
      92. SMART Extended Comprehensive Error Log Version: 1 (64 sectors)
      93. Device Error Count: 2
      94. CR = Command Register
      95. FEATR = Features Register
      96. COUNT = Count (was: Sector Count) Register
      97. LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
      98. LH = LBA High (was: Cylinder High) Register ] LBA
      99. LM = LBA Mid (was: Cylinder Low) Register ] Register
      100. LL = LBA Low (was: Sector Number) Register ]
      101. DV = Device (was: Device/Head) Register
      102. DC = Device Control Register
      103. ER = Error register
      104. ST = Status register
      105. Powered_Up_Time is measured from power on, and printed as
      106. DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
      107. SS=sec, and sss=millisec. It "wraps" after 49.710 days.
      108. Error 2 [1] occurred at disk power-on lifetime: 5327 hours (221 days + 23 hours)
      109. When the command that caused the error occurred, the device was active or idle.
      110. After command completion occurred, registers were:
      111. ER -- ST COUNT LBA_48 LH LM LL DV DC
      112. -- -- -- == -- == == == -- -- -- -- --
      113. 84 -- 51 00 01 00 00 00 35 3a 1f e0 00 Error: ICRC, ABRT at LBA = 0x00353a1f = 3488287
      Display All

      OpenMediaVault 1.12 on Debian Wheezy 7.8 64bit | 3.16 Backport Kernel | OMV-Extras.org 1.10
      ASRock Q1900-ITX | 1x4GB Corsair Vengeance SODIMM DDR3 | 1xWD Red 3TB | 1xApacer 1,8" SATA1 SSD 32GB as system drive | be quiet! Pure Power L8 350W | SilverStone Milo ML04 Black

      The post was edited 4 times, last by Nyctophilia ().

    • Brainfuck Source Code

      1. Commands leading to the command that caused the error were:
      2. CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
      3. -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
      4. ca 00 00 00 08 00 00 00 35 3a 18 e0 00 00:01:04.329 WRITE DMA
      5. ca 00 00 00 08 00 00 00 35 3a 10 e0 00 00:01:04.329 WRITE DMA
      6. ca 00 00 00 08 00 00 00 35 3a 08 e0 00 00:01:04.328 WRITE DMA
      7. ca 00 00 00 08 00 00 00 35 39 f8 e0 00 00:01:04.328 WRITE DMA
      8. ca 00 00 00 08 00 00 00 35 39 f0 e0 00 00:01:04.328 WRITE DMA
      9. Error 1 [0] occurred at disk power-on lifetime: 4124 hours (171 days + 20 hours)
      10. When the command that caused the error occurred, the device was active or idle.
      11. After command completion occurred, registers were:
      12. ER -- ST COUNT LBA_48 LH LM LL DV DC
      13. -- -- -- == -- == == == -- -- -- -- --
      14. 84 -- 51 00 08 00 00 05 c2 88 18 40 00 Error: ICRC, ABRT 8 sectors at LBA = 0x05c28818 = 96634904
      15. Commands leading to the command that caused the error were:
      16. CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
      17. -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
      18. 35 00 ff 00 08 00 00 05 c2 88 18 40 00 00:22:23.649 WRITE DMA EXT
      19. 00 00 ff 00 01 00 00 00 00 00 01 00 04 00:22:15.883 NOP [Reserved subcommand]
      20. 00 00 ff 00 01 00 00 00 00 00 01 00 ff 00:22:15.873 NOP [Reserved subcommand]
      21. 35 00 ff 00 08 00 00 05 c2 88 18 40 00 00:21:50.120 WRITE DMA EXT
      22. 42 ff 00 00 01 00 00 00 00 00 01 40 00 00:21:50.042 READ VERIFY SECTOR(S) EXT
      23. SMART Extended Self-test Log Version: 1 (2 sectors)
      24. Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
      25. # 1 Short offline Completed without error 00% 2942 -
      26. # 2 Extended offline Completed without error 00% 1264 -
      27. # 3 Short offline Completed without error 00% 1263 -
      28. # 4 Short offline Aborted by host 90% 1245 -
      29. SMART Selective self-test log data structure revision number 1
      30. SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
      31. 1 0 0 Not_testing
      32. 2 0 0 Not_testing
      33. 3 0 0 Not_testing
      34. 4 0 0 Not_testing
      35. 5 0 0 Not_testing
      36. Selective self-test flags (0x0):
      37. After scanning selected spans, do NOT read-scan remainder of disk.
      38. If Selective self-test is pending on power-up, resume after 0 minute delay.
      39. SCT Status Version: 2
      40. SCT Version (vendor specific): 0 (0x0000)
      41. SCT Support Level: 1
      42. Device State: Active (0)
      43. Current Temperature: 29 Celsius
      44. Power Cycle Max Temperature: 30 Celsius
      45. Lifetime Max Temperature: 62 Celsius
      46. SCT Temperature History Version: 2
      47. Temperature Sampling Period: 1 minute
      48. Temperature Logging Interval: 1 minute
      49. Min/Max recommended Temperature: 5/60 Celsius
      50. Min/Max Temperature Limit: -40/65 Celsius
      51. Temperature History Size (Index): 128 (28)
      52. Index Estimated Time Temperature Celsius
      53. 29 2014-12-27 19:17 35 ****************
      54. 30 2014-12-27 19:18 35 ****************
      55. 31 2014-12-27 19:19 35 ****************
      56. 32 2014-12-27 19:20 34 ***************
      57. 33 2014-12-27 19:21 33 **************
      58. 34 2014-12-27 19:22 33 **************
      59. 35 2014-12-27 19:23 ? -
      60. 36 2014-12-27 19:24 32 *************
      61. 37 2014-12-27 19:25 31 ************
      62. ... ..( 2 skipped). .. ************
      63. 40 2014-12-27 19:28 31 ************
      64. 41 2014-12-27 19:29 32 *************
      65. 42 2014-12-27 19:30 33 **************
      66. ... ..( 2 skipped). .. **************
      67. 45 2014-12-27 19:33 33 **************
      68. 46 2014-12-27 19:34 34 ***************
      69. ... ..( 2 skipped). .. ***************
      70. 49 2014-12-27 19:37 34 ***************
      71. 50 2014-12-27 19:38 35 ****************
      72. ... ..( 50 skipped). .. ****************
      73. 101 2014-12-27 20:29 35 ****************
      74. 102 2014-12-27 20:30 ? -
      75. 103 2014-12-27 20:31 35 ****************
      76. 104 2014-12-27 20:32 ? -
      77. 105 2014-12-27 20:33 25 ******
      78. 106 2014-12-27 20:34 ? -
      79. 107 2014-12-27 20:35 30 ***********
      80. 108 2014-12-27 20:36 ? -
      81. 109 2014-12-27 20:37 30 ***********
      82. 110 2014-12-27 20:38 ? -
      83. 111 2014-12-27 20:39 27 ********
      84. 112 2014-12-27 20:40 28 *********
      85. 113 2014-12-27 20:41 ? -
      86. 114 2014-12-27 20:42 28 *********
      87. 115 2014-12-27 20:43 28 *********
      88. 116 2014-12-27 20:44 ? -
      89. 117 2014-12-27 20:45 30 ***********
      90. 118 2014-12-27 20:46 ? -
      91. 119 2014-12-27 20:47 22 ***
      92. 120 2014-12-27 20:48 ? -
      93. 121 2014-12-27 20:49 25 ******
      94. 122 2014-12-27 20:50 ? -
      95. 123 2014-12-27 20:51 25 ******
      96. 124 2014-12-27 20:52 ? -
      97. 125 2014-12-27 20:53 26 *******
      98. 126 2014-12-27 20:54 ? -
      99. 127 2014-12-27 20:55 27 ********
      100. 0 2014-12-27 20:56 28 *********
      101. 1 2014-12-27 20:57 ? -
      102. 2 2014-12-27 20:58 27 ********
      103. 3 2014-12-27 20:59 27 ********
      104. 4 2014-12-27 21:00 27 ********
      105. 5 2014-12-27 21:01 28 *********
      106. ... ..( 5 skipped). .. *********
      107. 11 2014-12-27 21:07 28 *********
      108. 12 2014-12-27 21:08 29 **********
      109. 13 2014-12-27 21:09 29 **********
      110. 14 2014-12-27 21:10 29 **********
      111. 15 2014-12-27 21:11 ? -
      112. 16 2014-12-27 21:12 29 **********
      113. 17 2014-12-27 21:13 29 **********
      114. 18 2014-12-27 21:14 29 **********
      115. 19 2014-12-27 21:15 ? -
      116. 20 2014-12-27 21:16 29 **********
      117. 21 2014-12-27 21:17 29 **********
      118. 22 2014-12-27 21:18 29 **********
      119. 23 2014-12-27 21:19 30 ***********
      120. 24 2014-12-27 21:20 ? -
      121. 25 2014-12-27 21:21 29 **********
      122. 26 2014-12-27 21:22 30 ***********
      123. 27 2014-12-27 21:23 29 **********
      124. 28 2014-12-27 21:24 29 **********
      125. SCT Error Recovery Control:
      126. Read: Disabled
      127. Write: Disabled
      128. SATA Phy Event Counters (GP Log 0x11)
      129. ID Size Value Description
      130. 0x0001 4 0 Command failed due to ICRC error
      131. 0x0002 4 0 R_ERR response for data FIS
      132. 0x0003 4 0 R_ERR response for device-to-host data FIS
      133. 0x0004 4 0 R_ERR response for host-to-device data FIS
      134. 0x0005 4 0 R_ERR response for non-data FIS
      135. 0x0006 4 0 R_ERR response for device-to-host non-data FIS
      136. 0x0008 4 0 Device-to-host non-data FIS retries
      137. 0x0009 4 0 Transition from drive PhyRdy to drive PhyNRdy
      138. 0x000a 4 0 Device-to-host register FISes sent due to a COMRESET
      139. 0x000b 4 0 CRC errors within host-to-device FIS
      140. 0x000d 4 0 Non-CRC errors within host-to-device FIS
      141. 0x000f 4 0 R_ERR response for host-to-device data FIS, CRC
      142. 0x0010 4 0 R_ERR response for host-to-device data FIS, non-CRC
      Display All

      OpenMediaVault 1.12 on Debian Wheezy 7.8 64bit | 3.16 Backport Kernel | OMV-Extras.org 1.10
      ASRock Q1900-ITX | 1x4GB Corsair Vengeance SODIMM DDR3 | 1xWD Red 3TB | 1xApacer 1,8" SATA1 SSD 32GB as system drive | be quiet! Pure Power L8 350W | SilverStone Milo ML04 Black

      The post was edited 4 times, last by Nyctophilia ().

    • Whats the difference between code tags and quote tags? The latter fill up my mobile screen and make me scroll en masse...

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • -Tried a fresh OMV install to the 2,5" HDD
      -Changed a few settings in the UEFI and retried one by one

      Same problem persists.

      Next step: Installing Ubuntu 64bit
      OpenMediaVault 1.12 on Debian Wheezy 7.8 64bit | 3.16 Backport Kernel | OMV-Extras.org 1.10
      ASRock Q1900-ITX | 1x4GB Corsair Vengeance SODIMM DDR3 | 1xWD Red 3TB | 1xApacer 1,8" SATA1 SSD 32GB as system drive | be quiet! Pure Power L8 350W | SilverStone Milo ML04 Black

      The post was edited 1 time, last by Nyctophilia ().

    • ubuntu-14.04.1-desktop-amd64 reboots work fine with the standard installation...
      Then it must be a debian or GRUB related problem. Any ideas?
      OpenMediaVault 1.12 on Debian Wheezy 7.8 64bit | 3.16 Backport Kernel | OMV-Extras.org 1.10
      ASRock Q1900-ITX | 1x4GB Corsair Vengeance SODIMM DDR3 | 1xWD Red 3TB | 1xApacer 1,8" SATA1 SSD 32GB as system drive | be quiet! Pure Power L8 350W | SilverStone Milo ML04 Black

      The post was edited 1 time, last by Nyctophilia ().