Hi everyone!!!
I'm new to this forum and impressed as well, because I see so many people involved in openmediavault.
This gave me the courage to install a copy of omv in my machine, which is equipped with a LSI 9260 8i RAID card (among others).
I have installed 3 HDDs of 3TB each in RAID5 and created an ext4 file system.
I copied some files and everything seemed to be ok.
Unfortunetely, after a reboot, the system appeared "degraded". I checked the "faulty" disk. There was any problem.
Just to be safe, I replaced it, rebuilt it, but the file system wasn't mounted.
When I tried to mount it,manually, I received the following message:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount -v --source '/dev/disk/by-label/PRAMATEIA' 2>&1' with exit code '32': mount: mount /dev/sda1 on /srv/dev-disk-by-label-PRAMATEIA failed: Stale file handle in /usr/share/php/openmediavault/system/process.inc:175
Stack trace:
#0 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(720): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(874): OMV\System\Filesystem\Filesystem->mount()
#2 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)
#5 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)
#6 {main}My knowledge about linux is not so good, and my only concern is to avoid losing any data of mine.
Searching the forum, I found some instructions about some "diagnostic" commands.
The results are thefollowing:
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
unused devices: <none>blkid
/dev/sda1: LABEL="PRAMATEIA" UUID="461b0c96-47d8-46e6-bb6a-541b3a4e5b9b" TYPE="ext4" PARTUUID="e4349eba-7ac9-4f50-ac66-223acc4a2509"
/dev/sdb1: UUID="b2e07706-fd72-4c27-9ec2-7f1d968e5bde" TYPE="ext4" PARTUUID="9ad18e86-01"
/dev/sdb5: UUID="e1ed922c-c105-4770-92b3-9cd10be9a91c" TYPE="swap" PARTUUID="9ad18e86-05"fdisk -l | grep "Disk "
Disk /dev/sda: 5.5 TiB, 5999998009344 bytes, 11718746112 sectors
Disklabel type: gpt
Disk identifier: 663A7750-3721-4F9B-A04E-7E86B309EE5F
Disk /dev/sdb: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Disklabel type: dos
Disk identifier: 0x9ad18e86cat /etc/mdadm/mdadm.conf
# 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>
The command: "mdadm --detail --scan --verbose" didn't return any result.
Any help is appreciated.
