Hi I need to create a 8 tb disk on my odroid hc2 (Omv 4 / Debian stretch) Is this the right way for the disk to become "partition aligned"?
"parted / dev / sda
mklabel gpt
mkpart primary ext4 0% 100%
quit
mkfs.ext4 -L (partion name) / dev / sda1 "
I'm not geek on linux why i ask 
Thanks for the reply Is there a place where all these commands are (om-mkconf) so you can get an overview of options with that command? I didn't get any more warnings
Could it mabye be here i need to remove mount point?
/etc/monit/conf.d/openmediavault-filesystem.conf
Read that on another tread
If the mount alert on mail will continue to come even if i remove it in fstab, it must be removed in? :
etc/monit/conf.d/openmediavault-filesystem.conf
There must be a developer who knows something about it?
I removed this from config.xml:
<mntent>
<uuid>df557e4c-3834-4d00-ac05-4f76e159e739</uuid>
<fsname>/dev/disk/by-label/Backup</fsname>
<dir>/srv/dev-disk-by-label-Backup</dir>
<type>ext4</type>
<opts>defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>
<freq>0</freq>
<passno>2</passno>
<hidden>0</hidden>
</mntent>
And this from Fstab:
/dev/disk/by-label/Backup /srv/dev-disk-by-label-Backup ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
(I have backup) but I still get the email:
Status failed Service mountpoint_srv_dev-disk-by-label-Backup
Date: Sun, 23 Dec 2018 11:36:12
Action: alert
Host: odroidxu4share
Description: status failed (1) -- /srv/dev-disk-by-label-Backup is not a mountpoint
Your faithful employee,
Monit
If you are reinstalling all the time due to the fact that you are going to make a small mistake it is not durable - You should be able to correct this error manually.
I am not interested in reinstalling since I have a large setup on the card I would like to know where to remove the disk manually I have removed it in
etc / fstab
etc / openmediavault / config.xml (Under fstab)
Now it removed in the interface but still gets the message:
Status failed Service mountpoint_srv_dev-disk-by-label-Backup
Date: Sun, 23 Dec 2018 11:36:12
Action: alert
Host: odroidxu4share
Description: status failed (1) -- /srv/dev-disk-by-label-Backup is not a mountpoint
Your faithful employee,
Monit
Where should I remove it?
Since it is Linux it should be possible to remove it manually as the developers should know where?
I get this problem after I changed the name of mount point this was necessary as I moved my backup disk up as primary hard disk and put new backup disk in the other hc 2 but now i get the mail:
Status failed Service mountpoint_srv_dev-disk-by-label-Backup
Date: Sun, 23 Dec 2018 10:32:32
Action: alert
Host: odroidxu4share
Description: status failed (1) -- /srv/dev-disk-by-label-Backup is not a mountpoint
Your faithful employee,
Monit
Is there a way to manually remove mount points "srv_dev-disk-by-label-Backup" - So it doesn't attempt to mount a name that doesn't exist?
I moved the disk to a Usb 3.0 enclouser from my Odroid hc2 and ran Seatools from my laptop on the hard drive where I was running:
Short generic test
Short drive self test
There were no errors on some of the tests .. - But when I put it back in Ordoid Hc2 - OMV4 and mount it says clicks sound ..?! : /
Is a short smart test enough to determine if there are problems with the disk?
Okay but the hard drive is brand new so can't understand it says this sound? - Should I try to mount it again so it says the sounds and run a "dmesg"? - Only when I mount the disk in the interface it says it ...? I umount it to not destroy it 
I want to return it if the disk is defective but don't know if it is a mount problem?
I have tried the following on a brand new Toshiba N300 8TB Disk that sits in my Odroid Hc2 running OMV 4:
parted /dev/sda
mklabel gpt
mkpart primary ext4 0% 100%
quit
mkfs.ext4 -L (partion name) /dev/sda1
When I mount partition in the Openmediavault interface after this, the disk says a click sound constantly. and i get the following fdisk error:
Device Start End Sectors Size Type
/dev/sda1 65535 15628000379 15627934845 7.3T Linux filesystem
Partition 1 does not start on physical sector boundary.
Is the disk broken or do I do something completely wrong? (It is completely new)
Okay, it seems to me that I've got it working now by following Adoby's advice & and disabel S.M.A.R.T check so it does not read on the disk constantly
Most:
"192 Power-Off_Retract_Count 0x0032 100 100,000 Old_age Always"
Have my hard drives got while they were in a cloudshell2 which tells me that the problem is also there but it's not possible to keep an eye on that when S.M.A.R.T is broken on cloudshell 2
(The hard dishes were brand new when I put them in cloudshell 2)
To be absolutely sure your settings look like in picture? Because I can not make my iron wolf spin down with these settings even though I have done:
"./JMS578FwUpdate -d / dev / sda -f ./JMS578_Hardkernel_v173.01.00.01.bin -b ./backup.bin -t 30"
How do you underclock them, do you have a guide? And another question: Do you run SMART test on your disks in cronjob or have you turned it off?
Adoby do spindown function when you have all off in physical disk properties ?
sudo smartctl -a /dev/sda
What device do you use for nas trohn_javolta?
And 192 Power-Off_Retract_Count dosent increas on your disk?
Hi, I'm having trouble with "192 Power-Off_Retract_Count" increase on Odroid Hc 2 (Omv 4), despite having added the correction from this link:
https://wiki.odroid.com/odroid…eshooting/shutdown_script
On a Seagate IronWolf 4 Tb
I'm not a nerd but can understand that this problem smashes the hard drive?
What should I do ?
(I have purchased 2 hc2 to solve the problems that occurred at Cloudshell2 with unstable usb connection / unmount and are now having trouble with "192 Power-Off_Retract_Count" on Hc2 as if the issues will never end :()
Knowing this is not a problem due to openmeidavault but maybe some nerds could give some advice - Thanks in advance
smartctl 6.6 2016-05-31 r4324 [armv7l-linux-4.14.69-odroidxu4] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, http://www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate IronWolf
Device Model: ST4000VN008-2DR166
Serial Number: WDH2XW3K
LU WWN Device Id: 5 000c50 0aacce2a7
Firmware Version: SC60
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5980 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Nov 14 14:21:52 2018 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 591) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 655) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x50bd) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 083 064 044 Pre-fail Always - 198761572
3 Spin_Up_Time 0x0003 094 093 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1261
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 076 060 045 Pre-fail Always - 36301290
9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 9004 (6 158 0)
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 189
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 099 099 000 Old_age Always - 17180131332
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 062 061 040 Old_age Always - 38 (Min/Max 38/39)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 885
193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6263
194 Temperature_Celsius 0x0022 038 040 000 Old_age Always - 38 (0 20 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 423 (220 221 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2012647957
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3274270929
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 8857 -
# 2 Short offline Completed without error 00% 8857 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
