Re: fsck: CANNOT SEEK BLK: -1 (after changing the mainboard)
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]
Really no one knows ?!
Hi, A few days ago I've asked in this message: http://www.freebsd.org/cgi/getmsg.cgi? fetch=1728586+0+/usr/local/www/db/text/2003/freebsd-current/20031109. freebsd-current about suggestions of how to recover the non-root slices from a HDD after the change of the mainbord resulted in not finding the superblock, or at least how to avoid such things in the future. DES suggested You probably switched your disk from CHS to LBA mode or vice versa in this message: http://www.freebsd.org/cgi/getmsg.cgi? fetch=1815326+0+/usr/local/www/db/text/2003/freebsd-current/20031109. freebsd-current which it is not the case. Now, leaving apart that my lest backup dated a month ago, and it's really stupid to lost all your data from a HDD without suffering any hardware or software crash, I would really apreciate some ideas, links whatever about what it is to do to avoid this to happend if the future. Mannyt thanks, IOnut ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Really no one knows ?!
Quoting Putinas Piliponis [EMAIL PROTECTED]: some bioses thinks differently about geometry layout for harddisk 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. btw dont trust to much what it shows you in bios ... This days I tend to not trust anything :-/ The system was istalled on a Gigabyte GA-7VAXP (KT400/8235) and moved _without_any_problem_ on a Gigabyte GA-7VT600 1394 (KT600/8237). The HDD set in BIOS on auto and no custom newfs options. But on this new Gigabyte GA-7VT600L (KT600/8237) it just not working. Now, I'll lose some money due to a dead-line ... I'll do daylly back-ups in the future... This is just my desktop ... with mail, docs and work on it. It's fruntating to see the XP booting up with no problem and loosing all your BSD data ... But what if the same thing happends on one of my servers ? That's what really scares me. if you still have old mb - try to boot from that one, and see what is says and make same with new one ... [..] I would recommend to start from cd, and in sysinstall choose fdisk and after there is option to change / view disk geometry layout ... Yeh, If I was having it probably I wouldn't bother the list so much. But I don't have it. I now the G option, but I don't understand what your suggestion is. Could you please elaborate ? Still, suposing I'll get one MB from my supplier and see what geometry that mobo reports, what should I do to get the HDD working on the new mobo ? Thanks, IOnut ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[no subject]
Quoting Michel TALON [EMAIL PROTECTED]: Just an idea. This occurred to me once that the superblock and primary alternate were corrupted. Hence i was in the same unfortunate situation as you, fsck was not working. The situation was solved by running newfs with the -N flag on the slice. This printed the location of other copies of the superblock. Feeding that to fsck allowed to recover the filesystem, without losing anything. Booted from the Fixit disk. On the /temp: Fixit# newfs -N ad0s2d /dev/ad0s2d: 512.0MB (1048576 sectors) block size 16384, fragment size 2048using 4 cylinder groups of 128.02MB, 8193 blks, 16448 inodes. super-block backups (for fsck -b #) at: 160, 262336, 524512, 786688 Fixit# fsck_ufs -b 262336 -n ad0s2d Alternate super block location: 262336 ** /dev/ad0s2d (NO WRITE) 262336 is not a system superblock. Same with 160, 262336, 524512, 786688 On the /, which when booting from the harddisk and fsck-ing is OK ???: Fixit# newfs -N ad0s2a /dev/ad0s2a: 256.0MB (524288 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 64.02MB, 4097 blks, 8256 inodes. super-block backups (for fsck -b #) at: 160, 131264, 262368, 393472 Fixit# fsck_ufs -b 160 -n ad0s2a Alternate super block location: 160 ** /dev/ad0s2a (NO WRITE) ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups SUMMARY BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no 2123 files, 37012 used, 126839 free (7 frags, 15854 blocks, 0.0% fragmentation) Fixit# newfs -N ad0s2 /dev/ad0s2: 84474.6MB (173003984 sectors) block size 16384, fragment size 2048 using 460 cylinder groups of 183.77MB, 11761 blks, 23552 inodes.super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, 3387328, 3763680, 4140032, 4516384, 4892736, 5269088, 5645440, 6021792, 6398144, 6774496, 7150848, 7527200, 7903552, 8279904, 8656256, 9032608, 9408960, 9785312, 10161664, 10538016, 10914368, 11290720, 11667072, 12043424, 12419776, 12796128, 13172480, 13548832, 13925184, 14301536, 14677888, 15054240, 15430592, 15806944, 16183296, 16559648, 16936000, 17312352, 17688704, 18065056, 18441408, 18817760, 19194112, 19570464, 19946816, 20323168, 20699520, 21075872, 21452224, 21828576, 22204928, 22581280, 22957632, 2984, 23710336, 24086688, 24463040, 24839392, 25215744, 25592096, 25968448, 26344800, 26721152, 27097504, 27473856, 27850208, 28226560, 28602912, 28979264, 29355616, 29731968, 30108320, 30484672, 30861024, 31237376, 31613728, 31990080, 32366432, 32742784, 33119136, 33495488, 33871840, 34248192, 34624544, 35000896, 35377248, 35753600, 36129952, 36506304, 36882656, 37259008, 37635360, 38011712, 38388064, 38764416, 39140768, 39517120, 39893472, 40269824, 40646176, 41022528, 41398880, 41775232, 42151584, 42527936, 42904288, 43280640, 43656992, 44033344, 44409696, 44786048, 45162400, 45538752, 45915104, 46291456, 46667808, 47044160, 47420512, 47796864, 48173216, 48549568, 48925920, 49302272, 49678624, 50054976, 50431328, 50807680, 51184032, 51560384, 51936736, 52313088, 52689440, 53065792, 53442144, 53818496, 54194848, 54571200, 54947552, 55323904, 55700256, 56076608, 56452960, 56829312, 57205664, 57582016, 57958368, 58334720, 58711072, 59087424, 59463776, 59840128, 60216480, 60592832, 60969184, 61345536, 61721888, 62098240, 62474592, 62850944, 63227296, 63603648, 6398, 64356352, 64732704, 65109056, 65485408, 65861760, 66238112, 66614464, 66990816, 67367168, 67743520, 68119872, 68496224, 68872576, 69248928, 69625280, 70001632, 70377984, 70754336, 71130688, 71507040, 71883392, 72259744, 72636096, 73012448, 73388800, 73765152, 74141504, 74517856, 74894208, 75270560, 75646912, 76023264, 76399616, 76775968, 77152320, 77528672, 77905024, 78281376, 78657728, 79034080, 79410432, 79786784, 80163136, 80539488, 80915840, 81292192, 81668544, 82044896, 82421248, 82797600, 83173952, 83550304, 83926656, 84303008, 84679360, 85055712, 85432064, 85808416, 86184768, 86561120, 86937472, 87313824, 87690176, 88066528, 88442880, 88819232, 89195584, 89571936, 89948288, 90324640, 90700992, 91077344, 91453696, 91830048, 92206400, 92582752, 92959104, 93335456, 93711808, 94088160, 94464512, 94840864, 95217216, 95593568, 95969920, 96346272, 96722624, 97098976, 97475328, 97851680, 98228032, 98604384, 98980736, 99357088, 99733440, 100109792, 100486144, 100862496, 101238848, 101615200, 101991552, 102367904, 102744256, 103120608, 103496960, 103873312, 104249664, 104626016, 105002368, 105378720, 105755072, 106131424, 106507776, 106884128, 107260480, 107636832, 108013184, 108389536, 108765888, 109142240, 109518592, 109894944, 110271296, 110647648, 111024000, 111400352, 111776704, 112153056, 112529408, 112905760, 113282112, 113658464, 114034816, 114411168, 114787520, 115163872, 115540224, 115916576, 116292928, 116669280, 117045632,
Re: Really no one knows ?!
- Forwarded message from [EMAIL PROTECTED] - Date: Mon, 10 Nov 2003 13:29:39 +0200 From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Michel TALON [EMAIL PROTECTED] Quoting Michel TALON [EMAIL PROTECTED]: Just an idea. This occurred to me once that the superblock and primary alternate were corrupted. Hence i was in the same unfortunate situation as you, fsck was not working. The situation was solved by running newfs with the -N flag on the slice. This printed the location of other copies of the superblock. Feeding that to fsck allowed to recover the filesystem, without losing anything. Booted from the Fixit disk. On the /temp: Fixit# newfs -N ad0s2d /dev/ad0s2d: 512.0MB (1048576 sectors) block size 16384, fragment size 2048using 4 cylinder groups of 128.02MB, 8193 blks, 16448 inodes. super-block backups (for fsck -b #) at: 160, 262336, 524512, 786688 Fixit# fsck_ufs -b 262336 -n ad0s2d Alternate super block location: 262336 ** /dev/ad0s2d (NO WRITE) 262336 is not a system superblock. Same with 160, 262336, 524512, 786688 On the /, which when booting from the harddisk and fsck-ing is OK ???: Fixit# newfs -N ad0s2a /dev/ad0s2a: 256.0MB (524288 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 64.02MB, 4097 blks, 8256 inodes. super-block backups (for fsck -b #) at: 160, 131264, 262368, 393472 Fixit# fsck_ufs -b 160 -n ad0s2a Alternate super block location: 160 ** /dev/ad0s2a (NO WRITE) ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups SUMMARY BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no 2123 files, 37012 used, 126839 free (7 frags, 15854 blocks, 0.0% fragmentation) Fixit# newfs -N ad0s2 /dev/ad0s2: 84474.6MB (173003984 sectors) block size 16384, fragment size 2048 using 460 cylinder groups of 183.77MB, 11761 blks, 23552 inodes.super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, 3387328, 3763680, 4140032, 4516384, 4892736, 5269088, 5645440, 6021792, 6398144, 6774496, 7150848, 7527200, 7903552, 8279904, 8656256, 9032608, 9408960, 9785312, 10161664, 10538016, 10914368, 11290720, 11667072, 12043424, 12419776, 12796128, 13172480, 13548832, 13925184, 14301536, 14677888, 15054240, 15430592, 15806944, 16183296, 16559648, 16936000, 17312352, 17688704, 18065056, 18441408, 18817760, 19194112, 19570464, 19946816, 20323168, 20699520, 21075872, 21452224, 21828576, 22204928, 22581280, 22957632, 2984, 23710336, 24086688, 24463040, 24839392, 25215744, 25592096, 25968448, 26344800, 26721152, 27097504, 27473856, 27850208, 28226560, 28602912, 28979264, 29355616, 29731968, 30108320, 30484672, 30861024, 31237376, 31613728, 31990080, 32366432, 32742784, 33119136, 33495488, 33871840, 34248192, 34624544, 35000896, 35377248, 35753600, 36129952, 36506304, 36882656, 37259008, 37635360, 38011712, 38388064, 38764416, 39140768, 39517120, 39893472, 40269824, 40646176, 41022528, 41398880, 41775232, 42151584, 42527936, 42904288, 43280640, 43656992, 44033344, 44409696, 44786048, 45162400, 45538752, 45915104, 46291456, 46667808, 47044160, 47420512, 47796864, 48173216, 48549568, 48925920, 49302272, 49678624, 50054976, 50431328, 50807680, 51184032, 51560384, 51936736, 52313088, 52689440, 53065792, 53442144, 53818496, 54194848, 54571200, 54947552, 55323904, 55700256, 56076608, 56452960, 56829312, 57205664, 57582016, 57958368, 58334720, 58711072, 59087424, 59463776, 59840128, 60216480, 60592832, 60969184, 61345536, 61721888, 62098240, 62474592, 62850944, 63227296, 63603648, 6398, 64356352, 64732704, 65109056, 65485408, 65861760, 66238112, 66614464, 66990816, 67367168, 67743520, 68119872, 68496224, 68872576, 69248928, 69625280, 70001632, 70377984, 70754336, 71130688, 71507040, 71883392, 72259744, 72636096, 73012448, 73388800, 73765152, 74141504, 74517856, 74894208, 75270560, 75646912, 76023264, 76399616, 76775968, 77152320, 77528672, 77905024, 78281376, 78657728, 79034080, 79410432, 79786784, 80163136, 80539488, 80915840, 81292192, 81668544, 82044896, 82421248, 82797600, 83173952, 83550304, 83926656, 84303008, 84679360, 85055712, 85432064, 85808416, 86184768, 86561120, 86937472, 87313824, 87690176, 88066528, 88442880, 88819232, 89195584, 89571936, 89948288, 90324640, 90700992, 91077344, 91453696, 91830048, 92206400, 92582752, 92959104, 93335456, 93711808, 94088160, 94464512, 94840864, 95217216, 95593568, 95969920, 96346272, 96722624, 97098976, 97475328, 97851680, 98228032, 98604384, 98980736, 99357088, 99733440, 100109792, 100486144, 100862496, 101238848, 101615200, 101991552, 102367904, 102744256, 103120608, 103496960, 103873312, 104249664, 104626016, 105002368, 105378720, 105755072, 106131424, 106507776, 106884128, 107260480, 107636832, 108013184, 108389536, 108765888, 109142240, 109518592, 109894944, 110271296, 110647648,
Re: fsck: CANNOT SEEK BLK: -1 (after changing the mainboard)
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]
[no subject]
[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 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 probed (disabled) ie0: not probed (disabled) le0: not probed (disabled) lnc0: not probed (disabled) pcic0 failed to probe at port 0x3e0 iomem 0xd on isa0 pcic1: not probed (disabled)
fsck: CANNOT SEEK BLK: -1 (after changing the mainboard)
- 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
