Hi !
Is there an "Open Media Vault" sticker to stick on the front of the case ?
Doesn't it have a merchandising section ?
Thanks
Hi !
Is there an "Open Media Vault" sticker to stick on the front of the case ?
Doesn't it have a merchandising section ?
Thanks
Good news !
The nas was plugged into a first price UPS back-up power from amazon.
It was the UPS back-up power that no longer worked well and the hard drives could no longer start.
By plugging the nas directly into a power outlet, the hard drives are recognized in the bios, the RAID5 is detected in the admin GUI and all the data is present from Windows !
I am relieved !
Thanks a lot for your help !
IF they are seen in the bios and to do that you will have to restart the server, that reboot may bring them back up for OMV to see them.
I will try that. Thanks a lot !
I would say the possibility is the m'board, if the board has a bios are the drives seen/located in there, if they are then it's probably related to your OMV system being corrupted, if they can't be seen then it's quite possibly m'board related.
Ok, I'll look in the bios if the hard drives are detected. If they are detected in the bios, but not in OMV, what should I do?
I so hope it's the power supply or the PCB that's the problem.
(With apologies to geaves for butting in.)
??? Do you have an add-on JBOD or RAID card?
(Usually, for up to four drives, hard drives are plugged directly into the motherboard.)Did the chassis come with a power supply? Did you check the 12V supply
The sata cables are connected to the motherboard and on the other side, to a PCB card which is powered by the power supply (molex connector) and the hard disks are connected and powered by this PCB card.
I haven't RAID card. It's just a sata motherboard RAID.
Yes, the chassis come with a power supply (1U factor brand Enhance).
Well the pictures tell the story the drives are missing, OMV can't see them so until you can resolve that you can't sort the array
Okay, thanks.
Is it possible that the problem comes from the electronic card that connects the hard drives to the chassis ?
I can understand on 4 hard drives having a failure, but that the 4 hard drives are no longer seen by the system at all is not normal.
The chassis is a chinese case like a QNAP with standard ITX format.
That's not good at this moment I've no idea how to proceed, the blkid output shows no drives as does fdisk, in the GUI are the drives displayed in storage -> disks
The problem is the output is not seeing any of the drives + the email places (F) next to /dev/sd[abc] this would suggest that these drives have failed
Try the output mdadm --query --detail /dev/md0
So my disks are dead and my data lost ?
It's incredible, all the material is not even 2 years old...
Hello !
I'm panicked, I just got an email alert from my nas OMV 6.
I no longer see my RAID 5 and data.
The email message says:
This is an automatically generated mail message from mdadm
running on NASOMV
A Fail event had been detected on md device /dev/md0.
It could be related to component device /dev/sdd.
Faithfully yours, etc.
P.S. The /proc/mdstat file currently contains the following:
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md0 : active raid5 sdb[1](F) sda[0](F) sdc[2](F)
29298914304 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/0] [____]
bitmap: 0/73 pages [0KB], 65536KB chunk
unused devices: <none>
Alles anzeigen
# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
unused devices: <none>
# blkid
/dev/nvme0n1p1: LABEL="512Go" UUID="519ef04c-2f30-4eb3-8925-68ec3fe13e34" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="86b061fb-c9da-47cb-871b-86c8385c13bb"
/dev/nvme1n1p1: UUID="e714394a-0aea-4eff-84d7-d709ef085358" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="21023d25-01"
/dev/nvme1n1p5: UUID="5fc35304-0437-4676-894d-3b54e8907af0" TYPE="swap" PARTUUID="21023d25-05"
# fdisk -l | grep "Disk "
Disk /dev/nvme0n1: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: NE-512
Disk identifier: E13E89A7-826A-4E01-BDE3-582E078A123A
Disk /dev/nvme1n1: 119,24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: NE-128
Disk identifier: 0x21023d25
# cat /etc/mdadm/mdadm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# 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>
# instruct the monitoring daemon where to send mail alerts
MAILADDR gxxxxxxxxx@xxxxxxx.com
MAILFROM root
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=NASOMV:RAID5 UUID=d9dad86e:51cbe65e:5b4d88af:fa593c45
Alles anzeigen
SMART Logs before failure:
20/09/2022 11:40:25
Device: /dev/disk/by-id/nvme-NE-512_9800619606032, state written to /var/lib/smartmontools/smartd.NE_512-9800619606032-n1.nvme.state
20/09/2022 11:40:25
Device: /dev/disk/by-id/nvme-NE-128_9800624803340, state written to /var/lib/smartmontools/smartd.NE_128-9800624803340-n1.nvme.state
20/09/2022 11:40:24
smartd 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-18-amd64] (local build)
20/09/2022 11:40:24
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
20/09/2022 11:40:24
Opened configuration file /etc/smartd.conf
20/09/2022 11:40:24
Configuration file /etc/smartd.conf parsed.
20/09/2022 11:40:24
Device: /dev/disk/by-id/nvme-NE-128_9800624803340, opened
20/09/2022 11:40:24
Device: /dev/disk/by-id/nvme-NE-128_9800624803340, NE-128, S/N:9800624803340, FW:S1111H0L, NSID:1, 128 GB
20/09/2022 11:40:24
Device: /dev/disk/by-id/nvme-NE-128_9800624803340, is SMART capable. Adding to "monitor" list.
20/09/2022 11:40:24
Device: /dev/disk/by-id/nvme-NE-128_9800624803340, state read from /var/lib/smartmontools/smartd.NE_128-9800624803340-n1.nvme.state
20/09/2022 11:40:24
Device: /dev/disk/by-id/nvme-NE-512_9800619606032, opened
20/09/2022 11:40:24
Device: /dev/disk/by-id/nvme-NE-512_9800619606032, is SMART capable. Adding to "monitor" list.
20/09/2022 11:40:24
Device: /dev/disk/by-id/nvme-NE-512_9800619606032, NE-512, S/N:9800619606032, FW:S1111A0L, NSID:1, 512 GB
20/09/2022 11:40:24
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7U31N, unable to autodetect device type
20/09/2022 11:40:24
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7U31N, not available
20/09/2022 11:40:24
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7VADN, unable to autodetect device type
20/09/2022 11:40:24
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7VADN, not available
20/09/2022 11:40:24
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7W4EN, unable to autodetect device type
20/09/2022 11:40:24
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7W4EN, not available
20/09/2022 11:40:24
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7W6LN, unable to autodetect device type
20/09/2022 11:40:24
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7W6LN, not available
20/09/2022 11:40:24
Monitoring 0 ATA/SATA, 0 SCSI/SAS and 2 NVMe devices
20/09/2022 11:40:24
Device: /dev/disk/by-id/nvme-NE-512_9800619606032, state read from /var/lib/smartmontools/smartd.NE_512-9800619606032-n1.nvme.state
20/09/2022 11:39:58
Device: /dev/disk/by-id/nvme-NE-512_9800619606032, state written to /var/lib/smartmontools/smartd.NE_512-9800619606032-n1.nvme.state
20/09/2022 11:39:58
smartd received signal 15: Terminated
20/09/2022 11:39:58
Device: /dev/disk/by-id/nvme-NE-128_9800624803340, state written to /var/lib/smartmontools/smartd.NE_128-9800624803340-n1.nvme.state
20/09/2022 11:39:58
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7U31N [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD101EFAX_68LDBN0-VCG7U31N.ata.state
20/09/2022 11:39:58
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7VADN [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD101EFAX_68LDBN0-VCG7VADN.ata.state
20/09/2022 11:39:58
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7W4EN [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD101EFAX_68LDBN0-VCG7W4EN.ata.state
20/09/2022 11:39:58
Device: /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG7W6LN [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD101EFAX_68LDBN0-VCG7W6LN.ata.state
20/09/2022 11:39:58
smartd is exiting (exit status 0)
Alles anzeigen
What is the problem ?
Can someone help me ?
Do I have to shutdown my server remotely ?
Lot of thanks !
Thanks !
I found how to do that in Google account setup. It's revolved !
Hi !
For some time, I realized that sending SMTP notifications no longer works.
My setup with gmail used to work, but it longer does.
My config is:
SMTP server: smtp.gmail.com
SMTP port: 587
Encryption method: STARTTLS
I share you my Syslog
postfix/smtp[19743]: C5B6022089A: to=, orig_to=, relay=smtp.gmail.com[64.233.167.108]:587, delay=0.71, delays=0.02/0.03/0.66/0, dsn=4.7.8, status=deferred (SASL authentication failed; server smtp.gmail.com[64.233.167.108] said: 535-5.7.8 Username and Password not accepted. Learn more at?535 5.7.8 https://support.google.com/mail/?p=BadCredentials s14-20020adfeb0e000000b0021d7fa77710sm5595203wrn.92 - gsmtp)
postfix/error[19491]: D24F22207E8: to=, relay=none, delay=4635, delays=4629/5.7/0/0, dsn=4.7.8, status=deferred (delivery temporarily suspended: SASL authentication failed; server smtp.gmail.com[64.233.167.109] said: 535-5.7.8 Username and Password not accepted. Learn more at?535 5.7.8 https://support.google.com/mail/?p=BadCredentials k5-20020a05600c1c8500b003974cb37a94sm10048850wms.22 - gsmtp)
postfix/smtp[19487]: 5FA1E2206CF: to=, relay=smtp.gmail.com[64.233.167.109]:587, delay=4614, delays=4614/0.05/0.65/0, dsn=4.7.8, status=deferred (SASL authentication failed; server smtp.gmail.com[64.233.167.109] said: 535-5.7.8 Username and Password not accepted. Learn more at?535 5.7.8 https://support.google.com/mail/?p=BadCredentials k5-20020a05600c1c8500b003974cb37a94sm10048850wms.22 - gsmtp)
postfix/error[18877]: 0302122015D: to=, relay=none, delay=105692, delays=105679/13/0/0, dsn=4.7.8, status=deferred (delivery temporarily suspended: SASL authentication failed; server smtp.gmail.com[2a00:1450:400c:c00::6d] said: 535-5.7.8 Username and Password not accepted. Learn more at?535 5.7.8 https://support.google.com/mail/?p=BadCredentials t1-20020adfeb81000000b0021d6e49e4ebsm5526300wrn.10 - gsmtp)
postfix/smtp[18875]: F1A11220819: SASL authentication failed; server smtp.gmail.com[64.233.167.109] said: 535-5.7.8 Username and Password not accepted. Learn more at?535 5.7.8 https://support.google.com/mail/?p=BadCredentials k1-20020adfd841000000b0021d73772c87sm5504424wrl.91 - gsmtp
The problem is not solved because I always receive the same error by mail, while I create the directory.
Thank's !
The mentioned directory doesn't exists. I try it !
Hi !
I upgrade to OMV6 my NAS yesterday, and now, I receive this Anacron mail message:
/etc/cron.daily/openmediavault-check_locked_users:
faillock: Error reading tally directory: No such file or directory
Somebody know this error message and what I must to do for resolve this issue ?
ok, in this case, I don't touch anything.
It's looks like that.
Hi,
I have a RAID5 on my OMV NAS. All the first sunday per month, I have an automatic RAID scan which lasts near 24H longer.
During this time, the four HDD are in full-load state. That can be a problem during summer hot days.
Questions: This RAID scan is important ? Otherwise, how to disable this automatic RAID scan ?
Thank you for answers !
Any date for final release ?
EXT4 available for RAID storage ?
I'm still having this issue. Does anyone have any other ideas?
I have same issue with FTPS server on my OMV server. I try with older Filezilla 3.39.0 version, and it's resolve the 425 issue. Filezilla team change something with TLS, that's why all versions newer than 3.39.0 no longer work.
You can find easily 3.39.0 Filezilla version with Internet (filepuma.com is a trust website).
[EDIT]
I confirm that enable the option 'No session reuse required' (on the third screen capture), that should fix 425 issue.
Now, latest Filezilla and WinSCP versions work fine !