DaemonForums  

Go Back   DaemonForums > FreeBSD > FreeBSD General

FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 5th December 2008
Gemini Gemini is offline
New User
 
Join Date: Dec 2008
Posts: 7
Thanked 0 Times in 0 Posts
Default HDD formatted UFS under AMD64 experiences weirdness under I386

Background:

I installed FreeBSD 7.0-Release/AMD64 onto a 640GB SATA hard drive a few months ago. I sliced the drive with the standard assortment of partitions, but also including a large 550GB s1e partition for my media files.

Things were mostly fine with the install, except that I kept coming across an increasing number of apps that were broken under AMD64.

Eventually, I reinstalled the system using 7.0-Release/I386. I kept the original partitions, simply having sysinstall format them before unrolling the base tarballs.

Everything appeared to go fine until I rebooted. After the kernel was done initializing, garbage characters started appearing on my screen, and exec was complaining that numerous binaries were not proper ELF format. Reboot, and other files came up as garbage.

So, I grabbed my install CD and rebuilt the system again. This time, I deleted all of the partitions except for the 550GB s1e partition. Wash, rinse, repeat. Same garbage on reboot, same issue with binaries not being proper ELF format.

Move to a different computer, download the ISO again, verify Md5 checksum, burn a new CD-R, validate copy, and try again on the original system. No improvement. Run a non-destructive HDD bad sector scanner. No errors.

Grab a spare 10GB hard drive, install 7.0-Release/I386, boot off of it. No problems. Run FSCK against the s1e partition of the 640GB drive, no errors. Mount the partition, no errors. Try to play some of the media files... corrupted. The Md5 fingerprints of almost any file over a few KB in size is off.

Install 6.4-Release/AMD64 on the 10GB drive. Bring everything up and check out the media files on the 640GB drive and... all of the files are fine. Not an error to be found, not an Md5 checksum to be mismatched.

Huh. That's nice.


Question:

Has anyone else encountered this file corruption issue when moving from AMD64 to I386? I didn't see anything jump out in the bug reports.
Reply With Quote
  #2   (View Single Post)  
Old 6th December 2008
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 3,154
Thanked 182 Times in 149 Posts
Default

You could post your experience on the freebsd-stable mailing list, which is monitored by FreeBSD developers. Depending on the feedback you get, you then could file a PR (Problem Report).
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote
  #3   (View Single Post)  
Old 6th December 2008
Gemini Gemini is offline
New User
 
Join Date: Dec 2008
Posts: 7
Thanked 0 Times in 0 Posts
Default

I was most likely going to submit a report, but first wanted to check to see if I wasn't doing something that was already documented as "don't do that".
Reply With Quote
  #4   (View Single Post)  
Old 7th December 2008
lvlamb's Avatar
lvlamb lvlamb is offline
Real Name: Louis V. Lambrecht
Spam Deminer
 
Join Date: May 2008
Location: .be
Posts: 221
Thanked 25 Times in 24 Posts
Default

Are you wining about a 64-bit Intel cpu ?
Check IA-64 vs. x86-64 architecture. Check for AMD compatibility.
Uf coarse, BIOS is written for either one, many BIOSes really are crappy (motherboards sold with ebough CDROM drivers to full a juke-box).

FWIW, here is one fdisk I have, only OpenBSD reads all the data, other fdisks exit normally but either write junk or >/dev/null.
Code:
# fdisk wd0
Disk: wd0	geometry: 10011/255/63 [160836480 Sectors]
Offset: 0	Signature: 0xAA55
            Starting         Ending         LBA Info:
 #: id      C   H   S -      C   H   S [       start:        size ]
-------------------------------------------------------------------------------
 0: B6      0   1  63 -   1000 254  63 [         125:    16080940 ] <Unknown ID>
*1: A6   1001   0   1 -   2000 254  63 [    16081065:    16065000 ] OpenBSD     
 2: 83   2001   0   1 -   4000 254  63 [    32146065:    32130000 ] Linux files*
 3: 05   4001   0   1 -  10010 254  63 [    64276065:    96550650 ] Extended DOS
Offset: 64276065	Signature: 0xB0D7
            Starting         Ending         LBA Info:
 #: id      C   H   S -      C   H   S [       start:        size ]
-------------------------------------------------------------------------------
 0: 94  99190  13  10 - 252985 160   5 [  1593488178:  2470725932 ] Amoeba BBT  
 1: 6D 170160 126  20 -   7322 214  30 [  2733628357:  1678980381 ] <Unknown ID>
 2: E1 129346 194  61 -  67039  52   4 [  2077955772:  3293996339 ] SpeedStor   
 3: 44 183192 158   6 -  82602 231  37 [  2942989439:  2678993577 ] <Unknown ID>
No rw errors though for the last two months, but I finally decided to run the manufacturer's tests and wipe the drive.
Problems are Intel BIOS and hard drive related.

Better fdisk with sysutils/testdisk. Not the user friendly way.
__________________
da more I know I know I know nuttin'
Reply With Quote
  #5   (View Single Post)  
Old 9th December 2008
Gemini Gemini is offline
New User
 
Join Date: Dec 2008
Posts: 7
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by lvlamb View Post
Are you wining about a 64-bit Intel cpu ?
Check IA-64 vs. x86-64 architecture. Check for AMD compatibility.
I am using an AMD Athlon64 X2 model 4850e for both the AMD64 and I386 builds.

So, no, I am not crossing Intel EM64T or Intel IA-64 Itanium builds with this drive.
Reply With Quote
Reply

Tags
amd64, file corruption, i386, migration, ufs

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Anyone with AMD64 random panics on i386? indiocolifa FreeBSD General 13 24th March 2009 02:53 AM
Allow i386 and amd64 to boot from extended DOS partitions lvlamb OpenBSD General 4 16th July 2008 03:24 PM
i386 drivers on amd64 kienjakenobi FreeBSD Ports and Packages 5 25th June 2008 05:37 PM
i386 6.x binaries not working on AMD64 7.x (with compat) lesmando24 FreeBSD General 5 29th May 2008 05:39 AM
Revert from AMD64 to i386 chavez243 FreeBSD General 6 6th May 2008 12:24 PM


All times are GMT. The time now is 10:41 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick