disklabel and fdisk can't write to disk. Interactive versions?
From: Dr. Richard E. Hawkins (hawk_at_slytherin.ds.psu.edu)
Date: 01/20/05
- Next message: Pertti Kosunen: "Re: Network Configuration"
- Previous message: jpd: "Re: User Mount of da0s1a crashes kernel"
- Next in thread: Dorian Büttner: "Re: disklabel and fdisk can't write to disk. Interactive versions?"
- Reply: Dorian Büttner: "Re: disklabel and fdisk can't write to disk. Interactive versions?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 20 Jan 2005 18:21:34 +0000 (UTC)
I'm now seeing this on a couple of systems. One has source from January
10, the other from mid december. Both are 5.x.
When I run fdisk and dislabel from /stand/sysinstall, I get a message
"ERROR: Unable to write data to disk dao!"
(100%)
This happens on all four scsi drives on this system, and on the two ide
drives I tried on the home system. I get the same error from the
disklabel within /stand/sysinstall.
On my home system, with nothing important to lose, I held my breath and
manually edited (with disklabel, I think). That wrote successfully.
Am I missing something here? If it was one or two drives, I'd blaim
hardware. However, this system has high-end drives (15krpm), and one of
the drives on the home system is brand new.
Oh, dear, now it's worse. I just ran the interactive version with
"fdisk -i /dev/da0". /dev/da0s1f is still mounted, and still working,
but the interactive version of fdisk from systinstall and the
command line version are reporting different things.
The command line yields:
slytherin# fdisk /dev/da0
******* Working on device /dev/da0 *******
parameters extracted from in-core disklabel are:
cylinders=2213 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2213 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 35551782 (17359 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 164/ head 254/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
while the interac tive shows:
Offset Size(ST) End Name PType Desc Subtype
Flags
0 16000740 16000739 da0s3 4 unknown 0
16000740 19565738 35566477 - 12 unused 0
What is going on here? The command line is correct, and is what *used*
to be the configuration, and still *should* be. The interactive only
lists slice 3, which shouldn't exist, as slice 1 is the entire disk.
hawk, baffled
hawk
-- Richard E. Hawkins, Asst. Prof. of Economics /"\ ASCII ribbon campaign dochawk@psu.edu 111 Hiller (814) 375-4846 \ / against HTML mail Find commentary on law, economics, and X and postings. other issues of the day at dochawk.org! / \
- Next message: Pertti Kosunen: "Re: Network Configuration"
- Previous message: jpd: "Re: User Mount of da0s1a crashes kernel"
- Next in thread: Dorian Büttner: "Re: disklabel and fdisk can't write to disk. Interactive versions?"
- Reply: Dorian Büttner: "Re: disklabel and fdisk can't write to disk. Interactive versions?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
