-
6.12.0-rc2 - ZFS - encrypted results in "Unsupported or no file system".
I had some issues and asked for help on Discord. My issue did not get resolved and i ended up not going zfs. I want to post whatever i got here since someone mentioned it after i moved on. I run a completely new system with reinstalled USB. I tried to assign zfs - encryption to all drives. All gives the "Unmountable: Unsupported or no file system". I tried restarting, taking array off an on, Unassigned Devices plugin and pressed the red x to remove partitions, doing it all again in every different way. Nothing worked so i ended up going with xfs and btrfs. Here's the log for one of the drives it tried to fromat and mount. Mar 26 09:02:33 Boxen kernel: mdcmd (36): nocheck pause Mar 26 09:02:35 Boxen emhttpd: creating volume: disk1 (zfs - encrypted) Mar 26 09:02:35 Boxen emhttpd: shcmd (281): /sbin/wipefs -a /dev/sdc Mar 26 09:02:36 Boxen root: /dev/sdc: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54 Mar 26 09:02:36 Boxen root: /dev/sdc: 8 bytes were erased at offset 0x3a3817d5e00 (gpt): 45 46 49 20 50 41 52 54 Mar 26 09:02:36 Boxen root: /dev/sdc: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa Mar 26 09:02:36 Boxen root: /dev/sdc: calling ioctl to re-read partition table: Success Mar 26 09:02:36 Boxen emhttpd: writing GPT on disk (sdc), with partition 1 byte offset 32KiB, erased: 0 Mar 26 09:02:36 Boxen emhttpd: shcmd (282): sgdisk -Z /dev/sdc Mar 26 09:02:37 Boxen root: Creating new GPT entries in memory. Mar 26 09:02:37 Boxen root: GPT data structures destroyed! You may now partition the disk using fdisk or Mar 26 09:02:37 Boxen root: other utilities. Mar 26 09:02:37 Boxen emhttpd: shcmd (283): sgdisk -o -a 8 -n 1:32K:0 /dev/sdc Mar 26 09:02:38 Boxen root: Creating new GPT entries in memory. Mar 26 09:02:38 Boxen root: The operation has completed successfully. Mar 26 09:02:38 Boxen kernel: sdc: sdc1 Mar 26 09:02:38 Boxen emhttpd: shcmd (284): udevadm settle Mar 26 09:02:38 Boxen emhttpd: shcmd (285): /usr/sbin/cryptsetup luksClose md1p1 Mar 26 09:02:38 Boxen emhttpd: shcmd (287): /usr/sbin/cryptsetup luksFormat /dev/md1p1 Mar 26 09:02:44 Boxen emhttpd: shcmd (290): /usr/sbin/cryptsetup luksOpen /dev/md1p1 md1p1 Mar 26 09:02:47 Boxen emhttpd: shcmd (291): modprobe zfs Mar 26 09:02:47 Boxen emhttpd: shcmd (292): /usr/sbin/zpool create -f -o ashift=12 -o autotrim=off -O compression=off -O dnodesize=auto -O acltype=posixacl -O xattr=sa -O normalization=formD -m /mnt/disk1 disk1 /dev/mapper/md1p1 Mar 26 09:02:47 Boxen emhttpd: shcmd (293): /usr/sbin/zpool export disk1 Mar 26 09:02:47 Boxen emhttpd: mounting /mnt/disk1 Mar 26 09:02:47 Boxen emhttpd: shcmd (294): mkdir -p /mnt/disk1 Mar 26 09:02:47 Boxen emhttpd: shcmd (295): modprobe zfs Mar 26 09:02:47 Boxen emhttpd: /usr/sbin/zpool import -d /dev/mapper/md1p1 2>&1 Mar 26 09:02:47 Boxen emhttpd: pool: disk1 Mar 26 09:02:47 Boxen emhttpd: id: 6556196458859304560 Mar 26 09:02:47 Boxen emhttpd: shcmd (296): /usr/sbin/zpool import -N -o autoexpand=on -d /dev/mapper/md1p1 6556196458859304560 disk1 Mar 26 09:02:48 Boxen emhttpd: shcmd (297): /usr/sbin/zpool online -e disk1 /dev/mapper/md1p1 Mar 26 09:02:48 Boxen emhttpd: /usr/sbin/zpool status -LP disk1 2>&1 Mar 26 09:02:48 Boxen emhttpd: pool: disk1 Mar 26 09:02:48 Boxen emhttpd: state: ONLINE Mar 26 09:02:48 Boxen emhttpd: config: Mar 26 09:02:48 Boxen emhttpd: NAME STATE READ WRITE CKSUM Mar 26 09:02:48 Boxen emhttpd: disk1 ONLINE 0 0 0 Mar 26 09:02:48 Boxen emhttpd: /dev/dm-0 ONLINE 0 0 0 Mar 26 09:02:48 Boxen emhttpd: errors: No known data errors Mar 26 09:02:48 Boxen emhttpd: disk1: invalid config: 0 1 Mar 26 09:02:48 Boxen emhttpd: shcmd (298): /usr/sbin/zpool export disk1 Mar 26 09:02:48 Boxen emhttpd: /mnt/disk1 mount error: Unsupported or no file system Mar 26 09:02:48 Boxen emhttpd: shcmd (299): rmdir /mnt/disk1
-
[Support] SpaceinvaderOne Deconz
Any luck with this? I have currently been using the marthoc/deconz container but i tried the spaceinvaderone one and got the "Couldnt get API"-error. Tried to fix it but figured it was the container that tdidnt work since it worked when i switched back to Marthoc one. However, the docker stopped due to some kind of USB error. Maybe mount error or wahtever, so i tried recreating the docker but it dissapeard totally. I readded it and configured it some and got Phoscon running and it shows version and firmware but now i also get this API Key error on this contianer. I have no idea whats up with that.
mituv85
Members
-
Joined
-
Last visited