Tutorial[ Seagate Disks ]: Install Seagate OpenSeaChest Utilities

[tuxd3v]

no chance >

Hello Neo2018,

Ok, you can remove the 'test' directory we created 

Code:

rm -rf /opt/test

I think that the only option is geting the disk out, connecting to usb(but you need a power supply connected to usb->sata controller.. because this disks are 3.5".. and usb allone can't power it.. a big of a annoyance..)

Does you like the disks always in max performance?
O noticed that yours is in APM level 254 ( max performance.. )

[Neo2018]

Ok, you can remove the 'test' directory we created 

Code:

rm -rf /opt/test

I think that the only option is geting the disk out, connecting to usb(but you need a power supply connected to usb->sata controller.. because this disks are 3.5".. and usb allone can't power it.. a big of a annoyance..)

OK, already deleted.
I have an extra USB HDD 3.5 adapter with power supply. Previously used for RaspberryPi. The usb-> controller recognized the hard disk (model and serial number) well then. I hope it works.
I have to open the case anyway. I get a fan control upgrade with Arduino.

Does you like the disks always in max performance?
O noticed that yours is in APM level 254 ( max performance.. )

The 4TB Seagate discs are mostly used for watching movies (DLNA, Plex and data backup like Nextcloud). Otherwise, the hard drive is sleeping.
The 500GB disc is 24/7 in operation.
Where did you see that? > O noticed that yours is in APM level 254 ( max performance.. )
I use OMV with these settings >

[tuxd3v]

Does you like the disks always in max performance?
O noticed that yours is in APM level 254 ( max performance.. )

The 4TB Seagate discs are mostly used for watching movies (DLNA, Plex and data backup like Nextcloud). Otherwise, the hard drive is sleeping.
The 500GB disc is 24/7 in operation.
Where did you see that? > O noticed that yours is in APM level 254 ( max performance.. )
I use OMV with these settings >

Hello,
I saw here

Code:

=== START OF INFORMATION SECTION ===
Model Family:     Seagate IronWolf
Device Model:     ST4000VN008-xxxxxx
Serial Number:    xxxxxxxx
LU WWN Device Id: xxxxxxxxxxxxxxxxxxx
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:    Sat Mar  2 18:28:35 2019 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)

I have mines in mode 127,
Since it has no operating system running there, it will enter later in APM mode 1( StandBy )..
There exists a lag on first access, but after they are working fast, and a great part of the day, I am not using the Nas, so its nice


The disk is presented like normal to the OS, don't know why is hasn't worked
your /dev/sdb should have spits something out with or something else..

Code:

openSeaChest_Basics -d  /dev/sdb -i -v 4

 
To check the pcie controller:

Code:

dmesg|grep -Ei "ahci|pcie" --color

what is the output?

With usb adapter you should be ok then.

[Neo2018]

I saw here

Hello
At the time I tried a lot and probably put hdparm on default values or off.
Usually I always have it on 217.

The disk is presented like normal to the OS, don't know why is hasn't worked
your /dev/sdb should have spits something out with or something else..

Code:

openSeaChest_Basics -d  /dev/sdb -i -v 4

the self >

Code:

:~# openSeaChest_Basics -d  /dev/sdb -i -v 4
==========================================================================================
openSeaChest_Basics - openSeaChest drive utilities - NVMe Enabled
Copyright (c) 2014-2018 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
openSeaChest_Basics Version: 2.8.0-1_19_0 ARM
Build Date: Feb 28 2019
Today: Tue Mar  5 03:57:54 2019
==========================================================================================
open: Bad address
open failure
Error: 14 - Bad address
Error: Could not open handle to /dev/sdb

To check the pcie controller:

Code:

dmesg|grep -Ei "ahci|pcie" --color

what is the output?

No result, no output.

[tuxd3v]

No result, no output.

Well seems that the usb option its the only way..

[Neo2018]

Well seems that the usb option its the only way..

Hello tuxd3v
With USB have not tested it yet (little time)
But I discovered another problem. Much more important. 

I'm having trouble setting in OMV > physical disk properties > Spindown time. 
The hard drive goes too fast in standby mode.

I have created a new post in OMV Forum and PINE64 Forum.
Maybe you can look at it, or have a solution! It would be great.
Thank you.

[tuxd3v]

Well seems that the usb option its the only way..

Hello tuxd3v
With USB have not tested it yet (little time)
But I discovered another problem. Much more important. 

I'm having trouble setting in OMV > physical disk properties > Spindown time. 
The hard drive goes too fast in standby mode.

I have created a new post in OMV Forum and PINE64 Forum.
Maybe you can look at it, or have a solution! It would be great.
Thank you.

Hello Neo2018,

The APM mode 127, sends the disk in standby, relatively fast..
I don't know if you remember that I asked you about if you had something else Running from the IronWolf disk?

Usually, the best Thing is maintaining it only for Data, without Os and so..
Because if not, the disk will be waked constantly, reducing its life time (load/unload heads counts..)..

This has nothing to do with the PCIe card, or with the timers on the disk..
The timers by default are very nice, Seagate disks behave usually nicer in that regard..

If a disk is sleeping, and you issue some monitoring command on Him, it will wakeup, and I think this his the behaviour you are experiencing..

Maybe OMV is doing monitoring too much..
Try to use its corresponding SCSI counterpart, /dev/sgx, this can work for some commands, and doesn't usually wakeup the disks, but its more limited than query the /dev/sdX..

Maybe this is the problem..

[Neo2018]

The APM mode 127, sends the disk in standby, relatively fast..
I don't know if you remember that I asked you about if you had something else Running from the IronWolf disk?

The hard disk is used only for data> music, movies, data.
OS runs on the eMMC 64 GB.

If a disk is sleeping, and you issue some monitoring command on Him, it will wakeup, and I think this his the behaviour you are experiencing..

Maybe OMV is doing monitoring too much..
Try to use its corresponding SCSI counterpart, /dev/sgx, this can work for some commands, and doesn't usually wakeup the disks, but its more limited than query the /dev/sdX..

Maybe this is the problem..

For the test, I have the hard drive set to 128, SMART completely disabled. > No effect / same problem.
Hard disk changes to standby mode after 2 minutes.
OMV Forum report

[tuxd3v]

The APM mode 127, sends the disk in standby, relatively fast..
I don't know if you remember that I asked you about if you had something else Running from the IronWolf disk?

The hard disk is used only for data> music, movies, data.
OS runs on the eMMC 64 GB.

For the test, I have the hard drive set to 128, SMART completely disabled. > No effect / same problem.
Hard disk changes to standby mode after 2 minutes.
OMV Forum report

Hello,
You can put it do  254 but then the disk will be always spinning , waiting energy even when you are not using him..
Stand By Means stop rotating, and only the controller has some circuits waken, to start the disk when needed..

If you do  hdparm -B 254 the disk go to sleep in the same way?
If then...
The reason for the Setup via a usb-sata converter with OpenSeaChest is Valid..

[Neo2018]

If you do  hdparm -B 254 the disk go to sleep in the same way?

Hello tuxd3v,
Here I did a test with 127 and 254.
Currently 192 is set, > hdparm does not respond to -S specifications, but it goes automatically after an indeterminate time in standby mode.
This is much better than 127, where after 2/5 min. in standby mode changes.

The reason for the Setup via a usb-sata converter with OpenSeaChest is Valid..

Unfortunately, I do not have the time. But that is at the top of my list.

After this comment, (After this, not using hdparm at all ......) I have an idea.
What if I use a clean OMV without using hdparm. And immediately after mount the HDD, install or test OpenSeaChest. Accordingly, hdpart makes the problems and not PCI-e SATA-II Card.
or with another OS. (Which OS would be better suited?)?
is this worth a try?