Jump to content

SimonF

Members
  • Content Count

    77
  • Joined

  • Last visited

Community Reputation

8 Neutral

About SimonF

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. SAT means ATA disk connected via a SCSI port, i.e. SATA. The Smartctl code defaults all sdX devices to scsi then tries to do an open and scsi inquiry. If the drive vendor is ATA then device type in smartctl is changed from SCSI to SAT. root@Tower:/usr/local/sbin# ./smartctl -r ioctl /dev/sdc smartctl 7.2 2020-09-19 r5083 [x86_64-linux-5.8.12-Unraid] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org >>>> do_scsi_cmnd_io: sg_io_ver=3 [inquiry: 12 00 00 00 24 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=0 >>>> do_scsi_cmnd_io: sg_io_ver=3 [ata pass-through(16): 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=2 milliseconds resid=0 /dev/sdc [SAT]: Device open changed type from 'scsi' to 'sat' ATA device successfully opened Use 'smartctl -a' (or '-x') to print SMART (and more) information You can use -d test to see this. root@Tower:/usr/local/sbin# ./smartctl -d test /dev/sdc smartctl 7.2 2020-09-19 r5083 [x86_64-linux-5.8.12-Unraid] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdc: Device of type 'scsi' [SCSI] detected /dev/sdc [SAT]: Device open changed type from 'scsi' to 'sat' /dev/sdc [SAT]: Device of type 'sat' [ATA] opened
  2. I have a new version of smartctl build on 7.2 and the revision r5083 as of yesterday. Use at own risk. Talking to devs to get my changes added will post once ticket is raised. smartctl 7.2 2020-09-19 r5083 smartctl
  3. have noticed that spin down of additional pools is using the following command: Sep 15 14:44:08 Tower emhttpd: shcmd (154): /usr/sbin/hdparm -y /dev/sdb &> /dev/null would it be better to use smartctl -s standby,now ? I have submitted code changes to the smartctl team to support SAS drives 1) to support -n standby as currently unraid will spin up drives on device pool. 2) enable -s standby,now for SCSI drives 3) Addition option of -s active to spin up both ATA and SCSI drives. Existing ATA options smartctl -in standby /dev/sdb smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org Device is in STANDBY mode, exit(2) root@Tower:/# smartctl -s standby,now /dev/sdb smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org Device placed in STANDBY mode New Version for SCSI Drives root@Tower:/# smartctl -in standby /dev/sdd smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org Device is in STANDBY BY COMMAND mode, exit(2) root@Tower:/# smartctl -s standby,now /dev/sdd smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org Device placed in STANDBY mode If the changes are implemented into smartctl it will support spin down of SAS drives in pools.
  4. hdparm is only used from emhttpd for pools I think. mdcmd spins down array drives, I have sent some sample code that could be used to limetech for mdcmd. I have submitted changes to smartctl to enable standby for SAS drives, it already supports SATA/ATA, I am looking to check will work with usb attached drives. if this is the case will ask if hdparm option could be changed to smartctl and once changes have been incorporated by smartctl team them it will support both SAS and SATA.
  5. No does not fix green ball as that is controlled by mdcmd for the main array. hdparm will not work for SAS drives as it is for ATA commands.
  6. Found my issue emhttpd wasnt picking one up in /usr/local/sbin. So no spinups now with device poll 🙂 I have also made some addition changes to my revised smartctl changes. -n standby options as before. But now have added -s standby, now so same command could be used for both ATA and SCSI. Also added function -s active to spinup both ATA and SCSi drives. Awaiting feedback from smartctl team as yet no ticket is logged.
  7. where did you put the wrapper
  8. Change has not been accepted by moderators as yet. Attached is my version use at your own risk On my machine spin ups still happen if I have device poll enabled. But cannot trace where or what is called to do those checks. It may be in emhttpd but I dont have source to review/check. Again it may be that check is looking just for standby but I am outputting different status depending on how its spins down. smartctl is in my boot/extras added to go (This is on my test server not live one test is on beta25) cp /boot/extras/smartctl /usr/local/sbin chmod +x /usr/local/sbin/smartctl root@Tower:~# smartctl -i -n standby /dev/sdg smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org Device is in STANDBY BY COMMAND mode, exit(2) root@Tower:~# smartctl -i -n standby /dev/sdh smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org Device is in STANDBY BY TIMER mode, exit(2) root@Tower:~# smartctl -i -n never /dev/sdh smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: HGST Product: HUS724030ALS640 Revision: A1C4 Compliance: SPC-4 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Logical block size: 512 bytes LU is resource provisioned, LBPRZ=0 Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000cca027baa9a8 Serial number: Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Fri Sep 11 20:28:44 2020 BST SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Enabled Power mode was: STANDBY BY TIMER smartctl
  9. I have written the standby function into smartctl for SCSI(SAS) devices as its only currently available for ATA and submitted to owner for inclusion. example outputs not sure if that would be of use. root@Tower:~# smartctl -i -n standby /dev/sdg smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org Device is in STANDBY BY COMMAND mode, exit(2) root@Tower:~# smartctl -i -n standby /dev/sdh smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org Device is in STANDBY BY TIMER mode, exit(2) root@Tower:~# smartctl -i -n never /dev/sdh smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: HGST Product: HUS724030ALS640 Revision: A1C4 Compliance: SPC-4 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Logical block size: 512 bytes LU is resource provisioned, LBPRZ=0 Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000cca027baa9a8 Serial number: Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Fri Sep 11 20:28:44 2020 BST SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Enabled Power mode was: STANDBY BY TIMER I have also provided some code to devs for changes to mdcmd to include within Unraid
  10. Yes they are the same, how did you check standby? I found device polling would spin them up. Using sdX without -r or --readonly I saw an entry in the syslog for the disk and no action on the drive spin down. sgX you do not need to specify readonly. Command I use to see spindown is as follows. sdparm --command=sense /dev/sdg /dev/sdg: HGST HUS724030ALS640 A1C4 Additional sense: Standby condition activated by command
  11. You can use the sdX drive if you use -r this would simplify your script.
  12. @doron not sure if background media scans happen if drives in standby. I have disabled on my drives for when i was using idle timers. sdparm --clear=EN_BMS --save /dev/sdX You can see if background scans are active on Smartctl. Also maybe some other functions are accessing drive as I know Smartctl doesn't work with the standby option on SAS. Does the GUI check for standby? Do you run the IPMI plugin and checking disk temps as this may cause spinups also.
  13. Its system wide I believe and there is no option per device. I have only SAS drives in my test system array so that works for me.
  14. i found that smartctl requests can spin up the drives. I have set my device poll to 18000 which means they wake up every 5 hours. Not sure about UD as dont have a SAS drive as UD only SATA I have also found a way to use the sdX names by using the --readonly so the device is opened as readonly and not readwrite. sg_start --readonly --pc=3 /dev/sdd also sg_raw can be used also. sg_raw -v -R /dev/sdd 1b 00 00 00 10 00 cdb to send: [1b 00 00 00 10 00] SCSI Status: Good root@Tower:~# sg_raw -v -R /dev/sdd 1b 00 00 00 30 00 cdb to send: [1b 00 00 00 30 00] SCSI Status: Good
  15. on my system sg_map -i provides more info, ATA are SATA devices and Vendor name are SAS so maybe that could be used. root@Tower:~# sg_map -i /dev/sg0 /dev/sda SanDisk Cruzer Fit 1.00 /dev/sg1 /dev/sr0 HL-DT-ST BD-RE BU40N 1.03 /dev/sg2 /dev/sdb ATA ST3320310CS SC14 /dev/sg3 /dev/sdc HGST HUS724030ALS640 A1C4 /dev/sg4 /dev/sdd HITACHI HMRSK2000GBAS07K 3P02 /dev/sg5 /dev/sde HGST HUS724030ALS640 A1C4 /dev/sg6 /dev/sdf HGST HUS724030ALS640 A1C4 /dev/sg7 /dev/sdg HGST HUS724030ALS640 A1C4 /dev/sg8 /dev/sdh ATA CT500MX500SSD1 023 /dev/sg9 /dev/sdi HITACHI HMRSK2000GBAS07K 3P02 /dev/sg10 /dev/sdj ATA SSD PLUS 480GB 00RL