From nobody Sat Apr 30 19:22:01 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id F10C41ABB676 for ; Sat, 30 Apr 2022 19:22:13 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp5.goneo.de (smtp5.goneo.de [85.220.129.30]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KrK443shjz3nrB; Sat, 30 Apr 2022 19:22:12 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from hub2.goneo.de (hub2.goneo.de [IPv6:2001:1640:5::8:53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id 0E12B10A1E4C; Sat, 30 Apr 2022 21:22:05 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 5FBBF10A3317; Sat, 30 Apr 2022 21:22:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1651346523; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Fd7Z/eZ/8oj1sBZE7jzq3yQsw0R1tSZLan7ZM7ZufiA=; b=RIpHT2lzAK2zauooezdGz6IYA+TKTEC5pTX3OVJY9/K1rAj5m7MptRUsFIXngyq0ukQc89 hTYS3CZfFV29kBO5zrh/DaOxNI6a+X7ygTnDqNNmqj0iDPLf8aJA246DE6r0od22cQ8MPV /2sLU2eibwcGeIskG4drAE+KBnQBa/m8+aAKqmjGhMah1asfOfpUf7gfhkN9/gFIxIknZb DYNctUZo0Wkroj0EaienVVuF4YGwu0OaUyNV05NPnXUWtv4dxKcOn1pAHavJ0Y5zKxj2wK VRfgFdpT72mF3lBnR/ytl8r5crEgFhy3GARPmaFhnz1lqDoFHP+roIJ30YsVZg== Received: from hermann (dynamic-2a01-0c22-a4ac-f100-1d57-526f-8182-eb64.c22.pool.telefonica.de [IPv6:2a01:c22:a4ac:f100:1d57:526f:8182:eb64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id F151A10A3306; Sat, 30 Apr 2022 21:22:02 +0200 (CEST) Date: Sat, 30 Apr 2022 21:22:01 +0200 From: FreeBSD User To: Alan Somers Cc: Marek Zarychta , FreeBSD CURRENT Subject: Re: ext2fs: WARNING: mount of XXXX denied due to unsupported optional features: needs_recovery Message-ID: <20220430212201.4e234ac4@hermann> In-Reply-To: References: <20220428212145.499a9cdd@hermann> <6648abc2-0ffa-dd88-2767-007ef833869a@plan-b.pwste.edu.pl> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: 9254ae X-Rspamd-UID: 89749e X-Rspamd-Queue-Id: 4KrK443shjz3nrB X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=RIpHT2lz; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 85.220.129.30) smtp.mailfrom=freebsd@walstatt-de.de X-Spamd-Result: default: False [-0.78 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; NEURAL_HAM_MEDIUM(-0.88)[-0.879]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(1.00)[1.000]; NEURAL_HAM_LONG(-1.00)[-0.996]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[walstatt-de.de]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[walstatt-de.de:+]; MLMMJ_DEST(0.00)[freebsd-current]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; RCVD_TLS_ALL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[85.220.129.30:from] X-ThisMailContainsUnwantedMimeParts: N On Thu, 28 Apr 2022 13:36:21 -0600 Alan Somers wrote: > On Thu, Apr 28, 2022 at 1:29 PM Marek Zarychta > wrote: > > > > W dniu 28.04.2022 o 21:21, FreeBSD User pisze: > > > Running XigmaNAS 12.3.0.4.9009 on amd64 hardware, we try to mount HDD to rescue > > > them and store the data on ZFS volumes. Mounting of the HDD doesn't work, FreeBSD > > > 12.3 obviously lack in some etx2 features, namely "needs_recovery". The kernel > > > reports: > > > > > > WARNING: mount of da4p3 denied due to unsupported optional features: > > > needs_recovery > > > > > > How can this problem be solved? > > > > > > Thanks in advance, > > > > > > oh > > > > > Probably as the name of the mailing list suggest you should upgrade to > > 14.0-CURRENT and maybe run fsck.ext2(8) on this partition to fix it. > > > > -- > > Marek Zarychta > > > > You might also try sysutils/fusefs-ext2 from ports. > Hi all, thanks for the response. First of all, I'm bound to FreeBSD 12.3, which is the base for XigmaNAS (used for the ease of use for those colleagues without FreeBSD experience). No clue, when this project will jump over to 13.0 or 13.1. Last time I installed ports on Xigmanas itself and tried to remove those ports, some of the base system essential also got removed - so the system was wrecked. Therefore, I'm planning to try jails and grant access to the jail and try to bind/mount the HDDs in question into the jail for backup - if this task is not an impossible mission on FBSD. Last, but the most problematic issue is: I do not know what the HDDs filesystem in reality really is! There is an EFI partition (FAT32), there is a second one, fstyp report unknown and here is the large partition identified as ext2fs by fstyp. But I think he former administration in the department used LVM on the more recent Linux boxes, so I might have to deal with that also. Kind regards, O. Hartmann Another issue on several of those HDDs in question seems to be