From owner-freebsd-questions Thu Jan 10 14: 6: 7 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mail.mango-bay.com (mail.mango-bay.com [208.206.15.12]) by hub.freebsd.org (Postfix) with ESMTP id 4B2DD37B41B for ; Thu, 10 Jan 2002 14:05:58 -0800 (PST) Received: from barbish ([63.70.155.107]) by mail.mango-bay.com (Post.Office MTA v3.5.3 release 223 ID# 0-52377U2500L250S0V35) with SMTP id com; Thu, 10 Jan 2002 17:08:39 -0500 From: "Joe & Fhe Barbish" To: "Steven Kirk" Cc: "FBSD Questions" Subject: RE: Slices, and Partitions, and Tigers, OH MY! Date: Thu, 10 Jan 2002 17:05:50 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Back out the firmware update on the SCSI backplane. There is nothing you can do in FBSD to compensate for the way the new firmware is accessing the disk. If you are lucky the data slice can still be read once you get back to the way the scsi drives worked before the scsi upgrade. -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Steven Kirk Sent: Thursday, January 10, 2002 3:58 PM To: freebsd-questions@freebsd.org Subject: Slices, and Partitions, and Tigers, OH MY! You'll be glad to know this is not your standard "I don't know how to partition my drive" question :) I have two physical drives in my system (a server): /dev/amrds0 - for the OS /dev/amrds1 - for my data Well, something happened (don't know what, how, why etc) but now the partition/slice entries are fubar'd. It started after I did a firmware update on the SCSI backplane. It installed fine, so I don't know what happened to cause this. At this point I just need to recover, then I can root-cause it afterwards. Don't care about the first (OS) drive -- that's easily rebuilt. It's the data drive which has had me up for two days trying to save. Anytime I attempt to access the drive, I get a series of kernel messages: /kernel: amrd1: raw partition size != slice size /kernel: amrd1: start 63, end 8369864, size 8369802 #(this is incorrect) /kernel: amrd1c: start 63, end 143107019, size 143106957 #(this is correct) /kernel: amrd1e: start 63, end 143107019, size 143106957 /kernel: amrd1: truncating raw partition /kernel: amrd1: rejecting partition in BSD label: it isn't entirely within the slice I've tried installing the OS (FreeBSD 4.4) back onto the OS drive (start from scratch)(no amrd1 NOT in the system). The install went fine, no errors. Then I run /stand/sysinstall to add the data drive into the system, but I get the kernel messages when sysinstall starts up & probes devices. I'm VERY wary of making any changes thru fdisk or disklabel for fear of losing anything that's still there. I've tried installing FreeBSD 4.2, 4.3, and 4.4, all get the same error. I've tried mounting the drive under Linux, but I get a cryptic error (reclen does not match namelen, directory #2 -- ??). I tried running "fsck -n /dev/amrd1s1e" (and variations) to see if fsck could maybe see the errors enough to repair them, but again the kernel messages spew out, and fsck reports wrong superblock. so.... I'm open to any ideas. I'm really rather desperate to save what's on this drive. Thoughts, ideas, theories...all are welcome! Thanks! --Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message