Skip to main content

Cleaning up ZFS

I have a Sun USS 7110 with some issues.  I have had to swap OS drives between machines, at one point the drives were formatted for Linux, etc... At the end of the day, the USS 7110 (basically a Sun x4200) is most useful as it's intended purpose, a Unified Storage Array - imagine that? ;-)

Anyhow... once you have the 2 OS drives configured correctly... go to work
# echo | format | awk '{ print $2 }'


DISKS="c0t5000CCA0002AF4B8d0
c0t5000CCA0002B33A0d0
c0t5000CCA0002CED64d0
c0t5000CCA0002D9A8Cd0
c0t5000CCA0002D9A44d0
c0t5000CCA0007AA6F4d0
c0t5000CCA0007ABB18d0
c0t5000CCA0007ABDBCd0
c0t5000CCA0007B632Cd0
c0t5000CCA0007B3934d0
c0t5000CCA00019B378d0
c0t5000CCA00031D8CCd0
c0t5000CCA000222E5Cd0
c0t5000CCA0002874C4d0"

#c0t5000CCA0002CE1C4d0  -- OS Drive
#c0t5000CCA00029536Cd0  -- OS Drive


for DISK in $DISKS
do
  echo "dd if=/dev/zero of=/dev/rdsk/${DISK} bs=1024 count=72000"
  dd if=/dev/zero of=/dev/rdsk/${DISK} bs=1024 count=72000
done


for DISK in $DISKS
do
  echo "echo \"y\" | fdisk ${DISK}"
  echo "y" | fdisk ${DISK}
done


format -e $DISK

lab
0
y
q





To scan for non-imported Zpools (seems strange to me)

uss01# zpool import 



Comments

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.