Seagate 500Gb don't sleeps when standbye and wol...

[dabezt]

Hi my friends, first of all THANKS a lot for Fvdw firmware... I've 'degraded' a 3tb cloudbox to 500gb and I've reused the 3tb disk for another NAS. I've enoug with 500gb in the cloudbox. The firmware is very easy and useful. Thanks.

I've detected a situation: the disk still spins when I select NAS standbye WOL...

The disk is Seagate ST3500630AB
With "firmware: cloudbox fvdw-sl 16.1 patched "

I can wake the box with WOL without problems, but the disk was spinning in standbye mode...

is this disk supported for standye WOL? is a fvwd firmware issue?

BTW: there's no way to configure to go to standbye after not using the disk for example in 30 minutes? I've not found the option in the web gui.

Thanks again! regards!

[dabezt]

N1 here could be kind helping me please?¿ thnx

[fvdw]

Sorry I overlooked your post. The firmware uses a standard command that it sent to the disk if it has to enter standby. Most disks support that. I need to check if your disk it but I think it should.
Your second question.
In the disk menu of the web interface you can activate and set the time for the disk to go to standby after period of inactivity.
This will only work in case the disk supports the standby command and if there is no program or server running on the cloudbox keeping the nas busy, or if it receives request for file share via your lan

Are you familiar with using ssh access using a ssh cluent like putty? We can use to enter a linux command to test if your disk respobds to the standby command

[dabezt]

Sorry I overlooked your post. The firmware uses a standard command that it sent to the disk if it has to enter standby. Most disks support that. I need to check if your disk it but I think it should.
Your second question.
In the disk menu of the web interface you can activate and set the time for the disk to go to standby after period of inactivity.
This will only work in case the disk supports the standby command and if there is no program or server running on the cloudbox keeping the nas busy, or if it receives request for file share via your lan

Are you familiar with using ssh access using a ssh cluent like putty? We can use to enter a linux command to test if your disk respobds to the standby command

Yes I know linux / unix as well... so you can let me know which commands have to be run... Thanks!

About the othe rquestion, is not possible to establish in the firmware options how many minutes /hours of inactivity are enough to put the whole Cloudbox in hibernation? For example, after 20 minutes of inactivity..?

Thanks!

[fvdw]

connect to your cloudbox via ssh using for instance Putty (user: root password: giveit2me)
At linux command prompt enter this command to see which capabilities your hard disk has, post the output here.

Code: Select all

hdparm -I /dev/sda

The see what happens if you try to put it in standby use this command

Code: Select all

hdparm -y /dev/sda

This command should switch off your hard disk, probably it may spin up immediately because of activity on your nas
If you hear it spin down for a moment after giving this command then it supports the standby feature.

for your second question, look better in the web interface it is there

standbyl.JPG

[dabezt]

I think now it works after following your steps... I get the disk sleeping until I wake up it with WOL commands... thanks!

The hdparm command (-y) does sleep the disk, but it wakes up inmediately

The info (-I) (it's now a 1Tb disk instead 500Gb one I had days ago)

Code: Select all

/dev/sda:

ATA device, with non-removable media
        Model Number:       ST31000528AS
        Serial Number:      9VPB2LVR
        Firmware Revision:  CC46
        Transport:          Serial
Standards:
        Used: unknown (minor revision code 0x0029)
        Supported: 8 7 6 5
        Likely used: 8
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  268435455
        LBA48  user addressable sectors: 1953525168
        Logical/Physical Sector size:           512 bytes
        device size with M = 1024*1024:      953869 MBytes
        device size with M = 1000*1000:     1000204 MBytes (1000 GB)
        cache/buffer size  = unknown
        Nominal Media Rotation Rate: 7200
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = ?
        Recommended acoustic management value: 208, current value: 254
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    SMART feature set
                Security Mode feature set
           *    Power Management feature set
           *    Write cache
           *    Look-ahead
           *    Host Protected Area feature set
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    DOWNLOAD_MICROCODE
                SET_MAX security extension
           *    Automatic Acoustic Management feature set
           *    48-bit Address feature set
           *    Device Configuration Overlay feature set
           *    Mandatory FLUSH_CACHE
           *    FLUSH_CACHE_EXT
           *    SMART error logging
           *    SMART self-test
           *    General Purpose Logging feature set
           *    WRITE_{DMA|MULTIPLE}_FUA_EXT
           *    64-bit World wide name
                Write-Read-Verify feature set
           *    WRITE_UNCORRECTABLE_EXT command
           *    {READ,WRITE}_DMA_EXT_GPL commands
           *    Segmented DOWNLOAD_MICROCODE
           *    Gen1 signaling speed (1.5Gb/s)
           *    Gen2 signaling speed (3.0Gb/s)
           *    Native Command Queueing (NCQ)
           *    Phy event counters
                Device-initiated interface power management
           *    Software settings preservation
           *    SMART Command Transport (SCT) feature set
           *    SCT Long Sector Access (AC1)
           *    SCT LBA Segment Access (AC2)
           *    SCT Error Recovery Control (AC3)
           *    SCT Features Control (AC4)
           *    SCT Data Tables (AC5)
                unknown 206[12] (vendor specific)
Security:
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
                supported: enhanced erase
        170min for SECURITY ERASE UNIT. 170min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c5002d7880fc
        NAA             : 5
        IEEE OUI        : 000c50
        Unique ID       : 02d7880fc
Checksum: correct



Thanks. Regards.