I use zfs on linux for more than 1 year without issues.
Posts by fumantsu
-
-
I think I found a small bug. I download the netinst for Wheezy and it didn't download the current version but the first (20130430 instead of 20130613+deb7u3). The result is that the modules that come from the mirror was different kernel version and in a Virtualbox VM (probably is more wider the effect) couldn't be loaded.
I think a good idea would be the ability to edit the entries in Images. Differently @davidh2k has to update frequently the links.
-
Is it global sshkey or for root?
-
Good day,
I want to ask what is the meaning of this page.
-
I got installed after 3 times (once I had warnings from dpkg) and with unstable enabled. So.... solved
-
True. I got installed the qbittorrent from unstable. I don't remember something to had with python but I can't be 100% sure. The whole installation I done it very manually package by package trying not to mix to much the system.
-
Code
Display More# # deb cdrom:[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150108-14:12]/ wheezy contrib main non-free # deb cdrom:[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150108-14:12]/ wheezy contrib main non-free deb http://ftp.cvut.cz/debian/ wheezy main deb-src http://ftp.cvut.cz/debian/ wheezy main deb http://security.debian.org/ wheezy/updates main contrib non-free deb-src http://security.debian.org/ wheezy/updates main contrib non-free # wheezy-updates, previously known as 'volatile' deb http://ftp.cvut.cz/debian/ wheezy-updates main contrib non-free deb-src http://ftp.cvut.cz/debian/ wheezy-updates main contrib non-free #deb http://ftp.cvut.cz/debian/ unstable mainCode
Display Moredeb http://ftp.debian.org/debian wheezy-backports main contrib non-free deb http://packages.omv-extras.org/debian/ stoneburner-backports main deb http://ftp.debian.org/debian wheezy-backports main contrib non-free deb http://packages.omv-extras.org/debian/ kralizec-backports main # Custom repos # Custom repos # Regular omv-extras.org repo deb http://packages.omv-extras.org/debian/ kralizec main # miller repo deb http://dh2k.omv-extras.org/debian/ kralizec-miller main deb http://ppa.launchpad.net/deluge-team/ppa/ubuntu precise main # ZFS repo deb http://packages.omv-extras.org/debian/ kralizec-zfs main deb http://archive.zfsonlinux.org/debian wheezy main # ZFS testing repo deb http://packages.omv-extras.org/debian/ kralizec-zfs-testing main # Regular omv-extras.org repo deb http://packages.omv-extras.org/debian/ stoneburner main # Testing omv-extras.org repo deb http://packages.omv-extras.org/debian/ stoneburner-testing main # miller repo deb http://dh2k.omv-extras.org/debian/ stoneburner-miller main deb http://ppa.launchpad.net/deluge-team/ppa/ubuntu precise main # ZFS repo deb http://packages.omv-extras.org/debian/ stoneburner-zfs main deb http://archive.zfsonlinux.org/debian wheezy main # ZFS testing repo deb http://packages.omv-extras.org/debian/ stoneburner-zfs-testing main # mono-project repo deb http://packages.omv-extras.org/debian/ stoneburner-mono main deb http://download.mono-project.com/repo/debian wheezy main deb http://packages.openmediavault.org/public stoneburner main # deb http://downloads.sourceforge.net/project/openmediavault/packages stoneburner main ## Uncomment the following line to add software from the proposed repository. # deb http://packages.openmediavault.org/public stoneburner-proposed main # deb http://downloads.sourceforge.net/project/openmediavault/packages stoneburner-proposed main ## This software is not part of OpenMediaVault, but is offered by third-party ## developers as a service to OpenMediaVault users. # deb http://packages.openmediavault.org/public stoneburner partner # deb http://downloads.sourceforge.net/project/openmediavault/packages stoneburner partner deb http://packages.openmediavault.org/public kralizec main # deb http://downloads.sourceforge.net/project/openmediavault/packages kralizec main ## This software is not part of OpenMediaVault, but is offered by third-party ## developers as a service to OpenMediaVault users. deb http://packages.openmediavault.org/public kralizec partner # deb http://downloads.sourceforge.net/project/openmediavault/packages kralizec partner deb file:/var/cache/openmediavault/archives / -
The following packages have unmet dependencies:
python-gtk2 : Depends: python-numpy (>= 1:1.6.1) but it is not going to be installed
Depends: python-numpy-abi9
E: Unable to correct problems, you have held broken packages.python-numpy:
Installed: (none)
Candidate: 1:1.6.2-1.2
Version table:
1:1.6.2-1.2 0
400 http://ftp.cvut.cz/debian/ wheezy/main amd64 PackagesThe following packages have unmet dependencies:
python-numpy : Depends: libblas3 but it is not going to be installed or
libblas.so.3 or
libatlas3-base but it is not going to be installed
Depends: libgfortran3 (>= 4.3) but it is not going to be installed
Depends: liblapack3 but it is not going to be installed or
liblapack.so.3 or
libatlas3-base but it is not going to be installed
E: Unable to correct problems, you have held broken packages. -
I'm meaning by apt-get install calibre
python-gtk2:
Installed: (none)
Candidate: 2.24.0-3+b1
Version table:
2.24.0-3+b1 0
400 http://ftp.cvut.cz/debian/ wheezy/main amd64 Packages -
python-poppler:
Installed: (none)
Candidate: 0.12.1-8+b1
Version table:
0.12.1-8+b1 0
400 http://ftp.cvut.cz/debian/ wheezy/main amd64 Packagesand if I'm trying to install it
The following packages have unmet dependencies:
python-poppler : Depends: python-gtk2 (>= 2.10.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.I made a apt-cache clean, nothing.
If I try to install calibre directly, it seems to work (I didn't proceed but I didn't get error message)
-
Hi,
I'm trying to install the plugin and I'm getting this:
Reading package lists...
Building dependency tree...
Reading state information...>>> *************** Error ***************
Failed to execute command 'export LANG=C; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --force-yes --fix-missing --allow-unauthenticated --reinstall install openmediavault-calibre 2>&1': Reading package lists...Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:The following packages have unmet dependencies:
openmediavault-calibre : Depends: python-poppler but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
<<< *************************************System is running OMV 2.18. Any help?
-
-
Today, I had different error message:
/etc/cron.weekly/openmediavault-update-smart-drivedb:Updating smartmontools drive database .../tmp/tmp.mCC69edTik: download from trunk failed (HTTP error)
Internet was working for sure (email...)
-
From time to time I'm getting this errors on the smartmontools email (not always)
/etc/cron.weekly/openmediavault-update-smart-drivedb:Updating smartmontools drive database ...grep: /usr/share/smartmontools/drivedb.h.new: No such file or directorycmp: EOF on /usr/share/smartmontools/drivedb.h.new/usr/share/smartmontools/drivedb.h updated from branches/RELEASE_5_41_DRIVEDB
I wonder if there is something to do to fix it.
-
The cron file is installed by default by the mdadm Debian package. Delete the cron job file if you do not want it.
I check that there are two crons for mdadm. One is "mdadm" and one is "openmediavault-mdadm"
-
What is the output of:
cat /etc/mdadm/mdadm.conf
fdisk -lCode
Display More# mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # definitions of existing MD arrays Disk /dev/sdc: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 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 identifier: 0x00000000 Disk /dev/sdc doesn't contain a valid partition table Disk /dev/sde: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 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 identifier: 0xad28ad28 Device Boot Start End Blocks Id System Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 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 identifier: 0x00000000 Disk /dev/sdb doesn't contain a valid partition table Disk /dev/sdd: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 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 identifier: 0xad91ad91 Device Boot Start End Blocks Id System Disk /dev/sda: 32.0 GB, 32017047552 bytes 255 heads, 63 sectors/track, 3892 cylinders, total 62533296 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 identifier: 0x000589d9 Device Boot Start End Blocks Id System /dev/sda1 1 23439359 11719679+ 83 Linux /dev/sda2 23439360 31250431 3905536 82 Linux swap / Solaris WARNING: GPT (GUID Partition Table) detected on '/dev/zd0'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/zd0: 343.6 GB, 343597383680 bytes 256 heads, 63 sectors/track, 41610 cylinders, total 671088640 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 8192 bytes I/O size (minimum/optimal): 8192 bytes / 8192 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/zd0p1 1 671088639 335544319+ ee GPT Partition 1 does not start on physical sector boundary. Disk /dev/zd0p1: 343.6 GB, 343596318208 bytes 16 heads, 63 sectors/track, 665760 cylinders, total 671086559 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 8192 bytes I/O size (minimum/optimal): 8192 bytes / 8192 bytes Disk identifier: 0x00000000 Disk /dev/zd0p1 doesn't contain a valid partition table # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # definitions of existing MD arrays# mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # definitions of existing MD arrays# mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # definitions of existing MD arrays -
Why should not be compatible? If you want to have it as boot disk more possible is to have compatibility issues with your MB than with the OS.
-
Good day,
I notice that from the moment that upgrade to 2.0 I have started to receive cron emails about mdadm.
/etc/cron.daily/mdadm:mdadm: No mail address or alert command - not monitoring.run-parts: /etc/cron.daily/mdadm exited with return code 1
The funny is that I don't have mdadm working (I use ZFS) and I don't have enable the software RAID in the notifications. I tried to enable/disable again but no luck.
-
-
Good day,
Any guide how to correctly setup this plugin? I'm not so familiar with syslinux and basically I need to test pxe boot for Windows 7 and 8 (I'm aware from other guides that I need to setup some PE iso images)