View Full Version : External usb still spinning
H7S has an internal ssd drive and an externally powered hdd plugged into the usb port.
Box is in standby and next morning i hear the hdd spinning.
Setting is the standard default to stop after 5 mins so unsure what might be happening.
I did have this mounted on box and still is showing in mounts.
Usb was inserted in standby and box rebooted but still the same.
H7S has an internal ssd drive and an externally powered hdd plugged into the usb port.
Box is in standby and next morning i hear the hdd spinning.
Setting is the standard default to stop after 5 mins so unsure what might be happening.
I did have this mounted on box and still is showing in mounts.
Usb was inserted in standby and box rebooted but still the same.
Debug logs please!
Not able to upload any attachments on this laptop for a while to WOS for months and have to try another way .
H7S has an internal ssd drive and an externally powered hdd plugged into the usb port.
Box is in standby and next morning i hear the hdd spinning.
Not every hdd honors the standby mode. What is the manufacturer and model of your hdd?
I assume you've put your hdd in an usb enclosure. This enclosure contains a SATA-USB converter chipset. Some chipsets do not pass the standby command to the hdd. So what is the manufacturer and model of your chipset? On a Linux command line just type 'lsusb'.
One log as requested
< 407.5028> [Harddisk] Command: 'hdparm -y /dev/sda'.
/dev/sda:
issuing standby commandSo Vix is sending the command.
It's perhaps this particular command that is failing?
< 49892.9921> [Hotplug] Connection lost.
< 49892.9928> [Hotplug] Calling processHotplugData, reason = [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
] eventData = {'ACTION': 'add', 'DEVPATH': '/dev/sdb', 'PHYSDEVPATH': '/block/sdb/device'}.< 49892.9934>
< 49892.9936> [Hotplug] DEBUG: {'ACTION': 'add', 'DEVPATH': '/dev/sdb', 'PHYSDEVPATH': '/block/sdb/device'}
< 49892.9940> [Hotplug] DEBUG: device = /dev/sdb action = add mediaState = None physDevPath = /block/sdb/device dev = sdb
< 49892.9944> [Harddisk] Evaluating hotplug connected device...
< 49892.9946> [Harddisk] DEBUG: device = 'sdb', physDevice = '/block/sdb/device'
< 49892.9985> [Harddisk] Found storage device 'sdb' (Removable = False).
< 49893.0001> [Harddisk] Command: 'sdparm --set=SCT=0 /dev/sdb'.
couldn't find field acronym: SCT
[perhaps a '--transport=<tn>' or '--vendor=<vn>' option is needed]
< 49893.0240> [Harddisk] Error: Command 'sdparm --set=SCT=0 /dev/sdb' returned error code 1!
< 49893.0241> [Harddisk] Command: 'hdparm -S0 /dev/sdb'.
/dev/sdb:
setting standby to 0
(off)
hdparm: HDIO_DRIVE_CMD: Invalid argument
@cactikid - so how is the hdd attached and does ut have its own power suppply? Because hotplug means its disconnected/reconnected
Only using externally powered Iomega 2tb and inserted into other port this morning while in standby , i assumed power would be dead at usb port like on laptop but it started to spin up while inserting it into other port.
Not sure if i used another one on that box before.
Only using externally powered Iomega 2tb and inserted into other port this morning while in standby , i assumed power would be dead at usb port like on laptop but it started to spin up while inserting it into other port.A box in standby is powered on, so the ports are active.
Anyway, I forgot you'd have 2 disks, so ignore the sda comment.
The internal one is being spundown (doubt it does anything for an SSD).
However, /dev/sdb is not, as if it were then the following commands would be run:
sdparm --flexible --readonly --command=stop /dev/sdb
and, if that fails:
hdparm -y /dev/sdb
But neither is.
Although the log also says:
< 49892.9985> [Harddisk] Found storage device 'sdb' (Removable = False).So in fact it may never run the first one anyway. (This bit isn't a Vix issue. My Kubuntu system also says that my external USB enclosures are not removable).
So, why does it not send the "hdparm -y" command?
Interestingly, I've just booted up my system and plugged in an external USB drive.
After 10mins (my spindown setting) I get:
< 721.396591> 00:14:22.7057 [Harddisk] Command: 'sdparm --flexible --readonly --command=stop /dev/sdc'.
/dev/sdc: HFS256G3 9TND-N210A 0
So it does seem to be working (although that is an SSD...)
Do you have something running that will be frequently/continually accessing the drive? If so, it will never be spundown.
@birdman - some HDD enclosures will not pass hdparm or sdparm commands.
As far as i know nothing should be running or accessing the box as i live alone.
@birdman - some HDD enclosures will not pass hdparm or sdparm commands.Which wouldn't stop Vix sending them.
Which wouldn't stop Vix sending them.
No - but it might explain why an error code 1 is returned and why the HDD is not spinning down.
No - but it might explain why an error code 1 is returned and why the HDD is not spinning down.Error code 1 is being returned because the command can't handle an SCT acronym (just as it can't do on my system).
Error code 1 is being returned because the command can't handle an SCT acronym (just as it can't do on my system).
SCT acronym?
SCT acronym?As reported in:
< 49893.0001> [Harddisk] Command: 'sdparm --set=SCT=0 /dev/sdb'.
couldn't find field acronym: SCT
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.