Eugene Kazarinov
2006-Oct-17 18:21 UTC
6.2-pre: g_vfs_done():ad4s1d[READ(offset=-8573723385966362624, length=16384)]error=5
IMHO very "nice" offset. It worked on ali chip, about wich I ask in message with topic: "cant start 18, 21-24 hdd drives on 6.2-PRERELEASE/amd64. pls pls hel" I mean sata drive that freebsd fand on ali controller - ad26 (seagate 320 gb 7200.10 sata II) fsck doesnt fix it. It hangs on [root@ddf /usr/home/kamuzon]# fsck -vf /dev/ad26s1d start /data26 wait fsck_ufs -f /dev/ad26s1d ** /dev/ad26s1d ** Last Mounted on /data26 ** Phase 1 - Check Blocks and Sizes>From single user cant fsck cause it wants swap.In normal user with swap 1gb fsck dies cause "swap is full" I make swap 320gb (full another hdd) and fsck hangs after "7651M Used" 8-( ) Swap: 32G Total, 7651M Used, 25G Free, 23% Inuse Sometime I got "cant write snap shot" 8-( ) Now I insert this hdd on 6.1-release/i386 and sil3114 controller scan_ffs faund this: block 588464544 id 4515c9a9,84e3a0df size 156284320 block 588486331 id e059b36b,390b9380 size 5555758927689266374 block 588840800 id 4515c9a9,84e3a0df size 156284320 after block 640 000 000 or near that scan_ffs dies with something like "segmentation fault" - I dont remember. Then I start mc and go to dir on this hdd - system hangs with subject. Then I make ls in directory on that drive - ok. I see filelisting. If I try ls -la - system hangs with subj (on first console this line run and run up). Some files I can copy/move from this drive. On some I get "Bad file descriptor". On some system hangs with subject on first console and this line run and run up. seagate hddtools full check drive and founds nothing. It says "all ok". That should I do to help resolve this problem in FreeBSD code? Or this problem is not in code and I can make newfs on this hdd and live forever on sil3114? ;) PS Maybe ali controller doesnt support 320-gb hdd drives or near that and it corrupt transferred data and fil system? Or ali doesnt support 64bit pointers? Why this can happens? Shit happens - I know. ;)