Error message too long cannot post in here,
----------
ID: quota_check_no_quotas_96cf22db-14dd-40ae-b917-60e1110dc32e
Function: cmd.run
Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-uuid/96cf22db-14dd-40ae-b917-60e1110dc32e
Result: False
Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-uuid/96cf22db-14dd-40ae-b917-60e1110dc32e" run
Started: 07:22:41.427532
Duration: 50.058 ms
Changes:
----------
pid:
13734
retcode:
1
stderr:
quotacheck: Your kernel probably supports ext4 quota feature but you are using external quota files. Please switch your filesystem to use ext4 quota feature as external quota files on ext4 are deprecated.
quotacheck: Scanning /dev/sdb1 [/srv/dev-disk-by-uuid-96cf22db-14dd-40ae-b917-60e1110dc32e] quotacheck: Checked 16 directories and 43 files
quotacheck: Cannot create new quotafile /srv/dev-disk-by-uuid-96cf22db-14dd-40ae-b917-60e1110dc32e/aquota.user.new: Read-only file system
quotacheck: Cannot initialize IO on new quotafile: Read-only file system
quotacheck: Cannot create new quotafile /srv/dev-disk-by-uuid-96cf22db-14dd-40ae-b917-60e1110dc32e/aquota.group.new: Read-only file system
quotacheck: Cannot initialize IO on new quotafile: Read-only file systemYour drive is Read-Only.
Post each of the outputs inside CODE boxes (symbol </> on the BLUE banner)
cat /etc/fstab
sudo omv-showkey fstab
blkid
lsblk
sudo fdisk -l | grep "Disk "
Will sudden power outage will cause this issue?
What do you think? No electronics component like to be cut out of power without a proper shutdown.
A UPS save a lot of problems.
Onward with the issue:
You didn't post the output of lsblk
Nonetheless, your system is borked. The picture you posted of your FS doesn't match the outputs you posted.
According to the showkey, you only have 2 drives referenced + the rootFS (which is the SDcard) but on the picture, you have the 32Gb drive as VFAT which should be a /dev/mmcblk and NOT a /dev/sdd.
Also, your fstab shows 3x drives that also don't match the showkey output.
Fixing this requires too much back and forth posts which I don't have time for it.
Maybe someone else will be willing to.
Honestly, you'll be better off starting with a fresh install with the drives unplugged.
After OMV is installed and running, power down and reconnect the drives.
All it's needed is to go to the File Systems page and mount them (NOT create)
Alles anzeigenWhat do you think? No electronics component like to be cut out of power without a proper shutdown.
A UPS save a lot of problems.
Onward with the issue:
You didn't post the output of lsblk
Nonetheless, your system is borked. The picture you posted of your FS doesn't match the outputs you posted.
According to the showkey, you only have 2 drives referenced + the rootFS (which is the SDcard) but on the picture, you have the 32Gb drive as VFAT which should be a /dev/mmcblk and NOT a /dev/sdd.
Also, your fstab shows 3x drives that also don't match the showkey output.
Fixing this requires too much back and forth posts which I don't have time for it.
Maybe someone else will be willing to.
Honestly, you'll be better off starting with a fresh install with the drives unplugged.
After OMV is installed and running, power down and reconnect the drives.
All it's needed is to go to the File Systems page and mount them (NOT create)
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-a5509997-df6f-4388-a9b3-d62a33020c9e
sdb 8:16 0 931.5G 0 disk
└─sdb1 8:17 0 931.5G 0 part /srv/dev-disk-by-uuid-96cf22db-14dd-40ae-b917-60e1110dc32e
sdc 8:32 0 465.8G 0 disk
└─sdc1 8:33 0 465.8G 0 part /srv/dev-disk-by-uuid-d779c748-c8a7-4e34-9240-da5c5a3917dc
sdd 8:48 0 465.8G 0 disk
└─sdd1 8:49 0 465.8G 0 part
mmcblk0 179:0 0 29.8G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /boot
└─mmcblk0p2 179:2 0 29.5G 0 part /Alles anzeigenWhat do you think? No electronics component like to be cut out of power without a proper shutdown.
A UPS save a lot of problems.
Onward with the issue:
You didn't post the output of lsblk
Nonetheless, your system is borked. The picture you posted of your FS doesn't match the outputs you posted.
According to the showkey, you only have 2 drives referenced + the rootFS (which is the SDcard) but on the picture, you have the 32Gb drive as VFAT which should be a /dev/mmcblk and NOT a /dev/sdd.
Also, your fstab shows 3x drives that also don't match the showkey output.
Fixing this requires too much back and forth posts which I don't have time for it.
Maybe someone else will be willing to.
Honestly, you'll be better off starting with a fresh install with the drives unplugged.
After OMV is installed and running, power down and reconnect the drives.
All it's needed is to go to the File Systems page and mount them (NOT create)
Will try fresh install without those drives, thanks.
Hopefully can fix
Alles anzeigenWhat do you think? No electronics component like to be cut out of power without a proper shutdown.
A UPS save a lot of problems.
Onward with the issue:
You didn't post the output of lsblk
Nonetheless, your system is borked. The picture you posted of your FS doesn't match the outputs you posted.
According to the showkey, you only have 2 drives referenced + the rootFS (which is the SDcard) but on the picture, you have the 32Gb drive as VFAT which should be a /dev/mmcblk and NOT a /dev/sdd.
Also, your fstab shows 3x drives that also don't match the showkey output.
Fixing this requires too much back and forth posts which I don't have time for it.
Maybe someone else will be willing to.
Honestly, you'll be better off starting with a fresh install with the drives unplugged.
After OMV is installed and running, power down and reconnect the drives.
All it's needed is to go to the File Systems page and mount them (NOT create)
Now able to share drive but smb asked for network credential, it does not work when I entered username and password based on the pi
Still have 500 internal server error when I try to compose docker
Still have 500 internal server error when I try to compose docker
Please, stick to post errors here.
You need to set your time correct first.
Make sure that the time on the GUI is correct.
As for SMB, see the wiki guides because everything is explained there.
I don't use SMB so, can't help you there.
Alles anzeigenPlease, stick to post errors here.
You need to set your time correct first.
Make sure that the time on the GUI is correct.
As for SMB, see the wiki guides because everything is explained there.
I don't use SMB so, can't help you there.
Sorry for the troubles... fixed by multiple times fresh install but SMB still have issue when comes to network credential. Maybe is because of the drives or somehow ...
Feel free to close this thread... thanks for the help.
Sorry for the troubles... fixed by multiple times fresh install but SMB still have issue when comes to network credential. Maybe is because of the drives or somehow ...
Feel free to close this thread... thanks for the help
On the CLI try setting/resetting the SMB password of the user you use for login credentials with the command smbpasswd
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
