2.0 is just the switch from extjs 4 to 5. Most plugins will work out of the box.
I can just urge you to not request backports so that volker can soleyly focus on 2.0 and the jessie upgrade after that.
Greetings
David
2.0 is just the switch from extjs 4 to 5. Most plugins will work out of the box.
I can just urge you to not request backports so that volker can soleyly focus on 2.0 and the jessie upgrade after that.
Greetings
David
Many thanks for this fix. I was wondering, am I okay to try applying this patch to Kralizec rather than having to upgrade to Stoneburner? Would I just need to use patch to apply the diff file?
I'm familiar with software development, but come mostly from a Java and C#/.NET background. I'd love to get into Linux programming and even try out PHP.
My concern is, if I apply the patch and I do an apt-get update and apt-get upgrade, the change will be clobbered. Would I need to create a .deb package and then install with dpkg? If I did this, is there a way I can somehow pin the change and stop apt/dpkg from overwriting it? There's the obvious risk here that I might miss other changes/updates though.
I guess I'd like to create my own backport if possible, mostly out of curiosity
Thanks again.
you can surely backport it yourself, but I think this is not the preferred way because the changes will be overwritten by any newer package. You can pin the package, but I suggest to upgrade to 2.x. I can not remember for sure but the improvement was submitted via multiple commits and requires various other changes in the storage backend implementation.
Fixed with 2.0.5
- Mantis 0001299: Improve KVM VirtIO storage backend.
votdef, Thanks!!
Hi, I have running OMW 2.1.23. When I try to run S.M.A.R.T. test from WebUI i have following command:
Zitatsmartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
/dev/disk/by-id/ata-WDC_WD20EARX-00PASB0_WD-WMAZA4998025: Unsupported USB bridge [0x152d:0x0539 (0x100)]
Smartctl: please specify device type with the -d option.
Use smartctl -h to get a usage summary
Runing test via CLI with - d sat parameter works fine, e.g.
Zitatsmartctl -d sat -x /dev/sdd
Any ideas? It should be fixed according to eralier posts.
You're using a USB-SATA adapter?
Yes, its USB 3.0 Sata Enclosure.
I've used cheap ones and they don't display smart values. Guess it depends on the chipset of the enclosure.
Read here
It read S.M.A.R.T values. There is problem with Openmediavault WebUI and a smartctl call.
In CLI I have output data:
ZitatAlles anzeigenroot@OpenMediaVault:~# smartctl -d sat -x /dev/sdd
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
== START OF INFORMATION SECTION ===
Model Family: Western Digital Green
Device Model: WDC WD20EARX-00PASB0
Serial Number: WD-WMAZA4998025
LU WWN Device Id: 5 0014ee 002cc1b98
Firmware Version: 51.0AB51
User Capacity: 2,000,398,934,016 bytes [2,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Sat Jan 2 12:06:03 2016 CETSMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
It read S.M.A.R.T values. There is problem with Openmediavault WebUI and a smartctl call.
In CLI I have output data:
I assume the problem is that the device is not recognized as USB device by OMV, thus the required "-d sat" paramater is not added to the command line.
Please execute the following command and post the output here, or better open a new bugreport.
Thank's. Output of this command is:
ZitatAlles anzeigenDEVLINKS=/dev/disk/by-id/ata-WDC_WD20EARX-00PASB0_WD-WMAZA4998025 /dev/disk/by-id/wwn-0x50014ee002cc1b98 /dev/disk/by-path/pci-0000:00:13.5-usb-0:3:1.0-scsi-0:0:0:0
DEVNAME=/dev/sdd
DEVPATH=/devices/pci0000:00/0000:00:13.5/usb1/1-3/1-3:1.0/host8/target8:0:0/8:0:0:0/block/sdd
DEVTYPE=disk
ID_ATA=1
ID_ATA_DOWNLOAD_MICROCODE=1
ID_ATA_FEATURE_SET_HPA=1
ID_ATA_FEATURE_SET_HPA_ENABLED=1
ID_ATA_FEATURE_SET_PM=1
ID_ATA_FEATURE_SET_PM_ENABLED=1
ID_ATA_FEATURE_SET_PUIS=1
ID_ATA_FEATURE_SET_PUIS_ENABLED=0
ID_ATA_FEATURE_SET_SECURITY=1
ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=388
ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=388
ID_ATA_FEATURE_SET_SMART=1
ID_ATA_FEATURE_SET_SMART_ENABLED=1
ID_ATA_SATA=1
ID_ATA_SATA_SIGNAL_RATE_GEN1=1
ID_ATA_SATA_SIGNAL_RATE_GEN2=1
ID_ATA_WRITE_CACHE=1
ID_ATA_WRITE_CACHE_ENABLED=0
ID_BUS=ata
ID_MODEL=WDC_WD20EARX-00PASB0
ID_MODEL_ENC=WDC\x20WD20EARX-00PASB0\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
ID_PART_TABLE_TYPE=dos
ID_PATH=pci-0000:00:13.5-usb-0:3:1.0-scsi-0:0:0:0
ID_PATH_TAG=pci-0000_00_13_5-usb-0_3_1_0-scsi-0_0_0_0
ID_REVISION=51.0AB15
ID_SERIAL=WDC_WD20EARX-00PASB0_WD-WMAZA4998025
ID_SERIAL_SHORT=WD-WMAZA4998025
ID_TYPE=disk
ID_WWN=0x50014ee002cc1b98
ID_WWN_WITH_EXTENSION=0x50014ee002cc1b98
MAJOR=8
MINOR=48
SUBSYSTEM=block
UDEV_LOG=3
USEC_INITIALIZED=17074329775
root@OpenMediaVault:~#
I still have the same issue with virtio drives. SMART properties are shown in GUI, but when I try to run tests from the GUI I still get the message
/dev/vda: Unable to detect device type
Smartctl: please specify device type with the -d option.
Cant you include a field in the GUI to specify the device type?
Regards,
Norman
Your Bugtracker report is now solved.
http://bugtracker.openmediavault.org/view.php?id=1501
Greetings
David
Will this fix the issue for Raidcards in JBOD mode as well?
I have an areca, where I need to pass the areca command (specify card brand).
Hello
I use KVM and virtio disk. Openmediavault is a virtual machine, in this VM I cannot run smart on the virtio disk.
smartctl --all -d sat /dev/vdb
Smartctl: Device Read Identity Failed: empty IDENTIFY data
A mandatory SMART command failed: exiting
I use openmediavault 2.2.6, No problem with data on this virtio disk
any help ?
sorry for my bad english
thanks
I use OpenmediaVault inside a Proxmox VM with 6 physical disks added as virtio drives. S.M.A.R.T does not work, using the -d option does not work either, gives me the same result as post #35.
When I first installed OMV, S.M.A.R.T worked as it should. It was not until I upgraded from Proxmox 3.4 to 4.2 that I noticed S.M.A.R.T no longer functioned.
Now I don't know if its because of the Proxmox upgrade, I only noticed it since I had to reattach the physical drives again since their IDs changed. The fault might have been there for awhile before the Proxmox upgrade.
If specify SCSI instead of virtio when adding the drives, S.M.A.R.T works but will sometime hang OMV on boot for some reason.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!