Your LVM does not seem to be under the impression that there is something on /dev/sdb1. Since it was a RAID 0 component disk, I assume you had to fully re-create the VG and restore the data from backups.
The commands like "pvs" or "pvdisplay" without arguments will display error messages about /dev/sdb1 because they will probe *all* the disks kernel knows about. So the problem is that the kernel has not been told that /dev/sdb is completely and irrevocably gone. (When a disk device just vanishes while the system is running, the kernel holds the device name in case the disk comes back later.)
Booting the system should certainly fix it, but there's an easier way to tell the kernel that a particular disk device is gone and won't come back:
echo 1 > /sys/block/sdb/device/delete
This should stop the error messages from tools like "pvdisplay" or "pvs".
On SLES, there might also be some files related to persistent device naming in /etc/udev/rules.d/ directory. If I recall correctly, there is one file that includes some physical identifier of each disk (like a WWID or a serial number) and the assigned device name, like "sdb".
If you want to allow the name /dev/sdb to be reassigned to some future disk, you may have to remove the current association. But if you don't care about it, you don't have to do it.
MK
MK
