Attached the drive to my backup pc, and are now in the process of recover files using UFS Explorer Pro Recovery.
Thanks anyways.
I guess I need a new drive
Attached the drive to my backup pc, and are now in the process of recover files using UFS Explorer Pro Recovery.
Thanks anyways.
I guess I need a new drive
When you talk about backup, do you mean drive backup or omw backup?
dmesg output:
dmesg
I've attached the syslog.syslog.zip
The backup I had, was on that group.
I do have a backup from 2016, but have no idea how to restore, since there's no restore button in the gui.
Couldn't run that curl command, since it's not installed, and have very little linux experience - sadly.
edit:
I ran the xfs_repair command on the disc failing with the -n attribute, and this is the output: https://pastebin.com/5RU3c6bi
edit2:
Usually I don't panic, but this freaks me out a bit. Could I by any chance connect the drive otherwise, and copy what's left on it? I don't care about the music, it's the pictures I'm after.
Also been reading that I might could try and zero'ing out any bad blocks, thus missing some few files - but I'll take that any day.
Hi guys,
I really need some help here.
I got the exact same issue, as this guy here: https://forum.openmediavault.o…torage-problem-DATA-Lost/
While listening to music from the drive, it just stopped, and started to skip songs.
I can't connect to the SMB drive, so I took a look on the gui, and saw, that it was unmonted.
When I press the mount button, it shows this error:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount -v --source '/dev/dm-0' 2>&1' with exit code '32': mount: /dev/mapper/VG_Musik_Billeder-Musik_Billeder: can't read superblock
I've tried the mount -a command, but that just gives me the output:
mount: /dev/mapper/VG_Musik_Billeder-Musik_Billeder: can't read superblock
Output of the blkid:
root@nas:~# blkid
/dev/sde: UUID="tFNS1G-i0OZ-KkfP-0P9C-sJWw-Kkrd-2bdfAi" TYPE="LVM2_member"
/dev/sdc: UUID="LcrJod-2EQp-oi23-0mRm-mbOh-j5Uo-ipaZef" TYPE="LVM2_member"
/dev/sda: UUID="TI3DFV-gKaq-d0oK-UFid-RfeL-JKWC-88Q40N" TYPE="LVM2_member"
/dev/sdd: UUID="hgWPii-RbWh-NSPE-Xkxs-0jAt-NYY0-SaCsdD" TYPE="LVM2_member"
/dev/sdb: UUID="egRNhd-th7t-XLHr-0SOh-fY4n-Urb9-j4El2j" TYPE="LVM2_member"
/dev/sdg1: UUID="d9a9a85e-6304-4ea5-a14b-e1b1ff914166" TYPE="ext4" PARTUUID="73f9388b-01"
/dev/sdg5: UUID="7e64765d-8956-40a3-b1eb-7b3216e3a744" TYPE="swap" PARTUUID="73f9388b-05"
/dev/mapper/VG_Musik_Billeder-Musik_Billeder: LABEL="Musik" UUID="69e39260-2291-4253-bf3c-18c22faa9b5e" TYPE="xfs"
/dev/mapper/VG_Film-Film: LABEL="Film" UUID="a3c06756-21dd-4e1d-895d-9d7757d1a65c" TYPE="xfs"
Then:
root@nas:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb1 during installation
UUID=d9a9a85e-6304-4ea5-a14b-e1b1ff914166 / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb5 during installation
UUID=7e64765d-8956-40a3-b1eb-7b3216e3a744 none swap sw 0 0
tmpfs /tmp tmpfs defaults 0 0
# >>> [openmediavault]
UUID=a3c06756-21dd-4e1d-895d-9d7757d1a65c /media/a3c06756-21dd-4e1d-895d-9d7757d1a65c xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
UUID=69e39260-2291-4253-bf3c-18c22faa9b5e /media/69e39260-2291-4253-bf3c-18c22faa9b5e xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
/media/a3c06756-21dd-4e1d-895d-9d7757d1a65c/Backup /sftp/henrik/Backup none bind,rw,nofail 0 0
# <<< [openmediavault]
Display More
and:
root@nas:~# fdisk -l
Disk /dev/sde: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdc: 1,8 TiB, 2000398934016 bytes, 3907029168 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
Disk /dev/sda: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdd: 3,7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdb: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdg: 74,5 GiB, 80026361856 bytes, 156301488 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: 0x73f9388b
Device Boot Start End Sectors Size Id Type
/dev/sdg1 * 2048 149874687 149872640 71,5G 83 Linux
/dev/sdg2 149876734 156301311 6424578 3,1G 5 Extended
/dev/sdg5 149876736 156301311 6424576 3,1G 82 Linux swap / Solaris
Disk /dev/mapper/VG_Musik_Billeder-Musik_Billeder: 1,8 TiB, 2000397795328 bytes, 3907026944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/VG_Film-Film: 10,9 TiB, 12002365800448 bytes, 23442120704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Display More
and finally:
root@nas:~# xfs_repair /dev/mapper/VG_Musik_Billeder-Musik_Billeder
Phase 1 - find and verify superblock...
- reporting progress in intervals of 15 minutes
Phase 2 - using internal log
- zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair. If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
Display More
I'm really screwed now...
The GUI it self. Seems it doesn't take an ip from the router. I even tried to make a static route, so that I could connect to the ip range, but no luck.
I can can use all other services on the box from the LAN side, with no issues...
Hey all,
I've been trying to figure out, why I can't connect to the docker GUI on my local network.
Also been watching a lot of tuts and youtube, but I still can't grasp how I can access it from my local lan.
I can ping the virtual IP of a docker image inside my nas box, but not on my pc.
Are there a kind person, who can help me see the light?
NAS details:
OMV: 3.0.68
Docker: 17.03.1-ce build c6d412e
Display MoreHi,
Still playing around with 3.0, but haven't gotten it installed/running properly. I keep getting "MDADM.CONF defines no arrays" and when I try to log on to the GUI I get Error Message and here's the details:
Error #0:exception 'OMV\Rpc\Exception' with message 'Failed to connect to socket: No such file or directory' in /usr/share/php/openmediavault/rpc/rpc.inc:138
Stack trace:
#0 /var/www/openmediavault/rpc/session.inc(56): OMV\Rpc\Rpc::call('UserMgmt', 'authUser', Array, Array, 2, true)#1 [internal function]: OMVRpcServiceSession->login(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array)
#4 /usr/share/php/openmediavault/rpc/proxy/json.inc(95): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3)
#5 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
#6 {main}
Help or clues to go from here would be gratefully accepted.
I have the exact same issues.
Hi guys,
Since I have some issues with plugins, and other I can't comprehend, I think it's time to to an update.
Failed to execute command 'export LANG=C; apt-get update 2>&1': Ign file: Release.gpg Ign file: Release Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] jessie Release.gpg Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] jessie Release Ign file: Translation-en Hit http://security.debian.org jessie/updates Release.gpg Hit http://ppa.launchpad.net precise Release.gpg Err cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] jessie/contrib amd64 Packages Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs Err cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] jessie/main amd64 Packages Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs Err cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] jessie/non-free amd64 Packages Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] jessie/contrib Translation-en Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] jessie/main Translation-en Ign cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150629-08:52] jessie/non-free Translation-en Hit http://debian.yeasoft.net wheezy Release.gpg Hit http://security.debian.org jessie/updates Release Hit http://ftp.dk.debian.org jessie Release.gpg Hit http://packages.omv-extras.org stoneburner Release.gpg Hit http://ppa.launchpad.net precise Release Hit
The only thing I'm worried about, is my data.
It's all setup in LVM (i think) as xfs.
And was wondering, if I did a fresh install of the new 3.x, will data be lost, or is it just like installing the LVM plugin once new build are installed, and then it will see the volume groups again?
The rest of my current plugins, I can't be bothered with - setup wise.
Meaning I will do them all from scratch if needed.
Hope it's not to noob'ish of a question
I have no experience in gparted, so many some cli commands I could follow, would be much better for me.
Thanks for your answer, but as I wrote initially, I can't reconnect those drives, and I will not be needing them. I just need to get rid of the leftovers.. ☺
I found this very helpfull.
echo "deb http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main" | tee /etc/apt/sources.list.d/webupd8team-java.list
echo "deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main" | tee -a /etc/apt/sources.list.d/webupd8team-java.list
apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys EEA14886
apt-get update
apt-get install oracle-java8-installer
exit
Edit: forgot to mention, that subsonic now works on my box, with those commands above
Hey again,
After a huge help the other day, upgrading from 0.5.60 to 2.1.28, I have a few issues laying around.
One is, that my Raid got damaged while undergoing maintenance. Luckily I had a backup of the files, but now I think this missing raid, are messing with my box.
I can't f.i, enable FTP, I just get errors, when I try to enable it:
From web-gui
Fejl #4000:
exception 'OMVException' with message 'Failed to execute command 'export LANG=C; invoke-rc.d 'proftpd' start 2>&1': Starting ftp server: proftpdNAS proftpd[9250]: ProFTPD terminating (signal 11)
NAS proftpd[9250]: FTP session closed.
Segmentation fault
failed!
invoke-rc.d: initscript proftpd, action "start" failed.' in /usr/share/php/openmediavault/initscript.inc:176
Stack trace:
#0 /usr/share/php/openmediavault/initscript.inc(141): OMVSysVInitScript->invoke('start')
#1 /usr/share/php/openmediavault/initscript.inc(61): OMVSysVInitScript->start()
#2 /usr/share/openmediavault/engined/module/proftpd.inc(79): OMVSysVInitScript->exec()
#3 /usr/share/openmediavault/engined/rpc/config.inc(206): OMVModuleProftpd->startService()
#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#5 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#6 /usr/share/php/openmediavault/rpcservice.inc(158): OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
#7 /usr/share/openmediavault/engined/rpc/config.inc(224): OMVRpcServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(500): OMVRpc::exec('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}
Display More
Under the Filesystem tab, I now have a n/a filesystem.
Here's the log from latest boot log:
Log of fsck -C -R -A -a
Sun Feb 14 18:37:11 2016
fsck from util-linux 2.20.1
/sbin/fsck.xfs: UUID=2cde33e3-2a90-4781-9d3e-0c6f32ddbf11 does not exist
/sbin/fsck.xfs: XFS file system.
/sbin/fsck.xfs: XFS file system.
fsck died with exit status 8
Sun Feb 14 18:37:11 2016
Display More
I'm not able to reconnect the missing raid drives, hence they're physically broken (at least the last one was, the other was damaged 6 months ago)
So I began digging for some solutions - both here, and on good old google, but I didn't get any closer to a soloution, cause most guides told me to rebuild the broken array etc.. But that's not possible in my case. I just want it gone, and only use LVM2 for now.
Oki doki.
Labled the thread as resolved, and I'll have you in my prayers tonite
Huge thanks man!
Yeah, I'll use the openmediavault-backup 1.0.11 plugin, and take a backup asap.
So I don't need to think about updating to version 3 soon?
I'll give it a go....
I can't thank you enough, for all your amazing hard work on this.
I'll be forever grateful!
Would it be safe to say, that I can continue tomorrow, or another day?
What is the output of:
dpkg -l | grep openm
root@NAS:~# dpkg -l | grep openm
ii openmediavault 2.1.27 all Open network attached storage solution
rc openmediavault-backup 0.5.2 all backup plugin for OpenMediaVault.
rc openmediavault-dnsmasq 0.4.4+0~1355672839.2~1.gbpeb9e03 all OpenMediaVault dnsmasq (local DNS and DHCP server) plugin
rc openmediavault-forkeddaapd 0.5.6 all OpenMediaVault forked-daapd (DAAP server) plugin
ii openmediavault-keyring 0.4 all GnuPG archive keys of the OpenMediaVault archive
rc openmediavault-lvm2 0.5.6 all OpenMediaVault Logical Volume Manager (LVM2) plugin
rc openmediavault-minidlna 0.5.9 all OpenMediaVault miniDLNA (DLNA server) plugin
ii openmediavault-omvextrasorg 2.13.1 all OMV-Extras.org Package Repositories for OpenMediaVault
rc openmediavault-openvpnas 1.0.3 all OpenVPN Acess Server plugin for OpenMediaVault.
rc openmediavault-transmissionbt 0.5.18 all OpenMediaVault Transmission (BitTorrent client) plugin
rc openmediavault-virtualbox 0.5.9 amd64 VirtualBox plugin for OpenMediaVault.
rc openmediavault-wol 0.5.1 all OpenMediaVault WOL plugin
Display More
I won't be needing virtualbox and wol btw...
I do, and all went fine.
root@NAS:~# apt-get dist-upgrade
Indlæser pakkelisterne... Færdig
Opbygger afhængighedstræ
Læser tilstandsoplysninger... Færdig
Beregner opgraderingen... Færdig
Følgende pakker vil blive opgraderet:
transmission transmission-cli transmission-common transmission-daemon
4 opgraderes, 0 nyinstalleres, 0 afinstalleres og 0 opgraderes ikke.
1 ikke fuldstændigt installerede eller afinstallerede.
1.676 kB skal hentes fra arkiverne.
Efter denne handling, vil 3.543 kB diskplads blive frigjort.
Vil du fortsætte [J/n]?
Display More
cat /var/lib/dpkg/status | grep libevent
root@NAS:~# cat /var/lib/dpkg/status | grep libevent
Depends: libantlr3c-3.2-0 | libantlr3c-antlrdbg-3.2-0, libasound2 (>> 1.0.18), libavahi-client3 (>= 0.6.16), libavahi-common3 (>= 0.6.16), libavcodec52 (>= 4:0.5.1-1) | libavcodec-extra-52 (>= 4:0.5.1-1), libavformat52 (>= 4:0.5.1-1) | libavformat-extra-52 (>= 4:0.5.1-1), libavl1, libavutil49 (>= 4:0.5.1-1) | libavutil-extra-49 (>= 4:0.5.1-1), libc6 (>= 2.9), libconfuse0 (>= 2.5), libevent-core-1.4-2 (>= 1.4.13-stable), libflac8 (>= 1.2.1), libgcrypt11 (>= 1.4.2), libgpg-error0 (>= 1.6-1), libmxml1, libplist1 (>= 0.16), libsqlite3-0 (>= 3.7.3), libswscale0 (>= 4:0.5.1-1) | libswscale-extra-0 (>= 4:0.5.1-1), libtag1c2a (>= 1.5), libtagc0 (>= 1.5), libunistring0, zlib1g (>= 1:1.1.4), avahi-daemon, adduser, psmisc
Depends: libc6 (>= 2.3), libcap2 (>= 2.10), libcomerr2 (>= 1.01), libdevmapper1.02.1 (>= 2:1.02.20), libevent-2.0-5 (>= 2.0.10-stable), libgssglue1, libk5crypto3 (>= 1.6.dfsg.2), libkeyutils1, libkrb5-3 (>= 1.6.dfsg.2), libmount1 (>= 2.19.1), libnfsidmap2, libtirpc1, libwrap0 (>= 7.6-4~), rpcbind, adduser, ucf, lsb-base (>= 1.3-9ubuntu3), initscripts (>= 2.88dsf-13.3)
Depends: libc6 (>= 2.10), libcurl3-gnutls (>= 7.16.2-1), libevent-2.0-5 (>= 2.0.10-stable), libminiupnpc5, libnatpmp1, libssl0.9.8 (>= 0.9.8m-1), zlib1g (>= 1:1.1.4), transmission-common (= 2.75-1-15~1.gbp4ed609)
Depends: libc6 (>= 2.10), libcurl3-gnutls (>= 7.16.2-1), libevent-2.0-5 (>= 2.0.10-stable), libminiupnpc5, libnatpmp1, libssl0.9.8 (>= 0.9.8m-1), zlib1g (>= 1:1.1.4), transmission-common (= 2.75-1-15~1.gbp4ed609), lsb-base (>= 3.0)
Package: libevent-2.0-5
Source: libevent
event driven network servers. Currently, libevent supports /dev/poll,
For backward compatibility and to transition to "libevent_core only"
or "libevent_core + libevent_extra", the libevent source package builds
the libevent library that includes everything in libevent_core and
libevent_extra.
Homepage: http://libevent.org/
Display More
1 package returned, now rebooting.
Edit: Rebooted fine