Re: Fail to boot from snapshot bsd.rd on T1000

Mark Kettenis wrote:
>>  Dave Wilson wrote:
>>> Well, it was worth a try, but it seems the bsd.mp kernel at least is
>>> suffering from the same problem. Of course, this means I probably have
>>> to pull the disk from the machine to put a working kernel on it to be
>>> able to boot again. Poop. I might be lucky and find that bsd works, but
>>> given both bsd.mp and bsd.rd panic, I doubt it.
>>>
>>> Also, I tried to run the commands suggested by the DO THIS OR WE WILL
>>> MOCK YOU instructions, but apparently one of them doesn't exist...
>>>
>>> I would enclose a dmesg, but I can't get that far. The dmesg from bsd.mp
>>> under 4.4-stable is earlier in this thread.
>>>
>>> Si1entDave
>>>
>>>
>>  Further to this, the machine is still sat at the ddb prompt, in case
>>  anyone can tell me what commands I should run to obtain any wanted
>>  information. I'll probably try and fix it tomorrow afternoon.
> 
> Dave,
> 
> Sorry I didn't reply earlier.  There was a bug in vcons(4) driver which I
> fixed on Nov 24.  Should be fixed in the next snapshot.
> 
> Mark
> 
> 

Okay, so there's a new snapshot gone up. Huzzah! Off I go and pull the
drive, bung it in a spare i386 machine I have (the sparc64 box's
predecessor as it happens), up it comes, and then I try and look at the
disk so I can drop the new bsd.rd on it...

anoncvs:~# fdisk wd1
Disk: wd1       geometry: 121601/255/63 [1953525168 Sectors]
Offset: 0       Signature: 0xC074
            Starting         Ending         LBA Info:
 #: id      C   H   S -      C   H   S [       start:        size ]
-------------------------------------------------------------------------------
 0: A0  33418 172   7 -  33418 204  38 [   536871012:        2048 ]
NotebookSave
 1: 14  15668  69   2 -  16712 156  36 [   251710768:    16777376 ] OS/2
hidden
 2: 00      0   0   0 -      0   0   0 [           0:           0 ]
unused
 3: 00      0   0   0 -      0   0   0 [           0:           0 ]
unused
anoncvs:~# disklabel -pg wd1
# /dev/rwd1c:
type: ESDI
disk: ESDI/IDE disk
label: ST31000340AS
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 121601
total bytes: 931.5G
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0

16 partitions:
#                size           offset  fstype [fsize bsize  cpg]
  c:           931.5G             0.0G  unused      0     0
  i:             0.0G           256.0G unknown
  j:             8.0G           120.0G unknown
anoncvs:~#


My Hope: That there's some daft thing I've missed, or some option I need
to set.

My Fear: This is an evil Endianness thing, and I'm screwed unless I can
find another machine of the same endianness, or other similar thing I
don't have. Avoiding re-installing the whole damn thing and having to
re-build ~500GB-worth of mirrors would be nice...

SD