Re: fsck: CANNOT SEEK BLK: -1 (after changing the mainboard)

2003-11-10 Thread itetcu
Quoting Alex Wilkinson [EMAIL PROTECTED]:

   On Fri, Nov 07, 2003 at 09:57:00PM +0200, [EMAIL PROTECTED]
 wrote:

   For reference this is what my AWARD BIOS reads:
   Capacity 120GB
   Access Mode   Auto  CHS   LBALarge
   Cylinder.57460.5746014593.3830
   Head1616..255..240
   Precomp..0.000
   Landing Zone.57459.57459.57459...57459
   Sector.255...25563.255
 
 Did you have to manually type this or did you use a utility to
 gather this table of info ?

By hand.

It seems to me that some Gigabyte MB (with extended fetures like 
SATA or RAID controlers - even when they're not used) report some 
other HDD geometry that the normal ones. I'll try today to test this 
if my supplier has got a new MB shipment.

IOnut


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: fsck: CANNOT SEEK BLK: -1 (after changing the mainboard)

2003-11-07 Thread Dag-Erling Smørgrav
[EMAIL PROTECTED] writes:
 The quick story: after a change of the MB from a GA-7VT600 1393 
 to a GA-7VT600-L, both with VIA Apollo KT600 / 8237 cipset, my 
 system's preen fsck can't find the superblock on partitions other that 
 / As far as I can say the fs where clean (note however that / was 
 mounted read-only AFAIR).

You probably switched your disk from CHS to LBA mode or vice versa.

DES
-- 
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: fsck: CANNOT SEEK BLK: -1 (after changing the mainboard)

2003-11-07 Thread itetcu
Quoting Dag-Erling Smrgrav [EMAIL PROTECTED]:

 [EMAIL PROTECTED] writes:
 The quick story: after a change of the MB from a GA-7VT600 1393 
 to a GA-7VT600-L, both with VIA Apollo KT600 / 8237 cipset, my 
 system's preen fsck can't find the superblock on partitions other
 that 
 / As far as I can say the fs where clean (note however that / was
 mounted read-only AFAIR).
 
 You probably switched your disk from CHS to LBA mode or vice
 versa.
 
 DES

Unfortunatly, I don't think that is the case (and I've checked it 
before posting).

For reference this is what my AWARD BIOS reads:
Capacity 120GB
Access Mode   Auto  CHS   LBALarge
Cylinder.57460.5746014593.3830
Head1616..255..240
Precomp..0.000
Landing Zone.57459.57459.57459...57459
Sector.255...25563.255

If I'm trying CHS or Large in BIOS It will not boot at all, but 
promting me to choose the boot partition with no luck (if I try XP it 
hangs or complain about missing NT..DLL)


I would really apreciate any other sugestion.


IOnut
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


fsck: CANNOT SEEK BLK: -1 (after changing the mainboard)

2003-11-06 Thread itetcu
- Forwarded message from [EMAIL PROTECTED] -
Date: Fri,  7 Nov 2003 08:28:23 +0200
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]

[please keep the [EMAIL PROTECTED] cc and excuse formatting -- webmail, and 
also the typos]

Hi,


The quick story: after a change of the MB from a GA-7VT600 1393 
to a GA-7VT600-L, both with VIA Apollo KT600 / 8237 cipset, my 
system's preen fsck can't find the superblock on partitions other that 
/ As far as I can say the fs where clean (note however that / was 
mounted read-only AFAIR).

I've googled around half a day and the hole night with no luck. The 
system was first on a KT400/8235 mobo and i've moved it with no 
real problem. What is different now ? It has been installed with the 
defaults newfs options.

Questions:
1. in-core disklabel means what is read from the disk ?
2. The sizes are OK, the root slice is OK and I can use it, the first 
FAT32 XP partition is OK and I can boot XP, what makes the diference 
between / and the others ?
3. If the slightly different BIOS is to blame, how to make the newfs 
when installing so that I will not have this problem again in the 
future ?
4. Besides McKusick's paper from 44doc what other sources of 
information on ufs are there ?
5. And, of course :-/ ,  how to get my data back ?


I can provide a dumpfs and/or ffsinfo, if someone cares to see them 
(btw, they still are in 5.1 ? as in the on-line man pages thy are not)


#fsck -p
/dev/ad0s2a: FILESYSTEM CLEAN; SKIPPING CHECKS
/dev/ad0s2a: clean, 89827 free (715 frags, 11139 blocks, 0.6% 
fragmentation)
Cannot find file system superblock
/dev/ad0s2e: CAN'T CHECK FILE SYSTEM.
/dev/ad0s2e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/ad0s2e: CANNOT SEEK BLK: -1
/dev/ad0s2e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Cannot find file system superblock
/dev/ad0s2f: CAN'T CHECK FILE SYSTEM.
/dev/ad0s2f: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/ad0s2f: CANNOT SEEK BLK: -1
/dev/ad0s2f: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Cannot find file system superblock
/dev/ad0s2d: CAN'T CHECK FILE SYSTEM.
/dev/ad0s2d: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Cannot find file system superblock
/dev/ad0s2g: CAN'T CHECK FILE SYSTEM.
/dev/ad0s2g: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/ad0s2g: CANNOT SEEK BLK: -1
/dev/ad0s2g: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.


A fsck -t ufs ad0s2d gives:
** /dev/ad0s2d
Cannot find file system superblock
/dev/ad0s2d: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, 
size 1048576

and fsck_ffs -b 32 isn't of much help either.



*** Working on device /dev/ad0 ***
parameters extracted from in-core disklabel are:
cylinders=232578 heads=16 sectors/track=63 (1008 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=232578 heads=16 sectors/track=63 (1008 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 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
start 63, size 61432497 (29996 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 61432560, size 173003985 (84474 Meg), flag 80 (active)
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED
# /dev/ad0s2:
8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  a:   52428804.2BSD0 0 0 
  b:  4194304   524288  swap
  c: 1730039850unused0 0 # raw part, 
don't edit
  d:  1048576  47185924.2BSD0 0 0 
  e:  1048576  57671684.2BSD0 0 0 
  f: 104857600  68157444.2BSD0 0 0 
  g: 61330641 1116733444.2BSD0 0 0 


The BIOS - LBA reads 14593/255/63 and in dmesg, next to ad0 it is 
232578/16/63.
If I'm booting with the live CD I get:
Offset Size(ST) End
   0.63...1
  63...6143249761432559 ad0s1
61462560..173003985.23443644ad0s2
234436545..2990234439543unused
and the geometry 14593/255/63


Bellow is the tail of boot -v.

ata0: pre reset mask=03 ostat0=50 ostat2=00
ata0-master: ATAPI 00 00
ata0-slave: ATAPI 00 00
ata0: after reset mask=03 stat0=50 stat1=00
ata0-master: ATA 01 a5
ata0: devices=01
ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0
ata1: pre reset mask=03 ostat0=50 ostat2=50
ata1-master: ATAPI 14 eb
ata1-slave: ATAPI 00 00
ata1: after reset mask=03 stat0=00 stat1=50
ata1-slave: ATA 01 a5
ata1: devices=06
ata1 at port 0x376,0x170-0x177 irq 15 on isa0
bt0: not probed (disabled)
cs0: not probed (disabled)
ed0: not probed (disabled)
fe0: not