Subject: "bad PBR sig" - msg#00043

Previous Message by Date: (click to view message preview)

Re: problem installing

On Thu, 2006-02-09 at 19:21 -0800, siucdude wrote: > I have used alpha1 for a while after yesturdays crash i have decided to > download and install alpha2 clean install, but huston we have a problem, my > install goes from "preparing file system" to "set root password", so myabe > two questions. > > is there still a place where i can get alpha1. my cd lost > or > what could this be. try to search on the web. search as +nexenta +alpha1. or something similar. but before your rollback, could you please describe your problem in more details? i.e. if this is a bug, we need to fix it... right? -- Erast

Next Message by Date: click to view message preview

Re: "bad PBR sig"

Ferenc Veres wrote: > I get a little red "Bad PBR sig" message, and nothing else, after > installing Alpha 2 on my Sun Ultra 20 workstation (bought that today, > wow ;-) ). That means the Solaris boot record signature is bad. > I partitioned manually using the following disk selection (I am not sure > I understand everything correctly): > > fdisk : waxed all the original Solaris 10 stuff, created a 25% partition > of "solaris2" type. (type selection:1) > > partition: I went to this tool, I saw the old partitions, so I rebooted, > then I went to this tool again, 25% was fine, And did you double check that such a partition is marked "active"? > I deleted all patitions by typing "unassigned" name and 0 to 0 as size. > > Then I created: > > 0 root ~8GB (/) > 1 swap ~1GB > 2 home ~10GB (/export) > > Additionally I saw cylinders 1, 2 busy with system stuff, like "boot" or > something like that. They had partition number 8 and 9 and could not be > changed (fortunately coz I almost deleted those two too :-) ). You can only start from cylinder 3, because 0, 1 and 2 are system-reserved for slices 8 and 9. > Installation went fine. (Playing tetris.) > > Any ideas how to fix PBR? > > Please help! :-) Can't use my SUN this way. :-D Bought it to solve the > Athlon problem. Hehe, not only. :-) So several things to check: a. Make sure the partition is marked as active before you begin your installation. b. You'd need to install GRUB, whether in MBR or inside the partition itself. If it's the latter (e.g. you have Linux GRUB on MBR), then you'd need to chainload Solaris's MBR since Linux's doesn't understand Solaris VTOC. c. You can try to fix it by booting from InstallCD, followed by re-installing GRUB on the partition. E.g. if your root file system is /dev/dsk/c0d0s0 then do: % installgrub -m /dev/rdsk/c0d0s0 (The -m flag is for MBR, so remove that if you don't want to install on MBR.) > Additional mini-questions: > > 1. Installer said [32 bit] for all options and there is no another CD > download. Did it actually install the 64 bit version anyway? Yes. You can double check by checking for "amd64" subdirs throughout the root file system. > 2. Is there any disk or partition and fs type I could share a large disk > space between Linux and Solaris? E.g. > > 10GB Nexenta / > 10GB Nexenta /home (or /export actually) > 10GB Linux / > 10GB Linux /home > 40GB /data for both?? Not on the same machine, because Linux can't read ufs and Solaris cannot read extfs/reiserfs/etc. But if you do it over the network then you can use NFS :) -- Mac

Previous Message by Thread: click to view message preview

problem installing

I have used alpha1 for a while after yesturdays crash i have decided to download and install alpha2 clean install, but huston we have a problem, my install goes from "preparing file system" to "set root password", so myabe two questions. is there still a place where i can get alpha1. my cd lost or what could this be. this is a full install on dell c400 laptop. i checked the cd on vmware and it worked so i don't think its that. thanks

Next Message by Thread: click to view message preview

Re: "bad PBR sig"

Ferenc Veres wrote: > I get a little red "Bad PBR sig" message, and nothing else, after > installing Alpha 2 on my Sun Ultra 20 workstation (bought that today, > wow ;-) ). That means the Solaris boot record signature is bad. > I partitioned manually using the following disk selection (I am not sure > I understand everything correctly): > > fdisk : waxed all the original Solaris 10 stuff, created a 25% partition > of "solaris2" type. (type selection:1) > > partition: I went to this tool, I saw the old partitions, so I rebooted, > then I went to this tool again, 25% was fine, And did you double check that such a partition is marked "active"? > I deleted all patitions by typing "unassigned" name and 0 to 0 as size. > > Then I created: > > 0 root ~8GB (/) > 1 swap ~1GB > 2 home ~10GB (/export) > > Additionally I saw cylinders 1, 2 busy with system stuff, like "boot" or > something like that. They had partition number 8 and 9 and could not be > changed (fortunately coz I almost deleted those two too :-) ). You can only start from cylinder 3, because 0, 1 and 2 are system-reserved for slices 8 and 9. > Installation went fine. (Playing tetris.) > > Any ideas how to fix PBR? > > Please help! :-) Can't use my SUN this way. :-D Bought it to solve the > Athlon problem. Hehe, not only. :-) So several things to check: a. Make sure the partition is marked as active before you begin your installation. b. You'd need to install GRUB, whether in MBR or inside the partition itself. If it's the latter (e.g. you have Linux GRUB on MBR), then you'd need to chainload Solaris's MBR since Linux's doesn't understand Solaris VTOC. c. You can try to fix it by booting from InstallCD, followed by re-installing GRUB on the partition. E.g. if your root file system is /dev/dsk/c0d0s0 then do: % installgrub -m /dev/rdsk/c0d0s0 (The -m flag is for MBR, so remove that if you don't want to install on MBR.) > Additional mini-questions: > > 1. Installer said [32 bit] for all options and there is no another CD > download. Did it actually install the 64 bit version anyway? Yes. You can double check by checking for "amd64" subdirs throughout the root file system. > 2. Is there any disk or partition and fs type I could share a large disk > space between Linux and Solaris? E.g. > > 10GB Nexenta / > 10GB Nexenta /home (or /export actually) > 10GB Linux / > 10GB Linux /home > 40GB /data for both?? Not on the same machine, because Linux can't read ufs and Solaris cannot read extfs/reiserfs/etc. But if you do it over the network then you can use NFS :) -- Mac