Tips: Add new disk online
Posted by dr.watson - on September 25th, 2008 in Operating Systems, Storage, Tips | 4 Comments »
The following article will share how to add new hard disk into SuSE Linux Enterprise Server without reboot.
Follow these steps:
- Create a new LUN and assign to the ESX Server Storage Group on SAN.
- Rescan Storage Adaptors on ESX Server Virtual Infrastructure Console.
- Add new Hard Disk into VM by Edit Setting.
- Open VM Console(SSH will work as well).
- Detect new disk command # rescan-scsi-bus.sh
- Find new disk command #Â cat /proc/partitions
- Create new partition on the disk command # fdisk /dev/sdx
- Format new disk partition # mkfs.ext3 /dev/sdx1
- Edit /etc/fstab to add in permanent mount point for new disk and partition.
- Mount new disk # mount -a
Now, you should have your new disk mounted on the SuSE Linux system without downtime.
Enjoy!
Related posts:
- NetApp Virtual Storage Console (VSC) for ESX ready for Download
- VMware Data Recovery Mount Show Password Detail?
4 Responses
My new disk is not recognized by the OS at all.
Situation: A hard disk failed on the server (namely /dev/sdc)
Replaced the hard disk with a new one.
Suse: version 9 Patch level 3
Problem: The OS doesn’t see the new disk. Tried rescan-scsi-bus.sh, but it didn’t help. Tried reboot, didn’t help.
Notes: The newly added disk has been initialized during system POST and the IBM ServeRaid controller reports the disk available; just not the OS.
Any suggestions appreciated.
I added a new scsi disk
Are you talk about disk do not recognize on ur physical linux box or virtual? I am little confuse on this
Yeah, The new disk that was added is not being seen on the OS. It was showing up on the Raid utility until yesterday, and it disappeared totally this morning; not even showing on the Raid utility now.
Wondering what is going on here.
Thanks.
I still dun understand what you try to meant here. If you are talking about your physical storage, I will suggest you to log a case to your hardware vendor. Seems like your issue here are not relevant to the virtual machine, just your physical raid is gone from your ESX host