You can run a long test while the drives are still in use, there is no need to take them offline. Just start the test and take note of the estimated time. Your system can still read and write to them at the same time
[Update: Seller Complaints Accumulating] HGST Ultrastar He10 - 10TB @ $129.95
- Thread starter ArthurA
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
If i remember correctly, a long 'offline' test doesn't mean your drives are really offline during the test. It just means they might not have 100% performance during the test, but they are still perfectly usable by your system while the test is running.
edit i think a BMS or Background Medium Scan is a Seagate thing, which is impossible to disable. It will run every time you either power on or even reset your computer. I remember it took about 18 hours to complete with my 8x3TB seagate drives, during which time they ran hot and it was a general pain. Another reason never to use seagate drives.
edit i think a BMS or Background Medium Scan is a Seagate thing, which is impossible to disable. It will run every time you either power on or even reset your computer. I remember it took about 18 hours to complete with my 8x3TB seagate drives, during which time they ran hot and it was a general pain. Another reason never to use seagate drives.
Last edited:
Code:
Background scan results page [0x15]
Status parameters:
Accumulated power on minutes: 1706858 [h:m 28447:38]
Status: background medium scan is active
Number of background scans performed: 168
Background medium scan progress: 93.08 %
Number of background medium scans performed: 168Again, the BMS or Background Medium Scan is a proprietary Seagate process that cannot be stopped, and if you reboot it will start again, and will not stop until it reaches 100%. It has nothing to do with a smartctl self-test at all. There is some 'interval timer' but again, it's all hardcoded into Seagate drives and cannot be disabled any way.
Last edited:
Don't have seagate drives anywhere.
as far as the long tests. I understand that can be ran with the drives online and in use..
as I said I started the first one when I did a quick test of the drives by them selfs in the chassis. I then shut the chassis down put in my 12 3tb drives back in the system rebooted the machine then went through and replaced a single drive at a time with the 10tbs in the first 6 disk vdev to expand the pool. How ever the inittial long test I didn't let finish. After all 6 10tbs were in I went with -X to stop the test I had started and ran a new long test but they apear to never complete.
as far as the long tests. I understand that can be ran with the drives online and in use..
as I said I started the first one when I did a quick test of the drives by them selfs in the chassis. I then shut the chassis down put in my 12 3tb drives back in the system rebooted the machine then went through and replaced a single drive at a time with the 10tbs in the first 6 disk vdev to expand the pool. How ever the inittial long test I didn't let finish. After all 6 10tbs were in I went with -X to stop the test I had started and ran a new long test but they apear to never complete.
Well then i don't know, i had Seagate nl-sas (nearline-sas)drives that did just this, and it has nothing to do with smartctl, so doing a smartctl -X or whatever the command to stop a smartctl long or short self test will not affect a BMS at all. Plus the BMS will always start again in a reboot and run until it reaches 100%, and cannot be stopped or disabled at all.
try to search internet with BMS and seagate and you should find some info.
Edit with that weird seagate line in your smartctl -x output, plus this BMS scan, you got some weird stuff going on here. I think you need to start doubting everything now and really find out what kinda drives you are running.
edit well now, it's my bad as well. Notice you have HUS drives, not HUH. HUS = no helium. You don't have helium drives at all, and my guess here is, without knowing, that you have some Hitatchi drives that are based on Seagate drives, because of the BMS stuff.
Last edited:
Very interesting, this seems to suggest it can be disabled. Might be useful for me someday. But OK, you don't have Helium drives. Your Hitatchi drives are based on Seagate drives. your BMS is separate from a smartctl self-test. There you go.
I think I've managed to get my self into a bit of an run-a-round situation.
So, the one long test that has been endlessly running as far as the report is concerned isn't actually running. It's a remnent log. Because I started the test but didn't let it finish it just stays in the log but it's not actually running and really isn't important. I started a new -t short and watched it show a new status where it went through then showed complete in the #1 spot and then I started a -t long where its now showing progress.
I think the long showing the 65535 seconds[1092.2 minutes] will stay there as a reference at all times and that was what was tripping me up. I was thinking it was a progress bar and it should be counting down.
How ever running the test again now shows above with x.xx% remaining. It's a reverse counter so 100% down to 0% rather then 0% to 100%
Now as far as the BMS side of things. your redit re-post makes sense. Since it's running and a background not worried about it.
Nothing like trying to figure something out and mistaking something for something else.
Now we just need to figure out why we can't poll the vender specific information. Cause I would very much like to know the helium levels also so as it will be a place holder on when to replace a drive.
So, the one long test that has been endlessly running as far as the report is concerned isn't actually running. It's a remnent log. Because I started the test but didn't let it finish it just stays in the log but it's not actually running and really isn't important. I started a new -t short and watched it show a new status where it went through then showed complete in the #1 spot and then I started a -t long where its now showing progress.
I think the long showing the 65535 seconds[1092.2 minutes] will stay there as a reference at all times and that was what was tripping me up. I was thinking it was a progress bar and it should be counting down.
How ever running the test again now shows above with x.xx% remaining. It's a reverse counter so 100% down to 0% rather then 0% to 100%
Now as far as the BMS side of things. your redit re-post makes sense. Since it's running and a background not worried about it.
Nothing like trying to figure something out and mistaking something for something else.
Now we just need to figure out why we can't poll the vender specific information. Cause I would very much like to know the helium levels also so as it will be a place holder on when to replace a drive.
Code:
Self-test execution status: 100% of test remaining
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Self test in progress ... - NOW - [- - -]
# 2 Background short Completed - 28470 - [- - -]
# 3 Background long Aborted (by user command) - 28417 - [- - -]
# 4 Background long Self test in progress ... - NOW - [- - -]
# 5 Background short Completed - 28250 - [- - -]
Long (extended) Self-test duration: 65535 seconds [1092.2 minutes]
Code:
Self-test execution status: 99% of test remaining
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Self test in progress ... - NOW - [- - -]
# 2 Background short Completed - 28470 - [- - -]
# 3 Background long Aborted (by user command) - 28417 - [- - -]
# 4 Background long Self test in progress ... - NOW - [- - -]
# 5 Background short Completed - 28250 - [- - -]
Long (extended) Self-test duration: 65535 seconds [1092.2 minutes]#4 is a smartctl long self test that you started.
#3 is that same test you aborted. It will remain in logs forever.
You don't have a helium drive. Your hitachi drive starts with HUS, not HUH. the second H in HUH = Helium.
once you allow this long self test to complete, it will become # 1 Background long Completed. Don't interrupt it, because it can affect resale value of the drive.
Last edited:
RIGHT
And your 3tb drives are the ones with BMS. I admit in the beginning of all this i never checked your model numbers, i just assumed they were all HUH. My bad.
now go check your Helium levels on your HUH drives
No the bms is reporting on the 10tb drives. using sg_logs -a /dev/da2-7 [which are my 10tb drives] da8-13 is the 3tb sata drives and they do not report the bmsRIGHT
And your 3tb drives are the ones with BMS. I admit in the beginning of all this i never checked your model numbers, i just assumed they were all HUH. My bad.
now go check your Helium levels on your HUH drives
and all of this was over the 10tb drives will not show helium levels. or the vender specific outputs.
Code:
root@aeronas:~ # sg_logs -a /dev/da8
ATA Hitachi HUS72403 A5F0
Supported log pages [0x0]:
0x00 Supported log pages [sp]
0x10 Self test results [str]
0x2f Informational exceptions [ie]
Self-test results page [0x10]
Parameter code = 1, accumulated power-on hours = 10584
self-test code: background short [1]
self-test result: completed without error [0]
Parameter code = 2, accumulated power-on hours = 10498
self-test code: background extended [2]
self-test result: completed without error [0]
Informational Exceptions page [0x2f]
IE asc = 0x0, ascq = 0x0
Current temperature = 33 C
Threshold temperature = 0 C [common extension]that doesn't work because it doesn't report back the vender specific info. which is what we've been going on with lol..
I referenced my 3tb hgst hus sata drives as they are on the same hba/expander and do show the venderspecific outputs.
I made this over at the truenas forums.
Smart issues with sas drives.
All, I'm running around in circles with Smart issues on some new to me Sas HGST 10tb Helium drives. I've been discussing the issue over at Serve the home at this link https://forums.servethehome.com/index.php?threads/hgst-ultrastar-he10-10tb-129-95.34395/post-334124 So here is all that has...
www.truenas.com
Only your 10tb drives can be helium. hitachi helium drives only exist from 8tb and up.
do smartctl -a | grep Helium on your 10tb drives
I understand that.. The 3tb drives were only referenced because they are on the same hba and running a -a will output venderspecific information. Rather then the 10tbs which are sas and they will NOT output helium levels or much of anything when compared to your sata version and my 3tb sata drives.
Readin that shows it sas.. if you're running *nix can you run smartctl -a on that drive and paste the output.
