From: Nicholas D Steeves <nsteeves@gmail.com>
To: J J <j333111@icloud.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Drive won't mount, please help
Date: Fri, 23 Oct 2020 21:11:37 -0400 [thread overview]
Message-ID: <87sga4ctrq.fsf@DigitalMercury.dynalias.net> (raw)
In-Reply-To: <DFA69BD3-6415-4342-B17D-2CFBF0BED53F@icloud.com>
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
Hi J J,
J J <j333111@icloud.com> writes:
> Thanks again Chris,
>
> Its btrfs-progs 4.7
>
> I spent an hour just trying to figure out how to update it, and still unsuccessful : (
>
> I’m running OMV 4, it’s debian.
>
> Sorry for such noob questions but can you tell me simplest way to update btrfs-progs?
>
OMV 4 appears to be based on Debian 9 (stretch). If it's truly Debian,
then it should be safe to use backports. If you s/buster/stretch/ with
the following instructions you will have access to btrfs-progs 4.20, the
last supported version for stretch-backports.
https://backports.debian.org/Instructions
If you can upgrade to OVM 5, then you can use buster-backports and will
have access to btrfs-progs 5.7 today, and newer versions as they pass
migrate to testing and are then backported to buster (Debian 10).
If you want to try building the buster-backport on OMV 4, try:
dget http://deb.debian.org/debian/pool/main/b/btrfs-progs/btrfs-progs_5.7-1~bpo10+1.dsc
cd btrfs-progs-5.7
apt-get build-dep ./
dpkg-buildpackage -us -uc
but I haven't tested this, and it may not succeed (IIRC you'll need
newer libzstd and other things), and of course it's easier to use recent
live media as Chris Murphy suggested.
Regards,
Nicholas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-10-24 1:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 20:56 Drive won't mount, please help J J
2020-09-14 8:34 ` Qu Wenruo
2020-09-24 22:28 ` J J
2020-09-24 23:14 ` Qu Wenruo
2020-09-26 17:27 ` J J
2020-09-27 0:12 ` Qu Wenruo
2020-09-27 5:43 ` Chris Murphy
2020-10-07 20:31 ` J J
2020-10-10 3:16 ` Chris Murphy
2020-10-13 20:28 ` J J
2020-10-19 4:14 ` Chris Murphy
2020-10-24 1:11 ` Nicholas D Steeves [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sga4ctrq.fsf@DigitalMercury.dynalias.net \
--to=nsteeves@gmail.com \
--cc=j333111@icloud.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox