omv-firstaid won't change web admin password

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • omv-firstaid won't change web admin password

      Tried to log into the web gui today and was told my username or password was incorrect. Tried the usual stuff, no luck. I'm certain I didn't change my password since the weekend, but decided to just do a re-set with omv-firstaid and be done with it.
      When I try to execute the control panel admin password change, I get the following error.
      Updating control panel administrator password. Please wait ...
      ERROR: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; usermod --password '$1$wITgGd9N$iASwhljseorIBYRc.f5hx/' admin 2>&1' with exit code '1': usermod: cannot lock /etc/passwd; try again later.

      I did find this thread with a similar issue, but the steps listed there don't work for me. forum.openmediavault.org/index…update-OMV-on-raspberry2/

      Also, I'm not sure if this matters, but the system seems sluggish.

      Any ideas?
    • The root filesystem is surely full.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Oh. How do I check that?
      It's a 150GB ssd.


      EDIT: ran the df command and this was the output.

      Filesystem 1K-blocks Used Available Use% Mounted on

      udev 12315196 0 12315196 0% /dev
      tmpfs 2466992 274852 2192140 12% /run
      /dev/sda1 90094440 3032944 82441876 4% /
      tmpfs 12334944 0 12334944 0% /dev/shm
      tmpfs 5120 0 5120 0% /run/lock
      tmpfs 12334944 0 12334944 0% /sys/fs/cgroup
      tmpfs 12334944 4740 12330204 1% /tmp
      JXNSRZ-part1:K5R14N-part1 19376767176 12746113800 6630620608 66% /sharedfolders/Colossus
      /dev/sdd1 9764087780 6397883200 3366188196 66% /srv/dev-disk-by-label-Parity
      /dev/sde1 491207900 10717244 480474272 3% /srv/dev-disk-by-id-ata-Samsung_SSD_850_PRO_512GB_S250NXAGB52683Y-part1
      /dev/sdb1 9688383588 6393550548 3294816656 66% /srv/dev-disk-by-id-ata-WDC_WD100EFAX-68LHPN0_JEJXNSRZ-part1
      /dev/sdc1 9688383588 6352563252 3335803952 66% /srv/dev-disk-by-id-ata-WDC_WD100EFAX-68LHPN0_JEK5R14N-part1
      So looks like my boot drive sda is 4% full.

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

    • Have never seen that, but maybe Google can help you.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Ah I see what you did there. You searched just for the relevant part of the error message. My eyes glazed over as soon as I hit the Path=/ part so ended up just searching for the whole string.

      Last night I got impatient and re-started the server and that resolved it. For now. I'll check those search results if it happens again and try the mentioned strace -f -e trace=file command.
    • So the same thing has happened again. First noticed today that I couldn't access the network file share, and then couldn't log into the web GUI.

      I tried to follow the instructions from the results in @votdevs post, but had to install strace first. When I tried to install it, I get the following error.
      apt-get install strace

      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      The following NEW packages will be installed:
      strace
      0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
      Need to get 533 kB of archives.
      After this operation, 1,396 kB of additional disk space will be used.
      Err:1 deb.debian.org/debian stretch/main amd64 strace amd64 4.15-2
      Could not open file /var/cache/apt/archives/partial/strace_4.15-2_amd64.deb - open (30: Read-only file system)
      W: Not using locking for read only lock file /var/lib/dpkg/lock
      W: chown to _apt:root of directory /var/cache/apt/archives/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
      W: chmod 0700 of directory /var/cache/apt/archives/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
      W: Not using locking for read only lock file /var/cache/apt/archives/lock
      W: Problem unlinking the file /var/cache/apt/archives/partial/.apt-acquire-privs-test.2PNfO8 - IsAccessibleBySandboxUser (30: Read-only file system)
      W: Problem unlinking the file /var/cache/apt/archives/partial/strace_4.15-2_amd64.deb - PrepareFiles (30: Read-only file system)
      E: Failed to fetch deb.debian.org/debian/pool/mai…e/strace_4.15-2_amd64.deb Could not open file /var/cache/apt/archives/partial/strace_4.15-2_amd64.deb - open (30: Read-only file system)
      E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
      Tried running apt-get update, but again got a ton of errors ending in (30: Read-only file system).

      The post was edited 1 time, last by sonofwatt: Speeeling ().

    • Check the syslog, the kernel will log it when he re-mounts a filesystem as read-only.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • I manged to get the logs. Couldn't use less command since it wasn't installed and couldn't add it with the system in this state, so ended up using WinSCP to log in and download the logs. Seems like an awesome app for novice users like me.

      @votdev What should I be looking/searching for in the logs?
      I don't really want to post them, but I'm game to send them directly to whoever is willing to take a look.
    • sonofwatt wrote:

      I manged to get the logs. Couldn't use less command since it wasn't installed and couldn't add it with the system in this state
      You can use the already installed tools cat, more, nano, head or tail.


      sonofwatt wrote:

      What should I be looking/searching for in the logs?
      Something like that

      Source Code

      1. Mon Day time Servername kernel: ext3_abort called.
      2. Mon Day time Servername kernel: EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
      3. Mon Day time Servername kernel: Remounting filesystem read-only
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • votdev wrote:

      You can use the already installed tools cat, more, nano, head or tail.
      Ah ok, good to know. Thank you.

      I searched multiple log files, but got no match for any of those terms. Tried, ext, ext4, filesystem, read-only and some other variations. Only 'abort' returned 1 match. Interestingly it's near the end of the log. Nothing has been added in 5 days to the log.
      Here's a snippet from the end of the log up a to the abort command.
      Display Spoiler

      Sep 20 15:45:01 Odin CRON[19161]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/null 2>&1)
      Sep 20 15:54:12 Odin kernel: [230351.436193] sd 1:0:0:0: attempting task abort! scmd(000000006efce6cf)
      Sep 20 15:54:12 Odin kernel: [230351.436200] sd 1:0:0:0: [sda] tag#648 CDB: Write(10) 2a 00 04 80 08 30 00 00 08 00
      Sep 20 15:54:12 Odin kernel: [230351.436204] scsi target1:0:0: handle(0x000d), sas_address(0x4433221107000000), phy(7)
      Sep 20 15:54:12 Odin kernel: [230351.436206] scsi target1:0:0: enclosure logical id(0x500605b0091ae200), slot(4)
      Sep 20 15:54:16 Odin kernel: [230355.239927] sd 1:0:0:0: task abort: SUCCESS scmd(000000006efce6cf)
      Sep 20 15:54:16 Odin kernel: [230355.239944] sd 1:0:0:0: attempting task abort! scmd(00000000a97df352)
      Sep 20 15:54:16 Odin kernel: [230355.239949] sd 1:0:0:0: [sda] tag#647 CDB: Write(10) 2a 00 04 53 6a 38 00 00 08 00
      Sep 20 15:54:16 Odin kernel: [230355.239952] scsi target1:0:0: handle(0x000d), sas_address(0x4433221107000000), phy(7)
      Sep 20 15:54:16 Odin kernel: [230355.239955] scsi target1:0:0: enclosure logical id(0x500605b0091ae200), slot(4)
      Sep 20 15:54:16 Odin kernel: [230355.239958] sd 1:0:0:0: task abort: SUCCESS scmd(00000000a97df352)
      Sep 20 15:54:16 Odin kernel: [230355.239967] sd 1:0:0:0: attempting task abort! scmd(000000000993aa62)
      Sep 20 15:54:16 Odin kernel: [230355.239971] sd 1:0:0:0: [sda] tag#646 CDB: Write(10) 2a 00 04 44 60 28 00 00 08 00
      Sep 20 15:54:16 Odin kernel: [230355.239973] scsi target1:0:0: handle(0x000d), sas_address(0x4433221107000000), phy(7)
      Sep 20 15:54:16 Odin kernel: [230355.239976] scsi target1:0:0: enclosure logical id(0x500605b0091ae200), slot(4)
      Sep 20 15:54:16 Odin kernel: [230355.239979] sd 1:0:0:0: task abort: SUCCESS scmd(000000000993aa62)
      Sep 20 15:54:16 Odin kernel: [230355.239985] sd 1:0:0:0: attempting task abort! scmd(00000000cc1ffed6)
      Sep 20 15:54:16 Odin kernel: [230355.239988] sd 1:0:0:0: [sda] tag#645 CDB: Write(10) 2a 00 04 44 47 d0 00 00 08 00
      Sep 20 15:54:16 Odin kernel: [230355.240028] scsi target1:0:0: handle(0x000d), sas_address(0x4433221107000000), phy(7)
      Sep 20 15:54:16 Odin kernel: [230355.240032] scsi target1:0:0: enclosure logical id(0x500605b0091ae200), slot(4)
      Sep 20 15:54:16 Odin kernel: [230355.240036] sd 1:0:0:0: task abort: SUCCESS scmd(00000000cc1ffed6)
    • yes, reboot and recheck, this time must be mounted on RW if not chkdsk disk to find the problem.


      PD: Wen a fail in boot disk happens, the next time of reboot the OS is mounted on Read-only until the problem is solved.
      OMV 4.1.11 x64 on a HP T510, 16GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ; ctop
      Dockers: MLDonkey ; PiHole ; weTTY
      Videos: @TechnoDadLife
    • I tried to use the forcefsck file method to make the system use fsck on boot. It scanned 3 of my other drives, but not the boot drive, also seems to have skipped with 2 others. Not sure why.
      I checked fstab and sda1 is set to 1. For some reason there are no fstab files for the other drives.
      I followed this tutorial thegeekstuff.com/2016/03/forcefsck-on-reboot/ And during that noticed my boot drive wasn't set to auto-scan with fsck ever. Tried initally running the command tune2fs -c 1 /dev/sda but it kicked out the error "Found a dos partition table in /dev/sda".

      I then noticed in fdisk that the drive is showing as having a "disklabel type" of dos. Is that normal? (full output below)
      Display Spoiler
      root@Odin:~# fdisk -l
      Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x13346caf

      Device Boot Start End Sectors Size Id Type
      /dev/sda1 * 2048 184131583 184129536 87.8G 83 Linux
      /dev/sda2 184133630 234440703 50307074 24G 5 Extended
      /dev/sda5 184133632 234440703 50307072 24G 82 Linux swap / Solaris


      I then was able to set the scan interval to 1 with tune2fs -c 1 /dev/sda1 I guess the 1 is needed. But even then, after a couple reboots, the output from tune2fs -l /dev/sda1 | grep -i check shows a last checked date from months ago.


      Also I noticed earlier after a few hours of rebooting the system the 1st time today, using WeTTy was really sluggish. After rebooting just now, it's back to normal speed. I did check the system resources and before the restart CPU was at 2% and used RAM at 6%. Not sure what's going on there.
    • I tried to use the forcefsck file method to make the system use fsck on boot. It scanned 3 of my other drives, but not the boot drive, also seems to have skipped with 2 others. Not sure why.
      I checked fstab and sda1 is set to 1. For some reason there are no fstab files for the other drives.
      I followed this tutorial thegeekstuff.com/2016/03/forcefsck-on-reboot/ And during that noticed my boot drive wasn't set to auto-scan with fsck ever. Tried initally running the command tune2fs -c 1 /dev/sda but it kicked out the error "Found a dos partition table in /dev/sda".

      I then noticed in fdisk that the drive is showing as having a "disklabel type" of dos. Is that normal? (full output below)
      Display Spoiler
      root@Odin:~# fdisk -l
      Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x13346caf

      Device Boot Start End Sectors Size Id Type
      /dev/sda1 * 2048 184131583 184129536 87.8G 83 Linux
      /dev/sda2 184133630 234440703 50307074 24G 5 Extended
      /dev/sda5 184133632 234440703 50307072 24G 82 Linux swap / Solaris


      I then was able to set the scan interval to 1 with tune2fs -c 1 /dev/sda1 I guess the 1 is needed. But even then, after a couple reboots, the output from tune2fs -l /dev/sda1 | grep -i check shows a last checked date from months ago.


      Also I noticed earlier after a few hours of rebooting the system the 1st time today, using WeTTy was really sluggish. After rebooting just now, it's back to normal speed. I did check the system resources and before the restart CPU was at 2% and used RAM at 6%. Not sure what's going on there.
    • boot from liveUSB or LiveUSB to perform a fsck on boot disk.


      revise your SMART values to see if some sectors are mark as bad on SMART.
      OMV 4.1.11 x64 on a HP T510, 16GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ; ctop
      Dockers: MLDonkey ; PiHole ; weTTY
      Videos: @TechnoDadLife
    • If you're certain that the boot drive is the issue, I'm game to buy a new SSD and do a fresh install. I'm desperate to get this up and running reliably. At this point I'll try just about anything.

      I'll do the LiveUSB boot/scan and report back.

      Here is the SMART info for this disk:
      Display Spoiler

      smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.19.0-0.bpo.5-amd64] (local build)
      Copyright (C) 2002-16, Bruce Allen, Christian Franke, smartmontools.org

      === START OF INFORMATION SECTION ===
      Model Family: Phison Driven SSDs
      Device Model: KINGSTON SA400S37120G
      Serial Number: 50026B7682A86189
      LU WWN Device Id: 5 0026b7 682a86189
      Firmware Version: SBFKB1D1
      User Capacity: 120,034,123,776 bytes [120 GB]
      Sector Size: 512 bytes logical/physical
      Rotation Rate: Solid State Device
      Form Factor: 2.5 inches
      Device is: In smartctl database [for details use: -P show]
      ATA Version is: Unknown(0x0ff8) (minor revision not indicated)
      SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
      Local Time is: Tue Oct 1 14:48:45 2019 EDT
      SMART support is: Available - device has SMART capability.
      SMART support is: Enabled

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

      General SMART Values:
      Offline data collection status: (0x00) Offline data collection activity
      was never started.
      Auto Offline Data Collection: Disabled.
      Self-test execution status: ( 0) The previous self-test routine completed

      without error or no self-test has ever
      been run.
      Total time to complete Offline
      data collection: (65535) seconds.
      Offline data collection
      capabilities: (0x79) SMART execute Offline immediate.
      No Auto Offline data collection support.
      Suspend 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: ( 2) minutes.
      Extended self-test routine
      recommended polling time: ( 30) minutes.
      Conveyance self-test routine
      recommended polling time: ( 6) minutes.

      SMART Attributes Data Structure revision number: 16
      Vendor Specific SMART Attributes with Thresholds:
      ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate 0x0032 000 100 000 Old_age Always - 0
      9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 2879
      12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 60
      148 Unknown_Attribute 0x0000 100 100 000 Old_age Offline - 0
      149 Unknown_Attribute 0x0000 100 100 000 Old_age Offline - 0
      167 Write_Protect_Mode 0x0000 100 100 000 Old_age Offline - 0
      168 SATA_Phy_Error_Count 0x0012 100 100 000 Old_age Always - 0
      169 Bad_Block_Rate 0x0000 100 100 000 Old_age Offline - 28
      170 Bad_Blk_Ct_Erl/Lat 0x0000 100 100 000 Old_age Offline - 0/19
      172 Erase_Fail_Count 0x0032 100 100 000 Old_age Always - 0
      173 MaxAvgErase_Ct 0x0000 100 100 000 Old_age Offline - 9 (Average 7)
      181 Program_Fail_Count 0x0032 100 100 000 Old_age Always - 0
      182 Erase_Fail_Count 0x0000 100 100 000 Old_age Offline - 0
      187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
      192 Unsafe_Shutdown_Count 0x0012 100 100 000 Old_age Always - 15
      194 Temperature_Celsius 0x0022 076 073 000 Old_age Always - 24 (Min/Max 17/27)
      196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
      199 SATA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 0
      218 CRC_Error_Count 0x0032 100 100 000 Old_age Always - 0
      231 SSD_Life_Left 0x0000 001 001 000 Old_age Offline - 99
      233 Flash_Writes_GiB 0x0032 100 100 000 Old_age Always - 432
      241 Lifetime_Writes_GiB 0x0032 100 100 000 Old_age Always - 245
      242 Lifetime_Reads_GiB 0x0032 100 100 000 Old_age Always - 94
      244 Average_Erase_Count 0x0000 100 100 000 Old_age Offline - 7
      245 Max_Erase_Count 0x0000 100 100 000 Old_age Offline - 9
      246 Total_Erase_Count 0x0000 100 100 000 Old_age Offline - 26736
      246 Total_Erase_Count 0x0000 100 100 000 Old_age Offline - 26736

      SMART Error Log Version: 1
      No Errors Logged

      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% 2879 -

      SMART Selective self-test log data structure revision number 0
      Note: revision number not 1 implies that no selective self-test has ever been run
      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.
    • try to boot without VGA Attached , perhaps your Radeon VGA have some problems and reboot your NAS.

      Once your NAS it's installed no need to have a VGA unless your NAS need one to boot
      OMV 4.1.11 x64 on a HP T510, 16GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ; ctop
      Dockers: MLDonkey ; PiHole ; weTTY
      Videos: @TechnoDadLife