Boot SLES 10 SP2

Hello

I have an instalation of sles 10, on the server i had to change the raid card because it is broken, when booting from the raid it gives an error "waiting for device /dev/disk/by-id/scsi-part2 to apear not found"

Any idea how to fix it?

Best Regards

Install the correct driver.

SLES 10 ?. Gotta be out of support by now, I used it years ago.
We are not here for you to sign up and expect us to solve your problems for you - we will help where we can when you make some effort.

Originally Posted by syg00 Install the correct driver. SLES 10 ?. Gotta be out of support by now, I used it years ago. We are not here for you to sign up and expect us to solve your problems for you - we will help where we can when you make some effort.

It's not about installing the correct driver, it's about the wrong boot table and I can't get it to work. I know that SLES 10 has not been supported for years, that is what SUSE support has told me directly.
I have tried searching all over the internet for any type of solution and I have not succeeded, I have seen videos and various tutorials and nothing. It is an old server and to extract some data from an application I need to start it, and I wanted to avoid removing the information and doing a re-installation. I'm not looking for my problems to be solved by just registering, I've only seen this linux forum and asked as a last attempt so if you could guide me or have any ideas, I would appreciate it.

Thanks for your help

Originally Posted by InfPose waiting for device /dev/disk/by-id/scsi-part2 to apear not found

I doubt it's the precise error message. Not because of the typo, but because "waiting to appear" and "not found" are unlikely to be in the same message.

The computer wants to mount or otherwise use a storage device with SCSI ID "scsi-part2". Which, presumably, is an artefact of the old RAID card. I would boot into rescue mode and check what's wrong with that RAID. Perhaps it generates different SCSI IDs and can be configured. Not sure if SUSE 10 has RAID card tools in rescue mode; if not, perhaps booting from an installation medium helps. Or there is a pre-boot environment, e.g. a utility on the RAID card's Boot-ROM, that helps reconfiguring it.

What server and RAID card type is that? If Proliant, I might be able to dig out some documentation.

Originally Posted by berndbausch I doubt it's the precise error message. Not because of the typo, but because "waiting to appear" and "not found" are unlikely to be in the same message. The computer wants to mount or otherwise use a storage device with SCSI ID "scsi-part2". Which, presumably, is an artefact of the old RAID card. I would boot into rescue mode and check what's wrong with that RAID. Perhaps it generates different SCSI IDs and can be configured. Not sure if SUSE 10 has RAID card tools in rescue mode; if not, perhaps booting from an installation medium helps. Or there is a pre-boot environment, e.g. a utility on the RAID card's Boot-ROM, that helps reconfiguring it. What server and RAID card type is that?

I quote the message that shows:
"Waiting for device /dev/disk/by-id/scsi-xxxxx-part2 to appear............... Not Found -- Exiting to /bin/sh"
Then i can't do anything more, just restart, keyboard is blocked. I see GRUB and Startup Options.

I have tried to start the server with a live cd and I see the information in the folders, user and file.

Is a IBM system x3200m2 and LSI SAS1064E

Originally Posted by InfPose It's not about installing the correct driver, it's about the wrong boot table and I can't get it to work.

Seriously ?.

... I wanted to avoid removing the information and doing a re-installation.

Followed by ...

I have tried to start the server with a live cd and I see the information in the folders, user and file.

Hmmm ... the data are good, the system is not. What is more valuable to your business ?.
If the apps you are running can't be upgraded to something meaningful, your business is (obviously) at risk. Fix the problem, not the symptom.

Totally agree with syg00 here. You changed the RAID card...did you rebuild/rescan the array?? And if you can see your data, I'd *STRONGLY* suggest backing it all up ASAP, before going any further. Beyond that, you're using an out of date version of SLES, making this the perfect time to get a current version installed, and get back under support. You're not getting security fixes or updates using something that's past EOL.

Rebuild the array, do a fresh install of something current, and reload from backups. Get an up to date working system.

Originally Posted by syg00 Seriously ?.Followed by ...Hmmm ... the data are good, the system is not. What is more valuable to your business ?. If the apps you are running can't be upgraded to something meaningful, your business is (obviously) at risk. Fix the problem, not the symptom.

Originally Posted by TB0ne Totally agree with syg00 here. You changed the RAID card...did you rebuild/rescan the array?? And if you can see your data, I'd *STRONGLY* suggest backing it all up ASAP, before going any further. Beyond that, you're using an out of date version of SLES, making this the perfect time to get a current version installed, and get back under support. You're not getting security fixes or updates using something that's past EOL. Rebuild the array, do a fresh install of something current, and reload from backups. Get an up to date working system.

Yes, the RAID configuration is correct, all the menus are correctly configured and the RAID visible and active

-----
It is a server that was forgotten in a warehouse with information from years ago which has to be extracted only once, which has to be contacted with three different companies to restore the data on another server, and that is what I wanted to avoid.

The simplest solution is livecd, copy data from one unit to another, create a virtual machine and dump the data, and from there work with a reliable and robust backup system.

This is what I have found in the company I have been working for recently, a bad job from the beginning

Greetings