Internal Error Unix.unix_error13 Read
Developer Network (CDN) ForumsCitrix Insight ServicesCitrix ReadyCitrix Success KitsCloud Provider PackCloudBridgeCloudPlatform (powered by Apache CloudStack)CloudPortalDemo CenterDesktopPlayerEdgeSightEducationForum PrototypeHDX MonitorHDX RealTime Optimization PackHotfix Rollup PackJapanese ForumsKnowledge Center FeedbackLicensingLTSRNetScalerNetScaler E-Business CommunityNetScaler Gateway (Formerly Access Gateway)Profile ManagementProof of Concept KitsProvisioning ServerQuick Demo ToolkitReceiver, Plug-ins, and Merchandising ServerSecure GatewayShareFileSingle Sign-On (Password Manager)SmartAuditorStoreFrontTechnology PreviewsTrial SoftwareUniversal Print ServerUser Group CommunityVDI-in-a-BoxWeb InterfaceXenAppXenClientXenDesktopXenMobileXenServer Discussions Support Forums Products XenServer XenServer Product Family Command-Line Interface Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. During xe vm-backup we get an Unix.Unix_error(13, "read", "") Started by Dietmar Simons , 21 June 2010 - 03:14 PM Login to Reply 9 replies to this topic Dietmar Simons Members #1 Dietmar Simons 3 posts Posted 21 June 2010 - 03:14 PM Hello,we use Andy Burton's Backup Script (http://www.andy-burton.co.uk/blog/index.php/2009-11/updated-citrix-xenserver-5-5-automatic-vm-backup-scripts/comment-page-1/#comment-1097) to backup our vm's.It works fine, but sometimes we get this error:[2010-06-21_15-36-08] Quiesce snapshot failed:[2010-06-21_15-36-08] Attempting normal snapshot[2010-06-21_15-36-08] Snapshot e5427941-d14a-0bf8-b9a8-3170485dad83 as DUGW01_snapshot[2010-06-21_15-36-18] snapshot_vm succeeded: 0cd1fbfe-0810-b2dc-bf68-ee0e7bd23094[2010-06-21_15-36-18] Remove template status 0cd1fbfe-0810-b2dc-bf68-ee0e7bd23094[2010-06-21_15-36-18] remove_template succeeded:[2010-06-21_15-36-18] Disable HA 0cd1fbfe-0810-b2dc-bf68-ee0e7bd23094[2010-06-21_15-36-18] disable_ha succeeded:[2010-06-21_15-36-18] Export VM 0cd1fbfe-0810-b2dc-bf68-ee0e7bd23094 as DUGW01-2010-06-21_15-36-08.xvaThe server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.mess
without export/import but with dd command Submitted by root on Thu, 01/07/2016 - 12:36 Citrix Xen has a way to migrate the machines from one host to another via xe vm-export and xe vm-import commands but there are situations when this won't work. For example, if the source disk is in bad shape and there are bad (unreadable) blocks on your vm's disks, the xe vm-export command will be unsuccessful with the following error: [root@XenGz ~]# xe vm-export vm=gzlinux filename=./gzlinux.xva The server failed to handle your request, due to an internal http://discussions.citrix.com/topic/267054-during-xe-vm-backup-we-get-an-unixunix-error13-read/ error. The given message may give details useful for debugging the problem. message: Unix.Unix_error(13, "read", "") Well, in this situation, if you do not have any backup, you must do something and one of the options is to use dd which is able to run past the bad blocks with the right options. Be advised, if you had important information located on the http://docs.gz.ro/citrix-xen-copy-vhd-lv-with-dd.html bad blocks, that information is lost from the start. You have this opportunity to save as much as you can and to save the disk as a whole. Also, if you have bad blocks on important system or boot files, your system may not properly run nor even boot. Before using the dd command, you need a destination LV. You can create it as you want, even manually, but if you want to use it directly as xen disk in a fresh new VM, follow 1.0 first. If you already have the target lv in good size, just skip to point 1.1. 1.0. How to create VM from OS template via command line: Note: by default, XEN will create for Debian 8G disk. You can resize it before installation. [root@XenGz ~]# xe vm-install template="Debian Wheezy 7.0 (64-bit)" new-name-label="gzvirt64" dfabebc3-7e4a-5f8d-2866-681d6c646909 [root@XenGz ~]# xe vm-disk-list vm="gzvirt64" Disk 0 VBD: uuid ( RO) : 2a4d5c07-3fbe-1ca2-6e8c-0681c155e5db vm-name-label ( RO): gzvirt64 userdevice ( RW): 0 Disk 0 VDI: uuid ( RO) : 3950c41a-39ef-439f-bd02-a6e346a60b99 name-label ( RW): 0 sr-name-label ( RO): Local storage virtual-size ( RO): 8589934592 [root@XenGz ~]# lvscan |grep 3950c41a-39ef-439f-bd02-a6e346a60b99 inactive '/dev/VG_XenStorage-2f40bcc0-ced1-c408-4395-b735957cb19e/VHD-3950c41a-39ef-439f-bd02-a6e346a6
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring http://unix.stackexchange.com/questions/53036/read-a-single-key-gives-an-error developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top “read” a single key gives an error up vote 4 down internal error vote favorite This simple script should read one letter: #!/bin/bash read -n 1 key echo $key But it gives the following error read: Illegal option -n Executed by hand read -n 1 key works though. bash share|improve this question edited Oct 27 '12 at 10:07 warl0ck 21.4k25107230 asked Oct 27 '12 at 9:43 Davoud Taghawi-Nejad 13316 1 How are you running that script? –Mat Oct 27 '12 at 9:52 put type read in your script, and see what internal error unix.unix_error13 that is –warl0ck Oct 27 '12 at 9:52 read is a shell builtin -n: not found 1: not found key: not found –Davoud Taghawi-Nejad Oct 27 '12 at 10:44 sh; yes that solved it running it with ./script.sh works –Davoud Taghawi-Nejad Oct 27 '12 at 10:48 Another shell runs it then — I guess you have some other sh bastard installed. –lynxlynxlynx Oct 27 '12 at 21:45 add a comment| 1 Answer 1 active oldest votes up vote 8 down vote accepted The -n option to read is a bash extension, not found in some other shells. If you got the error read: Illegal option -n, it means you didn't run the script under bash. It's most likely that you ran the script under /bin/sh, and /bin/sh is not bash but dash (the error message is the one dash produces). To run a script under bash, start it with a shebang line #!/bin/bash, make the script file executable, and call it by name. Since you have a shebang line, the problem may be that you ran . /path/to/script instead of /path/to/script from another script running under /bin/sh. share|improve this answer answered Oct 28 '12 at 0:18 Gilles 372k696751127 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as