| setuid | You can just edit the bundle locally and deploy with that, using juju | 01:25 |
|---|---|---|
| sentinel_ | would anyone know if there is a bug with smartctl-validate that causes it to fail on the hard drive and not leave a log? | 03:39 |
| sentinel_ | is there a time when this place is more active | 03:49 |
| sentinel_ | hi dsop_ | 04:22 |
| sentinel_ | althogh it's probably just a auto reconect | 04:23 |
| KingJ | One of my machines managed by MAAS has a HP RAID controller in it. Sadly, there's no HBA mode so each disk is a RAID0 array. However, this means that MAAS can't run smartctl-validate against the drives as the /dev/sdX entry doesn't support SMART. | 09:40 |
| KingJ | However, it's possible for smartctl to read the SMART data on each disk by using the -d flag | 09:41 |
| KingJ | e.g.smartctl -a -d cciss,0 /dev/sg1 | 09:41 |
| KingJ | Which returns the full SMART report for the disk. | 09:41 |
| KingJ | Is there any way I can get MAAS to use the -d flag? | 09:41 |
| KingJ | (it'd be nice to have all the SMART data visible through MAAS) | 09:41 |
| KingJ | Thinking about it, I can work around this with a custom test script | 10:57 |
| mup | Bug #1770982 opened: Show / set the chassis identify capability <MAAS:New> <https://launchpad.net/bugs/1770982> | 16:45 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!