• PROXMOX 3.4 при разбивке диска boot раздел создает в fat32, как сделать в ext3?

    @matrix_ekb Автор вопроса
    gep2005: Спасибо за ссылку, почитаю. Пока поднял debian+soft raid и накатил сверху proxmox. Все вроде работает.
  • PROXMOX 3.4 при разбивке диска boot раздел создает в fat32, как сделать в ext3?

    @matrix_ekb Автор вопроса
    что то не вышло:
    mkfs.ext3 /dev/md1
    я сделал
    mkfs.vfat /dev/md1
    и в этом месте, при редактировании fstab вместо
    /dev/md1 /boot ext3 defaults 0 1
    сделал
    /dev/md1 /boot vfat defaults 0 1
    После ребута получил вот это:

    Setting parameters of disc: (none).
    Tue Apr 21 23:24:31 2015: Activating swap...done.
    Tue Apr 21 23:24:31 2015: Checking root file system...fsck from util-linux 2.20.1
    Tue Apr 21 23:24:31 2015: /dev/mapper/pve-root: clean, 42454/6291456 files, 681123/25165824 blocks
    Tue Apr 21 23:24:31 2015: done.
    Tue Apr 21 23:24:31 2015: Loading kernel module fuse.
    Tue Apr 21 23:24:31 2015: Loading kernel module raid.
    Tue Apr 21 23:24:31 2015: FATAL: Module raid not found.
    Tue Apr 21 23:24:31 2015: Loading kernel module raid1.
    Tue Apr 21 23:24:31 2015: Generating udev events for MD arrays...done.
    Tue Apr 21 23:24:31 2015: Cleaning up temporary files... /tmp.
    Tue Apr 21 23:24:31 2015: Setting up LVM Volume Groups...  WARNING: Duplicate VG name pve: Existing nrCU0S-Qkvp-EbQy-AB3W-Rcbp-926l-UI4kR$
    Tue Apr 21 23:24:32 2015:   WARNING: Duplicate VG name pve: Existing nrCU0S-Qkvp-EbQy-AB3W-Rcbp-926l-UI4kRM (created here) takes preceden$
    Tue Apr 21 23:24:32 2015:   WARNING: Duplicate VG name pve: Existing nrCU0S-Qkvp-EbQy-AB3W-Rcbp-926l-UI4kRM (created here) takes preceden$
    Tue Apr 21 23:24:32 2015:   WARNING: Duplicate VG name pve: Existing nrCU0S-Qkvp-EbQy-AB3W-Rcbp-926l-UI4kRM (created here) takes preceden$
    Tue Apr 21 23:24:32 2015:   WARNING: Duplicate VG name pve: Existing xlKpDe-kLA6-80tI-4Cif-GD77-KccP-G5SwBH (created here) takes preceden$
    Tue Apr 21 23:24:32 2015:   device-mapper: create ioctl on pve-root failed: Device or resource busy
    Tue Apr 21 23:24:32 2015:   WARNING: Duplicate VG name pve: Existing nrCU0S-Qkvp-EbQy-AB3W-Rcbp-926l-UI4kRM (created here) takes preceden$
    Tue Apr 21 23:24:32 2015:   device-mapper: create ioctl on pve-swap failed: Device or resource busy
    Tue Apr 21 23:24:32 2015:   device-mapper: create ioctl on pve-data failed: Device or resource busy
    Tue Apr 21 23:24:32 2015: failed.
    Tue Apr 21 23:24:32 2015: Activating lvm and md swap...done.
    Tue Apr 21 23:24:32 2015: Checking file systems...fsck from util-linux 2.20.1
    Tue Apr 21 23:24:32 2015: /dev/mapper/pve-data: clean, 20/52723712 files, 3359370/210865152 blocks
    Tue Apr 21 23:24:32 2015: fsck.ext3: Bad magic number in super-block while trying to open /dev/md1
    Tue Apr 21 23:24:32 2015: /dev/md1:
    Tue Apr 21 23:24:32 2015: The superblock could not be read or does not describe a correct ext2
    Tue Apr 21 23:24:32 2015: filesystem.  If the device is valid and it really contains an ext2
    Tue Apr 21 23:24:32 2015: filesystem (and not swap or ufs or something else), then the superblock
    Tue Apr 21 23:24:32 2015: is corrupt, and you might try running e2fsck with an alternate superblock:
    Tue Apr 21 23:24:32 2015:     e2fsck -b 8193 <device>
    Tue Apr 21 23:24:32 2015:
    Tue Apr 21 23:24:32 2015: fsck died with exit status 8
    Tue Apr 21 23:24:32 2015: failed (code 8).
    Tue Apr 21 23:24:32 2015: File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please re$
    Tue Apr 21 23:24:32 2015: A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... (warni$
    Tue Apr 21 23:24:32 2015: Give root password for maintenance
    Tue Apr 21 23:24:32 2015: (or type Control-D to continue):