{"id":1478,"date":"2013-07-05T12:16:02","date_gmt":"2013-07-05T11:16:02","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1478"},"modified":"2015-12-09T18:53:59","modified_gmt":"2015-12-09T17:53:59","slug":"write-device-parameter-incorrect","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2013\/07\/write-device-parameter-incorrect\/","title":{"rendered":"Cannot write to device &#8211; the parameter is incorrect"},"content":{"rendered":"<p>When using the wrong block size for the tape devices, you may get the error message <code>Cannot write to device ([87] The Parameter is incorrect.)<\/code> during the backup or while formatting media. This error may occur if as SAS library, attached to the controller P212-ZM is used. When you try to use a higher block size in Data Protector for such a device you will receive the error above. In this case the only way to use a higher block size is to add RAM to the controller.<\/p>\n<p>Another szenario will be when using 1024K as block size and you update drivers. In a specific case with a QLogic HBA (QMH2462) in the past it was possible to backup data using a block size of 1024K for the devices. The HBA used firmware 5.03.15. After updating Windows drivers to version 9.1.10.27 and firmware to 5.06.05 the customer received the error above. The setting <code>qlfc - tsize 1024<\/code> didn&#8217;t fix the problem. Qlogic changed the bahavior for the possible block sizes with firmware version 5.04.02. In this particuallar case the customer was required to decrease the block size to 512K and to reformat the media with the new block size within Data Protector. Thanks to Volker for the comment on it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When using the wrong block size for the tape devices, you may get the error message Cannot write to device ([87] The Parameter is incorrect.) during the backup or while formatting media. This error may occur if as SAS library, attached to the controller P212-ZM is used. When you try to use a higher block [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[11],"tags":[],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"en","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-nQ","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":100,"url":"https:\/\/www.data-protector.org\/wordpress\/2010\/12\/disable-device-polling\/","url_meta":{"origin":1478,"position":0},"title":"Disable Device Polling","date":"31. December 2010","format":false,"excerpt":"{:de}In einem anderen Artikel \"What is device polling\" \u00a0hatte ich beschrieben was Device Polling ist und welche Auswirkungen das auf ein backup haben kann. Hier versuche ich nun aufzuzeigen wie man Device Polling verhindert. Bleibt zu erw\u00e4hnen das nachfolgende Hinweise f\u00fcr anst\u00e4ndige Hardware - HP - gelten. Wenn man gezwungen\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2190,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/01\/eadr-tape-block-size\/","url_meta":{"origin":1478,"position":1},"title":"EADR and Tape Block Size","date":"1. January 2015","format":false,"excerpt":"{:en}In older articles I often wrote about Bare Metal Recovery, a feature included in Data Protector without any additional costs and called Enhanced Automated Disaster Recovery (EADR) - see https:\/\/www.data-protector.org\/wordpress\/?s=eadr. To recover the Cell Server (see link) I always told to use tape devices with a block size of 64K.\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":87,"url":"https:\/\/www.data-protector.org\/wordpress\/2010\/12\/was-ist-eigentlich-device-polling\/","url_meta":{"origin":1478,"position":2},"title":"What is device polling","date":"31. December 2010","format":false,"excerpt":"{:de}Bestimmt jeder Data Protector Kunde mit einer Fibre Channel Tape Library hat dieses Problem schon mal wissentlich oder unwissentlich erlebt: ein SCSI Reset w\u00e4hrend einer Sicherung... und das ganze Band ist zerst\u00f6rt. Was war passiert? Das Bandlaufwerk wurde mit\u00a0SCSI Kommandos \u00fcbersch\u00fcttet - das nennt man auch Device Polling. Polling ist\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1155,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/01\/hanging-sessions-dp-7-01\/","url_meta":{"origin":1478,"position":3},"title":"Hanging Sessions with DP 7.01","date":"23. January 2014","format":false,"excerpt":"{:en}It has been told to me and I've seen it in some environments... with DP 7.01 it can occur that a sessions hang till forever or the backup is aborted after 7200 second. The message displayed shows IPC errors (i.e error below) as no more data from Disk Agent or\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1517,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/07\/virtual-environment-backups-vmware-storeonce-aborting-randomly\/","url_meta":{"origin":1478,"position":4},"title":"Virtual Environment Backups (VMware) to StoreOnce aborting randomly","date":"19. July 2013","format":false,"excerpt":"{:en}When backing up virtual machines using the Virtual Environment Integration (VE) to a Catalyst Gateway (StoreOnce), with Data Protector 7.01 (current patches) the VEPA backups might aborting randomly. The error message displayed: [Major] From: BSM@server.demo.local \"VE_Backup_VMware\" Time: 15\/07\/2013 10:03:03 [61:3003] Lost connection to BMA named \"StoreOnce_01_GW1 [GW 2296:4:26641437476]\" on host\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1393,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/advisory-c03753986\/","url_meta":{"origin":1478,"position":5},"title":"Advisory c03753986","date":"25. May 2013","format":false,"excerpt":"{:en}With document ID c03753986 on 2013\/05\/06 an advisory for HP Data Protector 6.11, 6.20, 6.21, 7.0 and 7.01 was released, describing a problem for restores of SAP data files and the file size is different from the SAP data file. When the omnirc parameter OB2SAPALIGN was used on Unix a\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1478"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=1478"}],"version-history":[{"count":3,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1478\/revisions"}],"predecessor-version":[{"id":2635,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1478\/revisions\/2635"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1478"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=1478"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=1478"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}