Error#0 after upgrade to stoneburner

  • After upgrade I have had to reset admin password: both root and admin passwords failed, and I could only login as user with no admin permissions.


    With the new admin password I get the following error:


    Error #0:
    exception 'Exception' with message 'Failed to open file 'js/omv/form/field/CertificateComboBox.js'' in /usr/share/php/openmediavault/htmlpage.inc:46
    Stack trace:
    #0 /usr/share/php/openmediavault/htmlpage.inc(72): OMVHtmlPageAbstract->scanFiles('js/omv/form/fie...', Array)
    #1 /usr/share/php/openmediavault/htmlpage.inc(91): OMVHtmlPageAbstract->scanFiles('js/omv/module/a...', Array)
    #2 /usr/share/php/openmediavault/htmlpage.inc(96): OMVHtmlPageAbstract->scanDir('js/omv/module/a...', Array, true)
    #3 /usr/share/php/openmediavault/htmlpage.inc(96): OMVHtmlPageAbstract->scanDir('js/omv/module/a...', Array, true)
    #4 /usr/share/php/openmediavault/htmlpage.inc(277): OMVHtmlPageAbstract->scanDir('js/omv/module/a...', Array, true)
    #5 /usr/share/php/openmediavault/htmlpage.inc(173): OMVControlPanel->getJavascriptIncludes()
    #6 /var/www/openmediavault/index.php(36): OMVHtmlPageAbstract->render()
    #7 {main}


    Any help appreciated.


    Bogo

  • An NAS server: disk layout as below. OMV (rootfs) is installed on 60Gb SSD drive.


    Filesystem Size Used Avail Use% Mounted on
    rootfs 57G 1.4G 53G 3% /
    udev 10M 0 10M 0% /dev
    tmpfs 744M 324K 744M 1% /run
    /dev/disk/by-uuid/3a26cce9-4598-4000-a921-1cde5ba78682 57G 1.4G 53G 3% /
    tmpfs 5.0M 0 5.0M 0% /run/lock
    tmpfs 2.0G 0 2.0G 0% /run/shm
    /dev/md0 3.6T 385G 3.3T 11% /media/6be1ea13-02dc-454f-854a-7ea93816cf1b
    /dev/md0 3.6T 385G 3.3T 11% /export/Images
    /dev/md0 3.6T 385G 3.3T 11% /export/Pictures
    /dev/md0 3.6T 385G 3.3T 11% /export/Music
    /dev/md0 3.6T 385G 3.3T 11% /export/Webs
    /dev/md0 3.6T 385G 3.3T 11% /export/bourbon_backup
    /dev/md0 3.6T 385G 3.3T 11% /export/alba_backup
    tmpfs 3.7G 0 3.7G 0% /tmp
    root@keruru:/#


    TIA

  • SSD = Adata Premier Pro Series SP900 64Gb 2.5" SATA 6Gb/s installed mid-January 2015


    Reinstalled as suggested but symptoms and Error Code exactly the same, even after resetting passwords via omv-firstaid.


    Can still log on as before as unprivileged user.


    TIA

  • Following is smart reading from the SSD. Doesn't seem to have wear level implemented, but has passed overall test.
    Should I do something more specific with smartctl?


    HTH


    root@keruru:/etc# smartctl -a /dev/sda1
    smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build)
    Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net


    === START OF INFORMATION SECTION ===
    Device Model: ADATA SP900
    Serial Number: 7E4320009671
    LU WWN Device Id: 5 707c18 00007fd20
    Firmware Version: 5.6.0
    User Capacity: 64,023,257,088 bytes [64.0 GB]
    Sector Size: 512 bytes logical/physical
    Device is: Not in smartctl database [for details use: -P showall]
    ATA Version is: 8
    ATA Standard is: ACS-2 revision 3
    Local Time is: Fri Jan 1 16:49:02 2016 NZDT
    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: (0x02) Offline data collection activity
    was completed without error.
    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: ( 0) seconds.
    Offline data collection
    capabilities: (0x7d) SMART execute Offline immediate.
    No Auto Offline data collection support.
    Abort Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    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: ( 48) minutes.
    Conveyance self-test routine
    recommended polling time: ( 2) minutes.
    SCT capabilities: (0x0025) SCT Status supported.
    SCT Data Table supported.


    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 0x0032 120 120 050 Old_age Always - 8589934592
    5 Reallocated_Sector_Ct 0x0033 097 097 003 Pre-fail Always - 0
    9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 224180112990025
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 50
    171 Unknown_Attribute 0x000a 100 100 000 Old_age Always - 0
    172 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
    174 Unknown_Attribute 0x0030 000 000 000 Old_age Offline - 40
    177 Wear_Leveling_Count 0x0000 000 000 000 Old_age Offline - 99
    181 Program_Fail_Cnt_Total 0x000a 100 100 000 Old_age Always - 0
    182 Erase_Fail_Count_Total 0x0032 100 100 000 Old_age Always - 0
    187 Reported_Uncorrect 0x0012 100 100 000 Old_age Always - 0
    194 Temperature_Celsius 0x0022 032 039 000 Old_age Always - 32 (Min/Max 16/39)
    195 Hardware_ECC_Recovered 0x001c 120 120 000 Old_age Offline - 8589934592
    196 Reallocated_Event_Count 0x0033 097 097 003 Pre-fail Always - 0
    201 Soft_Read_Error_Rate 0x001c 120 120 000 Old_age Offline - 8589934592
    204 Soft_ECC_Correction 0x001c 120 120 000 Old_age Offline - 8589934592
    230 Head_Amplitude 0x0013 100 100 000 Pre-fail Always - 100
    231 Temperature_Celsius 0x0013 100 100 010 Pre-fail Always - 4294967296
    233 Media_Wearout_Indicator 0x0032 000 000 000 Old_age Always - 1126
    234 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 242
    241 Total_LBAs_Written 0x0032 000 000 000 Old_age Always - 242
    242 Total_LBAs_Read 0x0032 000 000 000 Old_age Always - 9


    SMART Error Log not supported
    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% 8009 -


    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

    • Offizieller Beitrag

    177 Wear_Leveling_Count 0x0000 000 000 000 Old_age Offline - 99


    If i interpret that value with my samsung 840 evo, then my drive would be completely wasted.


    This is my current value:


    177 Wear_Leveling_Count PO--C- 098 098 000 - 18 is one year and half of use. When the value 098 goes down to 0 is the end, raw value would be some high value around 1800 if we do a linear interpretation.


    So i could be likely that your ssd is completly wasted. I think adata distributes some tools for windows to check health in their drives. You would need to boot windows or plug the drive in another system with sata (usb adapter won't read smart values i think)


    In my setup i use the flash memory plugin to minimise writes to the disk.
    Maybe some else with more experience in SSD Smart can give an opinion

  • Thanks for that info. As you suggest it would be interesting to hear from someone with more knowledge of SSD's than I! Meanwhile my research shows that there seem to be several interpretations of these smartctl readings. A Samsung user, for example, posted the following re Wear Leveling Count:


    Wear_Leveling_Count is the right attribute to track. However, like the other attributes, 100 is the BEST value and 0 is the WORST. Think of it as "percent life remaining".


    For Samsung SSDs, check SMART attribute 177 (Wear Leveling Count). ID # 177 Wear Leveling Count This attribute represents the number of media program and erase operations (the number of times a block has been erased). This value is directly related to the lifetime of the SSD. The raw value of this attribute shows the total count of P/E Cycles. Source: http://www.samsung.com/global/…tepaper/whitepaper07.html


    So according to this my Wear Leveling Count reading of 99 looks pretty ok.

    Adata use Intel standards, and I'm told that the Media_Wearout_Indicator is what I am looking for. For 100 means your ssd has 100% life, the lower number means less life left.


    In which case my reading of 1126 would seem more than healthy!


    I'm confused, so any contribution from someone better versed in SSD's would be appreciated.


    TIA

    • Offizieller Beitrag

    In which case my reading of 1126 would seem more than healthy!


    That's the raw value of Media_Wearout_Indicator , you should look at normalized value those are the 000 000 000 lines are VALUE WORST and THRESHOLD in line attribute 177 wear level count.


    You start with 100 at value and worst, threshold is 0, means when value reaches 0 is the end.


    Also the error could be browser cache, try open chrome in private mode see if the error comes again

    • Offizieller Beitrag

    Read this thread too.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Thanks, subzero79 & ryecoaaron.


    Followed ryecoaaron's suggested thread and removed ownCloud plugin.


    Used alternative browser as suggested by subzero79.


    Issue resolved. Combination of removal of oC with the new PHP plus the removal of Cert Combo Box solved problem.


    Hopefully using earlier version of oC will be possible. Anyone with success with new install of ownCloud v.7?

    • Offizieller Beitrag

    When are these templates expected to be available, subzero79?


    in hub.docker.com already built, or github in the form of a Dockerfile for building it yourself


    No responses on whether v.7 ownCloud successful on stoneburner: any idea?



    Don't use owncloud, and v7 of owncloud is unsupported by the plugin, there are guides to upgrade in the forum in the section.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!