After you have created the file system have you tried to select the drive and mount it?
You cannot use disks not formatted.
In "Storage" -> "Disks" you have to select the disk then click on "Reset to factory" (on OMV6); WARNING: All data will be permanently erased.
After this, you can select the disk and make a new file system.
p.s.: very important that disks are full of data that I don't want to lose
I don't get it: you have DATA on the drives?
Then you click + and Mount. NOT create
I think you need to start from the top:
You say you have 6 drives and they have DATA.
Where were they connected and how?
What filesystem do they have? Besides beeing ext4, were they on some RAID system? Any particular special setup you had on them (SnapRAID, for eg) ?
How and what are you running now? How are the drives attached to the system? And what kind of system?
Some outputs on the CLI can also show better info on what is going on:
Install tree with apt install tree
tree /dev/disk/by-*
cat /etc/fstab
lsblk
blkid
fdisk -l | grep sd
Alles anzeigenI think you need to start from the top:
You say you have 6 drives and they have DATA.
Where were they connected and how?
What filesystem do they have? Besides beeing ext4, were they on some RAID system? Any particular special setup you had on them (SnapRAID, for eg) ?
How and what are you running now? How are the drives attached to the system? And what kind of system?
Some outputs on the CLI can also show better info on what is going on:
Install tree with apt install tree
tree /dev/disk/by-*
cat /etc/fstab
lsblk
blkid
fdisk -l | grep sd
First of all thanks for the help,
Yes, I've 6 drives ( see disks.png ), all full of my files ( /sdc1 is system drive ).
They all come from a very old installation of omv1.
Now i'm still in the same pc, but i formatted the system disk and i installed Omv6
Here outputs:
tree /dev/disk/by-*
dev/disk/by-id
├── ata-KINGSTON_SH103S3120G_50026B7239044482 -> ../../sdc
├── ata-KINGSTON_SH103S3120G_50026B7239044482-part1 -> ../../sdc1
├── ata-KINGSTON_SH103S3120G_50026B7239044482-part2 -> ../../sdc2
├── ata-KINGSTON_SH103S3120G_50026B7239044482-part5 -> ../../sdc5
├── ata-SAMSUNG_HD103UJ_S13PJDWQA13822 -> ../../sdd
├── ata-SAMSUNG_HD103UJ_S13PJDWQA13822-part1 -> ../../sdd1
├── ata-WDC_WD10EACS-07D6B1_WD-WCAU47161702 -> ../../sda
├── ata-WDC_WD10EACS-07D6B1_WD-WCAU47161702-part1 -> ../../sda1
├── ata-WDC_WD10EACS-07D6B1_WD-WCAU47161755 -> ../../sdf
├── ata-WDC_WD10EACS-07D6B1_WD-WCAU47161755-part1 -> ../../sdf1
├── ata-WDC_WD20EADS-00R6B0_WD-WCAVY0168723 -> ../../sdb
├── ata-WDC_WD20EADS-00R6B0_WD-WCAVY0168723-part1 -> ../../sdb1
├── ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M2724078 -> ../../sde
├── ata-WDC_WD20EFRX-68EUZN0_WD-WCC4M2724078-part1 -> ../../sde1
├── wwn-0x50000f0000817e0d -> ../../sdd
├── wwn-0x50000f0000817e0d-part1 -> ../../sdd1
├── wwn-0x50014ee202792dd5 -> ../../sdf
├── wwn-0x50014ee202792dd5-part1 -> ../../sdf1
├── wwn-0x50014ee2ad2421fd -> ../../sda
├── wwn-0x50014ee2ad2421fd-part1 -> ../../sda1
├── wwn-0x50014ee2ad5473f7 -> ../../sdb
├── wwn-0x50014ee2ad5473f7-part1 -> ../../sdb1
├── wwn-0x50014ee2b4c78675 -> ../../sde
├── wwn-0x50014ee2b4c78675-part1 -> ../../sde1
├── wwn-0x50026b7239044482 -> ../../sdc
├── wwn-0x50026b7239044482-part1 -> ../../sdc1
├── wwn-0x50026b7239044482-part2 -> ../../sdc2
└── wwn-0x50026b7239044482-part5 -> ../../sdc5
/dev/disk/by-label
└── dati2015 -> ../../sde1
/dev/disk/by-partuuid
├── 97447e97-101c-419e-b477-b04fbd5be33e -> ../../sdd1
├── 9880e211-a638-4a07-8051-40df1c407b10 -> ../../sda1
├── c7464c2b-01 -> ../../sdc1
├── c7464c2b-02 -> ../../sdc2
├── c7464c2b-05 -> ../../sdc5
└── ce0ad713-8360-4198-9438-346afa103c4b -> ../../sde1
/dev/disk/by-path
├── pci-0000:00:1f.2-ata-1 -> ../../sdd
├── pci-0000:00:1f.2-ata-1.0 -> ../../sdc
├── pci-0000:00:1f.2-ata-1.0-part1 -> ../../sdc1
├── pci-0000:00:1f.2-ata-1.0-part2 -> ../../sdc2
├── pci-0000:00:1f.2-ata-1.0-part5 -> ../../sdc5
├── pci-0000:00:1f.2-ata-1.1 -> ../../sdd
├── pci-0000:00:1f.2-ata-1.1-part1 -> ../../sdd1
├── pci-0000:00:1f.2-ata-1-part1 -> ../../sdd1
├── pci-0000:00:1f.2-ata-1-part2 -> ../../sdc2
├── pci-0000:00:1f.2-ata-1-part5 -> ../../sdc5
├── pci-0000:00:1f.2-ata-2 -> ../../sdf
├── pci-0000:00:1f.2-ata-2.0 -> ../../sde
├── pci-0000:00:1f.2-ata-2.0-part1 -> ../../sde1
├── pci-0000:00:1f.2-ata-2.1 -> ../../sdf
├── pci-0000:00:1f.2-ata-2.1-part1 -> ../../sdf1
├── pci-0000:00:1f.2-ata-2-part1 -> ../../sde1
├── pci-0000:04:01.0-ata-1 -> ../../sda
├── pci-0000:04:01.0-ata-1.0 -> ../../sda
├── pci-0000:04:01.0-ata-1.0-part1 -> ../../sda1
├── pci-0000:04:01.0-ata-1-part1 -> ../../sda1
├── pci-0000:04:01.0-ata-2 -> ../../sdb
├── pci-0000:04:01.0-ata-2.0 -> ../../sdb
├── pci-0000:04:01.0-ata-2.0-part1 -> ../../sdb1
└── pci-0000:04:01.0-ata-2-part1 -> ../../sdb1
/dev/disk/by-uuid
├── 059c9f97-3f9d-4181-a0aa-c590f485e8cc -> ../../sdc5
├── 2f762ba8-1bf4-4df0-bca0-889818769978 -> ../../sdc1
├── 4dae5952-7e7d-49de-af1b-a6d35dd57295 -> ../../sda1
├── 8728a0d9-aa82-4e96-8f3b-3c625d8480bb -> ../../sde1
└── a8b62c6e-2131-451a-9edb-bc6db14f294b -> ../../sdd1
0 directories, 64 filescat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=2f762ba8-1bf4-4df0-bca0-889818769978 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=059c9f97-3f9d-4181-a0aa-c590f485e8cc none swap sw 0 0
# >>> [openmediavault]
/dev/disk/by-uuid/4dae5952-7e7d-49de-af1b-a6d35dd57295 /srv/dev-disk-by-uuid-4dae5952-7e7d-49de-af1b-a6d35dd57295 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/8728a0d9-aa82-4e96-8f3b-3c625d8480bb /srv/dev-disk-by-uuid-8728a0d9-aa82-4e96-8f3b-3c625d8480bb ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/a8b62c6e-2131-451a-9edb-bc6db14f294b /srv/dev-disk-by-uuid-a8b62c6e-2131-451a-9edb-bc6db14f294b ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
# <<< [openmediavault]lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931,5G 0 disk
└─sda1 8:1 0 931,5G 0 part /srv/dev-disk-by-uuid-4dae5952-7e7d-49de-af1b-a6d35dd57295
sdb 8:16 0 1,8T 0 disk
└─sdb1 8:17 0 1,8T 0 part
sdc 8:32 0 111,8G 0 disk
├─sdc1 8:33 0 110,8G 0 part /
├─sdc2 8:34 0 1K 0 part
└─sdc5 8:37 0 975M 0 part [SWAP]
sdd 8:48 0 931,5G 0 disk
└─sdd1 8:49 0 931,5G 0 part /srv/dev-disk-by-uuid-a8b62c6e-2131-451a-9edb-bc6db14f294b
sde 8:64 0 1,8T 0 disk
└─sde1 8:65 0 1,8T 0 part /srv/dev-disk-by-uuid-8728a0d9-aa82-4e96-8f3b-3c625d8480bb
sdf 8:80 0 931,5G 0 disk
└─sdf1 8:81 0 931,5G 0 part blkid
/dev/sdd1: UUID="a8b62c6e-2131-451a-9edb-bc6db14f294b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="97447e97-101c-419e-b477-b04fbd5be33e"
/dev/sdc1: UUID="2f762ba8-1bf4-4df0-bca0-889818769978" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c7464c2b-01"
/dev/sdc5: UUID="059c9f97-3f9d-4181-a0aa-c590f485e8cc" TYPE="swap" PARTUUID="c7464c2b-05"
/dev/sda1: UUID="4dae5952-7e7d-49de-af1b-a6d35dd57295" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9880e211-a638-4a07-8051-40df1c407b10"
/dev/sde1: LABEL="dati2015" UUID="8728a0d9-aa82-4e96-8f3b-3c625d8480bb" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ce0ad713-8360-4198-9438-346afa103c4b"
fdisk -l | grep sd
Disk /dev/sdb: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdb1 2048 3907029134 3907027087 1,8T Linux filesystem
Disk /dev/sdd: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
/dev/sdd1 2048 1953523711 1953521664 931,5G Microsoft basic data
Disk /dev/sdc: 111,79 GiB, 120034123776 bytes, 234441648 sectors
/dev/sdc1 * 2048 232441855 232439808 110,8G 83 Linux
/dev/sdc2 232443902 234440703 1996802 975M 5 Extended
/dev/sdc5 232443904 234440703 1996800 975M 82 Linux swap / Solaris
Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
/dev/sda1 2048 1953523711 1953521664 931,5G Microsoft basic data
Disk /dev/sde: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sde1 2048 3907029134 3907027087 1,8T Linux filesystem
Disk /dev/sdf: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
/dev/sdf1 2048 1953525134 1953523087 931,5G Linux filesystem/dev/sdd1 2048 1953523711 1953521664 931,5G Microsoft basic data
/dev/sda1 2048 1953523711 1953521664 931,5G Microsoft basic data
Your partitions don't add up on fdisk: it says Microsoft basic data but on the GUI, it's mounted as ext4.
And, again DO NOT TRY TO CREATE fs on drives that already have data. I really hope it didn't screw up the partition header.
They weren't recognized in the first place properly and know it's scrambled.
If you can, boot up a live CD (Gparted, Clonezilla, SystemRescue, etc) and see if it shows ALL drives.
If it does, shutdown and unplug ALL drives except the OS drive.
Reinstall Debian/OMV.
Plug only 1 drive to the system and boot up. Check if you see it and MOUNT it on the GUI.
Shutdown and plug the 2nd one. Do the same as above.
Once a drive doesn't show up or is unable to MOUNT, put it aside and continue with the rest.
Then we'll try to figure out what's the issues with those failing drive's
And, again DO NOT TRY TO CREATE fs on drives that already have data.
...... already done .... I hope nothing has changed ....
If you can, boot up a live CD (Gparted, Clonezilla, SystemRescue, etc) and see if it shows ALL drives.
If it does, shutdown and unplug ALL drives except the OS drive.
I don't know why, but Gparted live after configuration windows, don't start.
I try to use Gparted on Ubuntu in other pc to see file system of all drivers
Plug only 1 drive to the system and boot up. Check if you see it and MOUNT it on the GUI.
Shutdown and plug the 2nd one. Do the same as above.
Once a drive doesn't show up or is unable to MOUNT, put it aside and continue with the rest.
ok, all done, step by step.
2 drivers has a problems to mount.
I don't know if reset or not ...... 
Run and post the same commands of #8 with just the working drives attached.
And, I hope you do have a backup of the DATA on the drives that fail.
ext4 is one of the most mature and robust filesystem on Linux. Whatever you experienced it is not related to the filesystem type.
Be aware that BTRFS needs some maintenance, i.e scrub and balancing.
Most users would select BTRFS over ext4 for its additional features, which you will probably not use.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
