Error Read-only File System During Write On /dev/disks
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the
"setptablegpt: Unable To Commit To Disk"
workings and policies of this site About Us Learn more about Stack partedutil delete all partitions Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags
Writenewptable: Unable To Commit To Disk
Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how partedutil unable to delete partition it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top VMWare Error: Read-only file system during write on up vote 0 down vote favorite 1 I tried hundreds of forums and posts, but nothing seem to help! I have vSphere ESXi 5.5. and when starting ESXi the first time vmkload_mod: can not remove module plog: module symbols in use it created and formatted a storage automatically. For some reason I removed it and now I cannot get my disks/storage back! No problem if I need to reformat but even that is impossible ! I tried to reuse it, to format it, whatever possible, but nothing is working: The only message I get is : Error: Read-only file system during write on /dev/disks/naa.(...) ! For example : # partedUtil mklabel /dev/disks/naa.600605b009a647b01c5ed73926b7ede1 msdos Error: Read-only file system during write on /dev/disks/naa.600605b009a647b01c5ed73926b7ede1 WriteNewPtable: Unable to commit to device /dev/disks/naa.600605b009a647b01c5ed73926b7ede1 partedUtil delete partition gives the same message. partedUtil setptbl gives the same message. fdisk (delete, new partitions, write) is of no use. # partedUtil getptbl /dev/disks/naa.600605b009a647b01c5ed73926b7ede1 gpt 1215155 255 63 19521474560 1 63 8386622 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0 2 8386623 13629502 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0 Really, after trying more than 30 hours, I don't know anymore what to do ? Any help would be very much appreciated... Denis P. S. ESXi 5.5.0 P. P. S. The message in the GUI is Appel "HostDatastoreSystem.CreateVmfsDatastore" pour l'objet "ha-datastoresystem" sur ESXi "172.16.1.244" a échoué vmware-esxi filesystems comman
Next → VSAN Part 16 - Reclaiming disks for other uses Posted on February 18, 2014 by Cormac A number of customers have raised this question. How do you reclaim disks which were once
Esxcli Vsan Storage Remove
used by VSAN but you now wish to use these disks for remove vsan partition other purposes? Well, first off, if you are using some of the later builds of VSAN and you
Vsan Ineligible Disks
place the host into maintenance mode and remove the disk group from the host, this will automatically remove the partitions from the disks and you are good to go http://serverfault.com/questions/663970/vmware-error-read-only-file-system-during-write-on with reusing these disks for some other purpose. However, if you do something such as reinstall ESXi on the host but do not go through the appropriate VSAN clean up steps first, then there may still be VSAN partition information on the disks. So how do you go about cleaning up these disks? There are two method available - one http://cormachogan.com/2014/02/18/vsan-part-16-reclaiming-disks-for-other-uses/ is a nice controlled method, the other not so much. First of all, esxcli contains a nice command tor emove physical disks from VSAN disk groups. This wasn't in early beta versions of VSAN so you may not be aware of it. Usage: esxcli vsan storage remove [cmd options] The command options are -d (for magnetic disks), -s (for SSDs) and -u for UUID of VSAN Disk. Note that the -s option for SSD will also remove the magnetic disks from the disk group too. What is the other option? Well, before we had this nice esxcli command, we had to use a partedUtil delete command to clean up the disks. But if VSAN is still configured on the ESXi hosts and has claimed those disks, you will get an error similar to the following when you run partedUtil on the disks: Error: Read-only file system during write on /dev/disks/naa.500xxxxxxxx WriteNewPtable: Unable to commit to device /dev/disks/naa.500xxxxxxxx At this point, you can try the following steps. The first one is to get this host to lea
by Josh Coen Since VMware opened up the beta for VSAN I have wanted to take it for a spin in the lab but just haven’t had the time. Well, finally I had a http://www.valcolabs.com/2014/01/09/disks-not-available-for-use-in-vsan-configuration/ little bit of time. My three lab hosts had ESXi installed on the spinning disks and I had no SSDs installed. To get started I installed ESXi on USB sticks and installed some SSDs. Good to http://www.virtuallyghetto.com/2011/07/how-to-format-and-create-vmfs-volume.html get started, right? I logged into the web client and enabled VSAN in manual mode, but when I went to to configure the disk groups two of the hosts were only showing 0 of 1 unable to disks in use instead of 0 of 2 disks Taking a deeper look into the two hosts that were only showing one disk I discovered that labs-vmhost02 and labs-vmhost03 both weren’t showing the spinning disk as an available disk, only the SSDs were showing as available. The reason why only the SSDs were showing available is for two reasons: When ESXi was installed on the flash drive the spinning disk unable to commit was used for the scratch location The spinning disk is hosting the diagnostic/coredump partition In order to utilize the spinning disk for VSAN the partitions need to be moved or removed. Unfortunately when you try to remove these partitions using partedUtil because they are actively being used. The following error occurs: Error: Read-only file system during write on /dev/disks/t10.ATA_____TOSHIBA_MK3252GSX__________________________________4847P0FUT Unable to delete partition 2 from device /dev/disks/t10.ATA_____TOSHIBA_MK3252GSX__________________________________4847P0FUT For the purposes of this post we’ll be moving the scratch partition and unconfigure the coredump partition. You can also change the location of the coredump partition to a different device and partition number. Doing this will allow us to delete the partitions using partedUtil Before we can start changing things we need to identify the disk and partition numbers. First lets get the device ID of the disk we’re trying to use for VSAN: SSH into the host and run the following command esxcli storage core device list 1 esxcli storage core device list Now, find the disk in question (I knew which disk to look for because it was the only Toshiba disk in the system) and copy the device ID; this is the first line The device ID we’ll be using is: t10.ATA_____TOSHIBA_MK3252GSX__________________________________4847P0FUT Now we need to find any partition
CLI in ESXi 5 Posted on 07/19/2011 by William Lam VMware always recommends formatting and creating a new VMFS volume using the vSphere Client as it automatically aligns your VMFS volume. However, if you do not have access to the vSphere Client or you wanted to format additional VMFS volumes via a kickstart, you can do so using the CLI and the partedUtil under /sbin. ~ # /sbin/partedUtil Not enough arguments Usage: Get Partitions : get Set Partitions : set ["partNum startSector endSector type attr"]* Delete Partition : delete Resize Partition : resize Get Partitions : getptbl Set Partitions : setptbl ["partNum startSector endSector type/guid attr"]* Fix Partition Table : fix Create New Label (all existing data will be lost): mklabel Show commonly used partition type guids : showGuids With ESXi 5, an MBR (Master Boot Record) partition table is no longer used and has been replaced with a GPT (GUID Partition Table) partition table. There is also only one block size of 1MB versus the 2,4 and 8 that was available in ESX(i) 4.x We can view the partitions of a device by using the "getptbl" option and ensure we don't have an existing VMFS volume: ~ # /sbin/partedUtil "getptbl" "/vmfs/devices/disks/mpx.vmhba1:C0:T2:L0" gpt 652 255 63 10485760 Next we will need to create a partition by using the "setptbl" option: /sbin/partedUtil "setptbl" "/vmfs/devices/disks/mpx.vmhba1:C0:T2:L0" "gpt" "1 2048 10474379 AA31E02A400F11DB9590000C2911D1B8 0" The "setptbl" accepts 3 arguments: diskName label partitionNumber startSector endSector type/GUID attribute The diskName in this example is the full path to the device which is /vmfs/devices/disks/mpx.vmhba1:C0:T2:L0 The label will be gpt The last argument is actually a string comprised of 5 individual parameters: partitionNumber - Pretty straight forward startSector - This will always be 2048 for 1MB alignment for VMFS5 endSector - This will need to be calculated based on size of your device type/GUID - This is the GUID key for a particular partition type, for VMFS it will