Re: New snapshot install throws ERR M on boot continued
On 12/12/11 17:29, Nick Holland wrote: On 12/12/11 16:11, Jeff Ross wrote: On 12/12/11 13:18, Diana Eichert wrote: what is the output of fdisk when booted from bsd.rd? Hi Diana! Thanks for the thought. Disk: sd0 geometry: 487/255/63 [7827456 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 -486 254 63 [ 64: 7823591 ] OpenBSD Looks okay to me. Jeff yeah, that looks fine... How about your disklabel output? I can think of a few things you could do wrong to do that... ERR M indicates that biosboot got installed, but what it was told was the location of /boot is...uh...not. How that's happening...not sure. But, we know the MBR is good, the PBR is good, but what the PBR is pointing at is not. Next step would be to try 5.0-rel to make sure it is not a recent regression. The good thing about how OpenBSD handles flash disks is if something is broke for flash disks, it is typically going to break everywhere (I hope). Nick. Hi Nick! Here's the disklabel: # /dev/rsd0c: type: SCSI disk: SCSI disk label: Nano Pro duid: 4659f17835a3effa flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 128 sectors/cylinder: 8064 cylinders: 970 total sectors: 7827456 boundstart: 64 boundend: 7823655 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 516032 64 4.2BSD 2048 163841 b: 516096 516096swap c: 78274560 unused d: 2564352 1032192 4.2BSD 2048 163841 e: 516096 3596544 4.2BSD 2048 163841 f: 209664 4112640 4.2BSD 2048 163841 g: 1540224 4322304 4.2BSD 2048 163841 h:24192 5862528 4.2BSD 2048 163841 i: 209664 5886720 4.2BSD 2048 163841 j: 516096 6096384 4.2BSD 2048 163841 k: 516096 6612480 4.2BSD 2048 163841 l: 695072 7128576 4.2BSD 2048 163841 I don't see anything wrong here, either. I'll grab the 5.0 rel bsd.rd and give that a go. Jeff
Re: New snapshot install throws ERR M on boot continued
I see a difference in drive paramenters between disklabel and fdisk. diana Past hissy-fits are not a predictor of future hissy-fits. Nick Holland(06 Dec 2005)
Re: New snapshot install throws ERR M on boot continued
On 12/12/11 17:29, Nick Holland wrote: On 12/12/11 16:11, Jeff Ross wrote: On 12/12/11 13:18, Diana Eichert wrote: what is the output of fdisk when booted from bsd.rd? Hi Diana! Thanks for the thought. Disk: sd0 geometry: 487/255/63 [7827456 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 -486 254 63 [ 64: 7823591 ] OpenBSD Looks okay to me. Jeff yeah, that looks fine... How about your disklabel output? I can think of a few things you could do wrong to do that... ERR M indicates that biosboot got installed, but what it was told was the location of /boot is...uh...not. How that's happening...not sure. But, we know the MBR is good, the PBR is good, but what the PBR is pointing at is not. Next step would be to try 5.0-rel to make sure it is not a recent regression. The good thing about how OpenBSD handles flash disks is if something is broke for flash disks, it is typically going to break everywhere (I hope). Nick. 5.0 release on the same Imation Nano Pro also throws ERR M. I used the identical disk layout for the install. To eliminate the chance that there was something wrong with that specific Imation flash drive, I got a SanDisk Cruzer and installed 5.0 release on it, also using the identical layout. Same problem. So, I tried booting this computer off the SanDisk and bam! Booted right off--no problem at all. Same with the Imation Nano. Whatever the problem might be is specific to that Gateway trying to boot off of a flash drive. I did a 5.0 rel install to wd0 and no problems booting from the hard drive. Jeff
Re: New snapshot install throws ERR M on boot continued
On 12/13/11 12:02, Jeff Ross wrote: 5.0 release on the same Imation Nano Pro also throws ERR M. I used the identical disk layout for the install. To eliminate the chance that there was something wrong with that specific Imation flash drive, I got a SanDisk Cruzer and installed 5.0 release on it, also using the identical layout. Same problem. So, I tried booting this computer off the SanDisk and bam! Booted right off--no problem at all. Same with the Imation Nano. Whatever the problem might be is specific to that Gateway trying to boot off of a flash drive. I did a 5.0 rel install to wd0 and no problems booting from the hard drive. Jeff Silly me...forgot how many screwed up (when it comes to booting from USB) BIOSs I've seen... First time I've seen that exact result, but sadly, not surprising. Nick.
New snapshot install throws ERR M on boot continued
Hello, A little more information... I booted back into bsd.rd and ran installboot from that firewall by mounting /dev/sd0a to /mnt, cping the boot file from /usr/mdec to /mnt/boot, and running /usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot sd0 Plus, I saw the little red flashing light so I believe the disk was being written to. However, it still throws an ERR M on boot. Any ideas anyone? Jeff Ross
Re: New snapshot install throws ERR M on boot continued
what is the output of fdisk when booted from bsd.rd?
Re: New snapshot install throws ERR M on boot continued
On 12/12/11 13:18, Diana Eichert wrote: what is the output of fdisk when booted from bsd.rd? !DSPAM:4ee663138802030512579! Hi Diana! Thanks for the thought. Disk: sd0 geometry: 487/255/63 [7827456 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 -486 254 63 [ 64: 7823591 ] OpenBSD Looks okay to me. Jeff
Re: New snapshot install throws ERR M on boot continued
On 12/12/11 16:11, Jeff Ross wrote: On 12/12/11 13:18, Diana Eichert wrote: what is the output of fdisk when booted from bsd.rd? !DSPAM:4ee663138802030512579! Hi Diana! Thanks for the thought. Disk: sd0 geometry: 487/255/63 [7827456 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 -486 254 63 [ 64: 7823591 ] OpenBSD Looks okay to me. Jeff yeah, that looks fine... How about your disklabel output? I can think of a few things you could do wrong to do that... ERR M indicates that biosboot got installed, but what it was told was the location of /boot is...uh...not. How that's happening...not sure. But, we know the MBR is good, the PBR is good, but what the PBR is pointing at is not. Next step would be to try 5.0-rel to make sure it is not a recent regression. The good thing about how OpenBSD handles flash disks is if something is broke for flash disks, it is typically going to break everywhere (I hope). Nick.
