Posts by magnets99

thanks!

Hi,

So unfortunately there are too many results for ext4 or zfs so i'm hoping someone can give me some advice.

I have an SSD for the os and dockers (sdb)

I have a 4tb spinning rust disc for data (sda)

the data drive is one partition ext4

I'm using a fairly chunky intel i3 x86 based board with sata ports a plenty.

I don't have a need for raid as constant uptime is not important to me.

I use an external 6tb usb3 drive for backup and it gets backed up and stored offsite regularly.

i'm starting to run out of space on my data drive.

I have a spare 1.5tb disc i can shove in.

I do not want to have multiple shares with 'some' data on one drive and 'other' data on another drive. I have four categories of data (lets say photos, documents, music and dvds) and none of the those categories will fit into the 1.5tb disc without massive waste or running out of space.

So can i add my 1.5tb disc and have 'one file system' that uses both discs combined?

I thought this was possible with ext4 JBOD but it would appear i can't simply grow the partition across.

I'd rather not have to copy data from the usb backup as that will take a long while and leaves me vulnerable during the restore.

ok, this has been fixed via an upgrade to OMV
relates to this thread
Error: "Failed to read file '/tmp/bgstatusfs2WVj' (size=0)."?

simply use the upgrade manager

Hello,
I recently did a clean install on OMV and went from 0.7 to 4.
I have a USB backup drive with a previous copy of a backup from when it was 0.7.
I'm unsure if that info is pertinent.

I plugged in the USB some days ago and forgot about it.
Today i went into file systems and mounted the drive like i usually did.
When i went to USB backup i set up a new job with the same settings as before. When i tried to run the job it failed with a message saying the drive was not mounted.
I went back to the file system and sure enough it said it wasn't mounted (even though i had mounted it before).
I reboot OMV with the drive still connected.
Now when i go to the File Systems page i immediately get an error

Failed to read file '/tmp/bgstatusmeBQE3' (size=0).

in the background the page loads as normal and show the USB drive (dev/sdc1) as mounted

The details of the error are:

Error
Failed to read file '/tmp/bgstatusZR7vTz' (size=0).

Error
Failed to read file '/tmp/bgstatusAiup1I' (size=0).

Error
Failed to read file '/tmp/bgstatusmeBQE3' (size=0).

Error #0:OMV\Exception: Failed to read file '/tmp/bgstatusmeBQE3' (size=0). in /usr/share/php/openmediavault/json/file.inc:199Stack trace:#0 /usr/share/php/openmediavault/json/file.inc(214): OMV\Json\File->getContents()
#1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(314): OMV\Json\File->read()
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(544): OMV\Rpc\ServiceAbstract->finalizeBgProcStatus('/tmp/bgstatusme...', '', Object(OMV\Exception))
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#4 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(461): OMV\Rpc\ServiceAbstract->callMethodBg('getList', Array, Array)
#5 [internal function]: OMVRpcServiceFileSystemMgmt->getListBg(Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getListBg', Array, Array)
#8 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('FileSystemMgmt', 'getListBg', Array, Array, 1)
#9 {main}

Any ideas?
I haven't tried running a backup again but have posted in this forum as i think this is the most appropriate.

Part 2

Part 2: compiling from source:

I tried following these instructions
https://github.com/transmissio…iki/Building-Transmission
which are massively out of date and will give you errors.
and so, this is how i did it, and how i got round the errors.

FIRST FIRST FIRST COPY DOWN YOUR SETTINGS FOR TRANSMISSION, YOU WILL NEED THEM LATER.

first, connect to your box and bring up the console.
I have logged in as root, but i've used the sudo command anyway so apart from being asked a password occasionally this should work whether you are logged in as root or not.
If one of the commands says permission denied, try putting sudo in front of the command and try again.
anything in a block quote should be entered in its entirety

first up, let update apt
sudo apt-get update

if you get loads of errors check that your box can reach the internet.
next up lets check the install of transmission
sudo apt-get install transmission

if you get this error:
Reading package lists... Done
Building dependency treeReading state information... Done
transmission is already the newest version (2.92-2+deb9u1).
0 upgraded, 0 newly installed, 0 to remove and 37 not upgraded.

then carry on, if you don't then congratulations, someone has updated your repository since i wrote this and you can upgrade the easy way.

so what we're going to do is download the source code for the latest version of transmission, then compile it (turn it from human readable text into a program that can be run on the computer)
first though, all the things you need to compile transmisison are broken.
and... some of the things that the things that compile transmission need are also broken.
So let start at the bottom and do a bit of Yak shaving.
sudo apt-get install ca-certificates libcurl4-openssl-dev libssl-dev pkg-config build-essential checkinstall

off it will go, it should complain but not give you any proper "i can't do this because of reasons" errors

now we're going to move to the tmp directory
cd /var/tmp

let's download libevent
wget https://github.com/libevent/li…event-2.1.8-stable.tar.gz
and now we can extract that file
tar xzf libevent-2.1.8-stable.tar.gz
and move into that folder
cd libevent-2.1.8-stable/
now we compile libevent
CFLAGS="-Os -march=native" ./configure && make
ok, this is where it started to go wrong for me, checkinstall is a program that does something, and maybe soemone can reply with what it does, but it doesn't seem to be required to get Trnasmssion upgraded so lets move on.

So now we've got the things that the things that compile transmission need working (probably) lets get come out of this folder
cd /var/tmp

and go and get yet more stuff (if you're on ubuntu or another 'richer' install you may have all of these things, i didn't)
sudo apt-get install libevent-dev
sudo apt-get install zlib1g-dev
sudo apt-get install intltool

ugh, never ends.
ok, lets see if that was enough.
lets go get transmission.
wget https://github.com/transmissio…/transmission-2.93.tar.xz

oh look, it's an xz file that your computer can't work with. sigh.
let get xz utils
sudo apt-get install xz-utils

and now we should be able to extract transmission
tar xf transmission-2.93.tar.xz
and move to that folder
cd transmission-2.93/

man, did i mention you should have got a beverage before all this?

let see if we can compile it
CFLAGS="-Os -march=native" ./configure && make && checkinstall

did it take forever and give you a bucketton of warnings? good.

it will then fall into checkinstall which is that program from before. It will give you a load of questions. When it asks about the package description type
transmission293

then press enter twice

it will spend a lot time doing things, you're actually watching another program now called checkinstall. Yes that one that failed earlier.
did it end ok? Yes? good, you can skip this bit (jump to welcome back), if it failed miserably do this bit:

if your checkinstall ended with this

/bin/mkdir: cannot create directory ‘/usr/local/share/transmission’: No such file or directoryMakefile:405: recipe for target 'install-dist_dataDATA' failedmake[3]:
*** [install-dist_dataDATA] Error 1make[3]: Leaving directory '/var/tmp/transmission-2.93/web/images'Makefile:475: recipe for target 'install-am' failedmake[2]:
*** [install-am] Error 2make[2]: Leaving directory '/var/tmp/transmission-2.93/web/images'Makefile:497: recipe for target 'install-recursive' failedmake[1]:
*** [install-recursive] Error 1make[1]: Leaving directory '/var/tmp/transmission-2.93/web'Makefile:508: recipe for target 'install-recursive' failedmake:
*** [install-recursive] Error 1
**** Installation failed. Aborting package creation.
Cleaning up...OK
Bye.

Then this sucks. so lets fix it.
lets go where checkinstall config lives
cd /etc/

and open up the config file
sudo nano checkinstallrc

somewhere in this config file we need to make a change...

find the bit that says
# Are we going to use filesystem translation?
TRANSLATE=1
and change it to say
# Are we going to use filesystem translation?
TRANSLATE=0

now write out (ctrl+o) and exit (ctrl+x)

back to the folder
cd /var/tmp/transmission-2.93/

and lets try that again
CFLAGS="-Os -march=native" ./configure && make && checkinstall

and welcome back, you should have got

**********************************************************************

Done. The new package has been installed and saved to

/var/tmp/transmission-2.93/transmission_2.93-1_amd64.deb

You can remove it from your system anytime using:

dpkg -r transmission

**********************************************************************

ok, that worked, you've proven you can get the new one installed. you're probably still running the old one, so lets stop that and remove it
sudo service transmission-daemon stop

and (after a few seconds)
sudo apt-get remove transmission transmission-daemontransmission-common transmission-gtk transmission-cli transmission-qt

you'll get a few grumbles but you should see 2.92 get uninstalled.
now lets put the new in again

sudo service transmission-daemon start
oh dear, did you get

Failed to start transmission-daemon.service: Unit transmission-daemon.service is masked.
so to fix that we'll
sudo systemctl unmask transmission-daemon.service

and

start it again.
sudo service transmission-daemon start

is it working? you can tell with
sudo service transmission-daemon status

(i see Active active (exited) which i think is good. Now if you're using the normal transmision (not just the deamon) you can fire it up and put your settings in THAT YOU COPIED DOWN IN THE FIRST STEP.

woohoo you're done.

hello,
many torrent sites are banning the transmission client 2.92 and below. This is a problem becuase 2.93 is relativly new and is not in any repository or omv extras.
This is how i manged to get to 2.93. The guide was written for another site so might be a bit more generic, but hopefully, if you're a begginer to linux like me, you'll be able to follow it.

Are you trying to upgrade to Transmission 2.93 but,like me, are stuck in Linux hell of "simply compile from source" and then no instructions on how to do that?

I'm not a linux expert, but i am really stubborn.
So here's my guide.

Prerequisites:

You must have the ability to reach the CLI/Bash window of the computer you wish to upgrade.
You should at least know what the sudo, cd and ls commands do. If not, you'll struggle to follow this.
READ THE REPLIES TO THIS THREAD don't go blindly following the advice of some random on the internet. Wait for some other sucker to test my instructions and/or reply with how i could have done it better.

My system:
I'm using an ATOM intel pc running x64 bit architecture and kernel 4.4 of Debian.
I'm running Openmediavault on top.

I WILL NOT HELP YOU IF YOU BORK YOUR SYSTEM

Now this guide is in two parts, the first part is getting the new version from a repository, which; if it works, is much easier. and the second very long and very hard part where you really really have to compile from source. Which is the equivalent of building a car from parts with the help of a robot that sort of knows what its doing.


Part 1: trying a respository.

ok, so since this whole thing started there may have been an update to the repository to get you out of trouble.
My box is an x686 architecture device, and that is what the repository:

https://launchpad.net/~transmissionbt/+archive/ubuntu/ppa

says was updated on the 21 March 2018 (2.93-1ubuntu1~17.10.2)
I could be reading this wrong but if your device ISN'T a computer (it's a raspberry pi, or a firestick, or a nas box) running x86 or 64 bit archetecture this might not work for you and you're stuck with part 2.

anyway, lets add this repositry
sudo add-apt-repository ppa:transmissionbt/ppa

uh oh, did you get an error about command not found. don't worry do this to fix it
sudo apt-get install -y software-properties-common

ok, try that first command again.

did it work? no? it gave you an error like this:
gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory
gpg: connecting dirmngr at '/tmp/tmpyqcnq05k/S.dirmngr' failed: No such file or directory

ok, you need this
sudo apt-get install dirmngr

right, did that work? of course not. you probably got this error

Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fcdfd141510>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fcdfd141510>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable

so we're going to need to fix that too.

lets go to where python lives
cd /usr/lib/python3.5/

and edit the file that's being annoying
nano weakref.py

find line 109 (you can use ctrl+_ and type in 109)

change this

def remove(wr, selfref=ref(self)):

so it says this

def remove(wr, selfref=ref(self), _atomic_removal=_remove_dead_weakref):

and 117 change this

_remove_dead_weakref(d, wr.key)

with:

_atomic_removal(d, wr.key)

write it out (ctrl+o) and exit (ctrl+x)
lets try that command again

hmmm, that didn't work for me, just said i'ts already installed, but i don't trust it, so we'll remove it, and add back again
sudo apt-get remove dirmngr

and back in again
sudo apt-get install dirmngr

great, now lets update
sudo apt-get update

and try and install transmission
sudo apt-get install transmission

hopefully, it will then install 2.93-1 (or higher) and you're done!

but wait, when i try it, it still says 2.92 so something isn't right

restart, no change. ok, lets ask it where it thinks transmission is
which transmission-cli

mine says /usr/bin/transmission-cli

and when i go (note the capital v there)
/usr/bin/transmission-daemon -V

it says 2.92. so how it that possible?
perhaps i now have two versions of transmission, one installed in the 'correct' place running 2.93 and one in the 'wrong' place running 2.92
so two approaches to fix this, change the path so that it looks for the correct one, or copy the new version over the top.
i'm going for the latter.

stop transmision
sudo service transmission-daemon stop

lets find all my transmission-daemons
sudo find / -type f -name "transmission-daemon"

that might take a while
but i get

/etc/init.d/transmission-daemon
/etc/default/transmission-daemon
find: ‘/proc/1387’: No such file or directory
find: ‘/proc/1390/task/1390/net’: Invalid argument
find: ‘/proc/1390/net’: Invalid argument
/var/tmp/transmission-2.93/daemon/transmission-daemon
/usr/local/bin/transmission-daemon
/usr/bin/transmission-daemon

now for those of you playing along, you probably got somethign different. The reason is i've already tried part two of this guide and have pretty much littered my system with failed attempts. the 'correct' install location is

/usr/local/bin/

and not /usr/bin

so, with the new files in /usr/local/bin lets copy them accross
sudo cp /usr/local/bin/transmission-show /usr/bin/transmission-show
sudo cp /usr/local/bin/transmission-remote /usr/bin/transmission-remote
sudo cp /usr/local/bin/transmission-edit /usr/bin/transmission-edit
sudo cp /usr/local/bin/transmission-daemon /usr/bin/transmission-daemon
sudo cp /usr/local/bin/transmission-create /usr/bin/transmission-create
sudo cp /usr/local/bin/transmission-cli /usr/bin/transmission-cli

now when i tried that last one (transmission-cli) i got an error (cp: cannot stat '/usr/local/bin/transmission-cli': No such file or directory) which means source file not found.
we're going to ignore that.

ok, so reboot
reboot

is everything working? ahHAHAHAHA no of course not.
on my home client i'm getting "connection refused" and when i log back into the server and run
sudo service transmission-daemon status

i get

● transmission-daemon.service - Transmission BitTorrent Daemon
Loaded: loaded (/lib/systemd/system/transmission-daemon.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Mon 2018-04-30 19:52:07 AEST; 5min ago
Process: 555 ExecStart=/usr/bin/transmission-daemon -f --log-error (code=exited, status=0/SUCCESS)
Main PID: 555 (code=exited, status=0/SUCCESS)

Apr 30 19:50:36 mediafiler systemd[1]: Starting Transmission BitTorrent Daemon...
Apr 30 19:50:40 mediafiler transmission-daemon[555]: sendto: Network is unreachable
Apr 30 19:50:42 mediafiler transmission-daemon[555]: [2018-04-30 19:50:42.197] UDP Failed to set receive buffer: requested 4194304, got 425
984 (tr-udp.c:84)
Apr 30 19:50:42 mediafiler transmission-daemon[555]: [2018-04-30 19:50:42.198] UDP Failed to set send buffer: requested 1048576, got 425984
(tr-udp.c:95)
Apr 30 19:52:06 mediafiler systemd[1]: transmission-daemon.service: Start operation timed out. Terminating.
Apr 30 19:52:07 mediafiler systemd[1]: Failed to start Transmission BitTorrent Daemon.
Apr 30 19:52:07 mediafiler systemd[1]: transmission-daemon.service: Unit entered failed state.
Apr 30 19:52:07 mediafiler systemd[1]: transmission-daemon.service: Failed with result 'timeout'.

the important bit here isn't Network is unreachable, but that timeout error at the end
this is a bug in the build instructions which carried through to the ppa repository (which was built using the build instructions) see this rather salty exchange here for more info
https://github.com/transmission/transmission/issues/537

but lets not worry too much about that, how do we fix it? like this:

make a directory
sudo mkdir /etc/systemd/system/transmission-daemon.service.d/

make a file in that directory and open it for editing
sudo nano /etc/systemd/system/transmission-daemon.service.d/override.conf

write in that file

[Service]
Type=simple
User=debian-transmission
Group=debian-transmission

write out and exit
reboot
reboot

and we're done.

unless you couldn't get the repository to work, in which case, you'll need to "simply compile from sauce" which my guide is in part 2 below.

good luck.

thanks!

hi,
To whoever is doing the website (which is nice btw).
I need to rebuild OMV.
I go to this page
https://www.openmediavault.org/download.html
and click on the hyperlink
create an USB stick
but this goes to a 404 on the docs site.

Perhaps it could point to one of the guides in the forum?

thanks!

thanks everyone,

Ellnic: Yes i have two separate drives. I hadn't even thought that OMV would be happy with just plugging in the data drive back in. Are the shares and user ACL's stored on the data drive?

The home made guide is a great idea. I think i actually have some notes.
And hey, maybe it's time to try some new bits and bobs. I've been looking at flexget...

Hi All,
I'm a long time user of OMV. In fact so long i've been using 0.5 since it came out and never upgraded.
I also installed some plugins manually (omv-extras.org) and some through the cmd line.
I've run into an issue with SMB1 and I understand OMV 3 and above support SMB3+

Whilst i could just upgrade the SAMBA part it's probably a good time for me to upgrade.

What is the path for me to go from 0.5 to 4?

My system:

Official plugins:
openmediavault-transmissionbt 0.5.18
openmediavault-usbbackup 0.5.10
openmediavault-omvextrasorg 0.6.25

unoffical/ self installed programs:

Sabnzbd
couch potato
headphones
sickbeard

Data:
3 TiB on a single ext4 drive
2 users (one is read only)
Data (but not config) is backed up to a 3TiB USB drive

Hardware:
intel Atom mini ITX board Linux 2.6.32-5-686

I'd rather upgrade over reinstall because:
The motherboard does not support usb 3, so putting my data back will take a loooong time
everything else about my config works, and i remember it being an absolute pain to getting everything to play nice (sickbeard talking to sabnzb etc).

While i understand that if it doesn't work that's a lot of time wasted, but a reinstall is likely to take me about 7-14 hours so wasting 2 hours trying to upgrade is probably worth it.

but how do i do that? apt-get upgrade?
do i have to go .5>1>2>3>4?
Do i need to upgrade the plugins first or second?
I've had a look for some guides, and found this thread

Is it possible to upgrade from 0.5.60 (saudakar) to 2.x ?

which references instructions
Is it possible to upgrade from 0.5.60 (saudakar) to 2.x ?

but that link has been removed.

thanks David, will do.
Thanks again for the prompt response.

hello, this may be a stupid question but:

i had a single 1.5tb drive for data. a few months ago it died.
I bought a new 4tb drive, cloned from an offsite backup stuck it in and all was good.
but... it's cloned. so it's still only 1.5tb
how do i make it 4tb?

i went into omv webgui and clicked on physical disks. it's 4tb in there
I go into file systems and it says capacity 1.5
if i select it and click on resize i get a warning up that says

Quote

Do you really want to resize the selected file system? You have to do that after a RAID has been grown for example.

i click yes but nothing happens.

have i misunderstood what this funciton is for?

the machine itself has no cd rom drive and is in the garage so its hard to get to physiaclly (but i can ssh ok).

ok, i tried installing it again via the plugins

it spend a long time on updating locale, but i kept wiggling the mouse to prevent the session ending

aaaaHHHAAAA right, i've managed to configure it, and i can connect to it remotley via Tranmission Remote GUI
Thank you for all your help!

this was the log window output

Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
  transmission-daemon
The following NEW packages will be installed:
  openmediavault-transmissionbt transmission-daemon
0 upgraded, 2 newly installed, 0 to remove and 26 not upgraded.
Need to get 0 B/278 kB of archives.
After this operation, 1034 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  transmission-daemon openmediavault-transmissionbt
Authentication warning overridden.
Selecting previously deselected package transmission-daemon.
(Reading database ... 31279 files and directories currently installed.)
Unpacking transmission-daemon (from .../transmission-daemon_2.75-1-15~1.gbp4ed609_i386.deb) ...
Selecting previously deselected package openmediavault-transmissionbt.
Unpacking openmediavault-transmissionbt (from .../openmediavault-transmissionbt_0.5.18_all.deb) ...
Processing triggers for openmediavault ...
Restarting engine daemon ...
Updating file permissions ...
Updating locale files ...
Setting up transmission-daemon (2.75-1-15~1.gbp4ed609) ...
Starting bittorrent daemon: transmission-daemon.
Setting up openmediavault-transmissionbt (0.5.18) ...
Updating init script links and actions
Stopping bittorrent daemon: transmission-daemon.
Updating configuration
update-rc.d: using dependency based boot sequencing
insserv: warning: current start runlevel(s) (empty) of script `transmission-daemon' overwrites defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `transmission-daemon' overwrites defaults (0 1 6).
Updating configuration
# Add modules section
Updating configuration
# Add modules/filesandlocations section
Updating configuration
# Add modules/bandwidth section
Updating configuration
# Add modules/queuing section
Updating configuration
# Add modules/peer section
Updating configuration
# Add modules/scheduling section
Updating configuration
# Add filesandlocations/paths section
# Add filesandlocations/paths/download section
# Add filesandlocations/paths/incomplete section
# Add filesandlocations/paths/watch section
Stopping enhanced syslogd: rsyslogd.
Starting enhanced syslogd: rsyslogd.
Add debian-transmission user to group: users
Write Config
Updating init script links and actions
Stopping transmission-daemon
Stopping bittorrent daemon: transmission-daemon.
update-rc.d: using dependency based boot sequencing
Processing triggers for openmediavault ...
Restarting engine daemon ...
Updating file permissions ...
insserv: warning: current start runlevel(s) (empty) of script `transmission-daemon' overwrites defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `transmission-daemon' overwrites defaults (0 1 6).
Updating locale files ...
Done ...

I tried running
root@mediafiler:~# apt-get --purge remove transmission-daemon
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
openmediavault-transmissionbt* transmission-daemon*
0 upgraded, 0 newly installed, 2 to remove and 26 not upgraded.
2 not fully installed or removed.
After this operation, 1,034 kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 31340 files and directories currently installed.)
Removing openmediavault-transmissionbt ...
Purging configuration files for openmediavault-transmissionbt ...
Removing transmission-daemon ...
Stopping bittorrent daemon: transmission-daemon.
Purging configuration files for transmission-daemon ...
Processing triggers for openmediavault ...
Restarting engine daemon ...
Updating file permissions ...
Updating locale files ...

it spends a long time on updating locale files (i have no idea what thye are, i'm in australia; we use a metric system with a us keyboard)
on the OMV GUI it's long enough for the omv portal to time out.
in ssh it eventually completes.

[edited becuase i pasted the terminal window a billion times by mistake]

Thanks for all your help David, as advised i did as you suggested, here is the output (i elected to get it to try and reinstall)

root@mediafiler:~# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 26 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up transmission-daemon (2.75-1-15~1.gbp4ed609) ...

Configuration file `/etc/default/transmission-daemon'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** transmission-daemon (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/default/transmission-daemon ...
Starting bittorrent daemon: transmission-daemon[17:58:31.311] JSON parse failed in /var/lib/transmission-daemon/info/settings.json at pos 657: STRAY_TOKEN -- remaining text ",
"incomplete-di"
(warning).
invoke-rc.d: initscript transmission-daemon, action "start" failed.
dpkg: error processing transmission-daemon (--configure):
subprocess installed post-installation script returned error exit status 255
configured to not write apport reports
dpkg: dependency problems prevent configuration of openmediavault-transmissionbt:
openmediavault-transmissionbt depends on transmission-daemon (>= 2.42); however:
Package transmission-daemon is not configured yet.
dpkg: error processing openmediavault-transmissionbt (--configure):
dependency problems - leaving unconfigured
configured to not write apport reports
Errors were encountered while processing:
transmission-daemon
openmediavault-transmissionbt
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@mediafiler:~#

A bit more background about the machine, I don't think it's relevent but i'd like to give you too much information rather than not enough.
The machine is running on a two disk setup. One has the OS and the other holds all the data.
I have a backup.
two months ago my data drive started to die so i replaced it and restored from backup (manually recreating the share in omv then copying the data back).
everything has been fine, and it was only when i noticed that OMV was missing transmission that i tried to install.
missing is probably the wrong word. I'm unsure if it was ever there as about 8 months ago i rebuilt the os side to move to the latest version of OMV.
not sure if this is relevent but thought i'd mention it.

thanks for the advice. it's wierd!
when i log into the webgui of OMV i can see the bittorent service under services.
however when i go to Plugins, the Openmediavault-transmissionbt 0.5.18 is shown as not uinstalled.
when i try to install it i get

Quote

Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 25 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.

and it just hangs, i left it until the gui timed out, i also restarted OMV with nodifference.
I think i may have to manually uninstall it via ssh, but i'm unsure of the command to do that (uninstall, not connect via ssh).

hello,
I'm new to linux but not to computers.
I've enabled the extras repository and installed the bitTorrent plugin via the plugins page within omv.

when i come to configure it, when i open the "Files and Locations" tab i get

Failed to get configuration (xpath=//services/transmissionbt/modules/filesandlocations)


Error #3003:
exception 'OMVException' with message 'Failed to get configuration (xpath=//services/transmissionbt/modules/filesandlocations)' in /usr/share/openmediavault/engined/rpc/transmissionbt.inc:232
Stack trace:
#0 [internal function]: OMVRpcServiceTransmissionBT->getFilesAndLocations(NULL, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(62): OMVRpcServiceAbstract->callMethod('getFilesAndLoca...', NULL, Array)
#3 /usr/sbin/omv-engined(495): OMVRpc::exec('TransmissionBT', 'getFilesAndLoca...', NULL, Array, 1)
#4 {main}


OKHide details

i'm not sure how to fix this and i've googled but nothing similar is jumping out at me.

I also don't appear to have a debian-tranmission group so i just chmod my download folder to 777 but this didn't seem to make a difference.

ah no i havn't. i thought that's what resize would do.
i assume i have to use some sort of boot disk with the ext4 version of partition magic?

if my backup was recent i would go that way for sure.
but the thought of having to find 6 months of certain ahem public domain dvds and tv shows.
not to mention 'some' of my childs photos that arn't on the backup work. just not all of them. I'm not ready to throw them away just yet

i'm trying to work out how to expand the files system now..i think i'm missing something because when i select the drive and choose resize from the filesystem group. it gives me a

Quote

Do you really want to resize the selected filesystem? You have to do that after a RAID has been grown for example.

message, i click yes and nothing happens...

thank you both for your info,
I used clonezilla and went hdd to hdd

unforutnatly it failed, but at least most of the directory structure was copied.
files, while there, don't run. i'm currently overwriting with the files from my backup.

looks like I lost a few pictures from my camera phone that i recently replaced, but other than that i havn't lost too much.

for raid'ing my motherboard only has 2 sata ports, one is used for the OS, also the single pci slot has a gigabit network card in it.

for the expense (of going to raid) it's not really worth it, though i should backup to cold sotrage a bit more often than every 6 months!
live and learn i guess.

thanks again for your help...