Tutorial[ Seagate Disks ]: Install Seagate OpenSeaChest Utilities

[tuxd3v]

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?

I use mode 127, because it consumes a lot less energy, and my Disks are used to have my Knowledge Database Base/Notes and So on, everything of my stuff resuming..

But I only use the NAs for Consultations, or to add Data,
And for this purpose, mode 127 is nice because its true that you get some lag on first access( disks need to get out of standby mode ), but then its smooth, and when you done, disks go to sleep again..


But it all depends..for holding streaming of videos, maybe not the best option..
My IronWolfs came with mode 254( performance activated ), all of them..

but they also came with No Power On In Standby, and no Spinup Current control activated by default..
So a needed to activate them, since I wanted that features,
to prolong disks life and to consume less energy..
For that I used Seagate OpenSeachest..

I haven't used hdparm on this disks, because hdparm has only SMART Features,
It doesn't have the Seagate Features, or the Western Digital Features, or any other producer, that are not in the SMART feature set..

You tried to use OpenSeachest on it, but you haven't succeed, so my bet would be take the disk, put it in a usb-sata converter, configure what you need and then put it again in the NAS..

You also said that you have them in mode 192, so you succeeded in Setting a correct mode on them..

[Neo2018]

You tried to use OpenSeachest on it, but you haven't succeed, so my bet would be take the disk, put it in a usb-sata converter, configure what you need and then put it again in the NAS..

You also said that you have them in mode 192, so you succeeded in Setting a correct mode on them..

Hello tuxd3v,
I have tried everything possible to test, unfortunately I did not get a satisfactory result.

In the OMV forum I have described my current status and attitudes.

I have no ideas and do not know what else I can do to use OpenSeaChest or for me proper standby / spin down time.
That's why I might be waiting for a brainstorm or someone tells me 100% solution!

Many thanks for the support. I am ready for any further attempts. My HDD is very important to me!

[tuxd3v]

Hello tuxd3v,
I have tried everything possible to test, unfortunately I did not get a satisfactory result.

In the OMV forum I have described my current status and attitudes.

I have no ideas and do not know what else I can do to use OpenSeaChest or for me proper standby / spin down time.
That's why I might be waiting for a brainstorm or someone tells me 100% solution!

Many thanks for the support. I am ready for any further attempts. My HDD is very important to me!

I see that you tried using a usb to sata converter..
It could be that that your usb-sata model is not supported neither( mine is an ASMEDIA and is supported )
I have not the Pine pcie to Sata card.

You also said you can change the APM value, so in some way to are able to contact the disks..

The problem that maybe exists is related with Seagate own Commands..
We can wait for someone that has that pcie card , and a Seagate disk, and check, if they can configure their disks..

Or in the mean time we can try to contact Seagate,
For that please give me the product number and serial ID, of your card
So that they can made tests on that controller..

check with 'lspci' if you find your card, and its serial number/product number..

In the mean time, your disks are safe, they are simply on wake up consuming more energy, and on powerup they consume more energy too.

But its not the end of the world 
Find the product ID, and serial number of your card..

Best Regards

[Neo2018]

It could be that that your usb-sata model is not supported neither( mine is an ASMEDIA and is supported )

Most likely. I do not have another one. And I will not buy new ones!

The problem that maybe exists is related with Seagate own Commands..
We can wait for someone that has that pcie card , and a Seagate disk, and check, if they can configure their disks..

That would be good, of course, to check if, not only me have the problem. Wait, maybe once in my life I'll be lucky!

Or in the mean time we can try to contact Seagate,
For that please give me the product number and serial ID, of your card
So that they can made tests on that controller..

check with 'lspci' if you find your card, and its serial number/product number..

I do not know exactly how and what to write to explain my problem in the best possible way. (and if it is still in English, then I am completely out) lol
At 'lspci' do you mean that?

Code:

:~# lspci
00:00.0 PCI bridge: Device 1d87:0100
01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)

And with the product number and serial ID, I have already posted the output here several times, right?

Code:

=== START OF INFORMATION SECTION ===
Model Family:     Seagate IronWolf
Device Model:     ST4000VN008-2DR166
Serial Number:    ZDH36NNE

ps: Of course, very security is questionable to post such data publicly!

In the mean time, your disks are safe, they are simply on wake up consuming more energy, and on powerup they consume more energy too.

But its not the end of the world  

Yes, unfortunately the energy consumption is high. And with today's energy price we probably too expensive.
No, it's not the end of the world, but it's always annoying and frustrating when it does not work.

Thanks for the great support!

[tuxd3v]

Yes, unfortunately the energy consumption is high. And with today's energy price we probably too expensive.
No, it's not the end of the world, but it's always annoying and frustrating when it does not work.

Thanks for the great support!

You welcome,  
The majority of this tools use the SCSI layer, also because if your disk is in StandBy, it has big probability to not wake up, with certain commands..

On contrary using the Block Device driver, they will wake always..and 1 load/Unload cycle was waisted, and energy also..

Seagate guys, assured me that it should work for sure, they  have tested virtually almost all options..

Now I feel myself badly...   

I found some spare time today,
And I started playing around with some adaptors, none worked. on Rockpro64.

And so I checked( what I though was right, from the beginning.. the SCSI driver...it was not ) :

Code:

root@rockpro64:~# zcat /proc/config.gz |grep CHR_DEV_SG
# CONFIG_CHR_DEV_SG is not set

I though that the SCSI Generic driver was something that for sure was built on kernel..
Or as a module...
That is the problem..

You need a kernel module 'sg' driver for your kernel version...
I am sorry I haven't checked it before..I though it was for sure built-in...  

[Neo2018]

You need a kernel module 'sg' driver for your kernel version...
I am sorry I haven't checked it before..I though it was for sure built-in...  

What should / can I do?

[tuxd3v]

What should / can I do?

type this:

Code:

zcat /proc/config.gz |grep CHR_DEV_SG

see the output of it.. 

PS:
Also type this:

Code:

find /lib/modules -name sg.ko

You should have a SCSI driver loaded to be able to see information using OpenSeaChest..
But better to see first your outputs..

[Neo2018]

type this:

Code:

zcat /proc/config.gz |grep CHR_DEV_SG

see the output of it.. 

Sorry for the wait.
My kernel

Code:

:~# hostnamectl
  Static hostname: .........................
        Icon name: computer
       Machine ID: ............................
          Boot ID: ........................
 Operating System: Debian GNU/Linux 9 (stretch)
           Kernel: Linux 4.4.167-1161-rockchip-ayufan-g6f1664023387
     Architecture: arm64

:~# uname -a
Linux .............. 4.4.167-1161-rockchip-ayufan-g6f1664023387 #1 SMP Fri Mar 22 23:03:38 UTC 2019 aarch64 GNU/Linux

linux-rockpro64:arm64 is already the newest version (0.8.0rc5).

Code:

:~# zcat /proc/config.gz |grep CHR_DEV_SG
# CONFIG_CHR_DEV_SG is not set

PS:
Also type this:

Code:

find /lib/modules -name sg.ko

You should have a SCSI driver loaded to be able to see information using OpenSeaChest..
But better to see first your outputs..

Code:

:~# find /lib/modules -name sg.ko
root@R:~#

No output.....

[tuxd3v]

Sorry for the wait.
My kernel

Code:

:~# hostnamectl
  Static hostname: .........................
        Icon name: computer
       Machine ID: ............................
          Boot ID: ........................
 Operating System: Debian GNU/Linux 9 (stretch)
           Kernel: Linux 4.4.167-1161-rockchip-ayufan-g6f1664023387
     Architecture: arm64

:~# uname -a
Linux .............. 4.4.167-1161-rockchip-ayufan-g6f1664023387 #1 SMP Fri Mar 22 23:03:38 UTC 2019 aarch64 GNU/Linux

linux-rockpro64:arm64 is already the newest version (0.8.0rc5).

Code:

:~# zcat /proc/config.gz |grep CHR_DEV_SG
# CONFIG_CHR_DEV_SG is not set

Code:

:~# find /lib/modules -name sg.ko
root@R:~#

No output.....

That's the problem..

I filled a bug in ayufan build..
https://github.com/ayufan-rock64/linux-build/issues/350

The fastest way is getting the disk out, and put it in your 3.5" adapter, in a Desktop or laptop, 
Check if driver was builtin:

Code:

:~# zcat /proc/config.gz |grep CHR_DEV_SG
# CONFIG_CHR_DEV_SG is not set

If So,

Code:

modprobe sg

then install OpenSeaChest tools there:
And configure what you want, remove the disk and put it in the rockpro64 Again..

This is the easiest way of tunning your disk,
until you kernel compiles modules for SCSI Driver..

[Neo2018]

I filled a bug in ayufan build..
https://github.com/ayufan-rock64/linux-build/issues/350

I will follow it!

The fastest way is getting the disk out, and put it in your 3.5" adapter, in a Desktop or laptop, 

Unfortunately, I do not have a desktop PC. And it did not work that way>
The hard drive into a USB 3.0 external enclosure 3.5 and OpenSeaChest to instal after using OpenSeaChest features to control, also did not work.
In my case I have to wait and hope that the kernel will be fixed.