This came up in an earlier thread of mine, but I didn't pay attention. Now I have to. I have tried several commercial Backup Programs with Disaster Recovery. Most all are unable to do a Disaster Recovery on OpenSuSE because the "New" Drive ID does not Match the original. So the boot will fail. Easy to repair, but adds too much time to the recovery... Others have "solved" the problem by creating there own partitions (ext2/ext3) and Grub Entry. That's fine except when I tried that, the Windows Clients could no longer connect. I didn't check that out to see if it was a simple problem, I'll go to the site a play with that this weekend. But, I'd like to understand better why this boot from Drive ID, and if I have any control over that. In particular trying to do a Bare Metal Recovery on new hardware... These are all simple Samba Servers on 10.3 32 bit... behind a router. acting as a Workgroup. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org