waiting for /dev/sda1 to appear

[ronsrussell]

After installing from the latest VICIbox iso I finished step 1.5 -26. The zypper refresh did not work although routing and dns were working so I decided to reboot. The reboot got to the option of VICIbox v4 or Failsafe VICIbox v4. Either option results in an error that says "waiting for device /dev/sda1 to appear" with something like press enter to fail back to sda1. The hardware is Dell PE1750 with Perc 5i controller configured as RAID1. This box previously had Centos on it. I wiped the hd's before installing.

[gers55]

I might be off track but you might have to do something similar to this.

http://support.microsoft.com/kb/247804

[DomeDan]

Yes I think you're a little off track, but no worries

It seams to be a quite known problem with suse, if you google "waiting for device /dev/sda1 to appear" you will find this:
http://www.novell.com/support/kb/doc.php?id=7009643
just to try it out you can press "e" when you're in grub and change "/dev/sda1" to "/dev/cciss/c0d0p1" and check if that boots

I bet william will show up and write some words regarding this, because he is a Dell guy

[ronsrussell]

Thanks for the suggestion but it did not help. Fdisk shows /dev/sda1 /dev/sda2
Perhaps William could give me a link to the beta of the new Ubuntu VICIbox install?

[DomeDan]

well you can do a scratch install with ubuntu, but I dont think its too hard to get it working with opensuse.

so you get sda1 from fdisk... then you are not using raid. try to configure your raid during boot, remove the raid and add it again and try a install, and during install check if its using sda or c0d0
or just test without a configured raid to see if the raid is the culprint

or you can google the error and find a topic for ubuntu where they added an argument to grub to wait a bit longer

[williamconley]

may also not like your partitioning. but i'd recommend changing your raid approach to whatever you have not tried yet. if you are using raid: stop. if you are using a system with a raid controller but not using raid, try it. you may also try a 3rd party tool to delete all partitions for the heck of it.

i have not experienced this particular error and nobody sitting in the room right now has either. so ... no help here.

as for Ubuntu, we are presently seeking alpha testers for it. i cannot recommend it for production yet, as it has not been alpha'd. fully functional ... untested.

[ronsrussell]

I was able to free up another server to try this install on. This server is a Dell PE1950 with the PERC5i RAID controller configured as RAID1. The install worked just fine on this server. In the next few days I will do some testing on the PE1750 and see if it will work at all. Not sure how not to use raid as it only has SCSI drives attached to the built in RAID controller. Perhaps the controller has a non raid drive setting? But of course that would defeat the purpose of using that type of server but I'm willing to give it a go. Looking at the SUSE forums I see lots of similar unresolved issues.