Here is the summary for my fsck problem that I was having. I honestly dont
know what the problem was but the way I solved it was by running format,
running analyze and then doing the compare analyzation (the disk was empty
so it didn't matter that it wrote all over it) then re-partitioned it,
re-labeled it, re-newfs'd it and now I don't get this weirdness.
Thanks to all that offered help!
Micah
>From casper@holland.Sun.COM Thu Oct 31 10:33:38 1996
Date: Tue, 29 Oct 1996 09:22:39 +0100
From: Casper Dik <casper@holland.Sun.COM>
To: Micah Anderson <micah@smmedia.com>
Subject: Re: fsck problem...
>
>Am I doing something wrong? I just put a 2gig HP scsi drive onto our sparc
>5 for a home directory. I formatted it, newfs'd it and was able to mount
>it and even filled the drive up and removed everything from the drive
>(just to make sure I could), but when I unmount the filesystem and do a
>fsck I get an error about not being able to read certain sectors, is
>something wrong with the drive or did I miss something? My fsck errors are
>appended below, thanks for any assistance.
>
>Micah
>
>Script started on Mon Oct 28 23:08:19 1996
># fsck /dev/rdsk/c0t4d0s0
>** /dev/rdsk/c0t4d0s0
>** Last Mounted on /usr/home
>** Phase 1 - Check Blocks and Sizes
>
>CANNOT READ: BLK 4234848
Since these sectors are all > 2^22 (4194304) this looks like a formatting
problem.
If the disk is only 2GB, then it looks like it's newfs'd for something bigger.
(Check with format how many blocks it has)
Secondly, what OS are you running? Make sure /dev/rdsk/c0t4d0s0 is
indeed a raw disk device. Large disks should work fine in Solaris 2.x.
(Also try truss -t open on fsck to see if it does indeed open the right disk
device)
Casper
>From micah@smmedia.com Thu Oct 31 10:33:45 1996
Date: Mon, 28 Oct 1996 23:20:42 -0800 (PST)
From: Micah Anderson <micah@smmedia.com>
To: Sun Managers mailing list <sun-managers@eecs.nwu.edu>
Subject: fsck problem...
Followup-To: Micah Anderson <micah@smmedia.com>
Am I doing something wrong? I just put a 2gig HP scsi drive onto our sparc
5 for a home directory. I formatted it, newfs'd it and was able to mount
it and even filled the drive up and removed everything from the drive
(just to make sure I could), but when I unmount the filesystem and do a
fsck I get an error about not being able to read certain sectors, is
something wrong with the drive or did I miss something? My fsck errors are
appended below, thanks for any assistance.
Micah
Script started on Mon Oct 28 23:08:19 1996
# fsck /dev/rdsk/c0t4d0s0
** /dev/rdsk/c0t4d0s0
** Last Mounted on /usr/home
** Phase 1 - Check Blocks and Sizes
CANNOT READ: BLK 4234848
CONTINUE? y
THE FOLLOWING SECTORS COULD NOT BE READ: 4234848 4234849 4234850 4234851 4234852 4234853 4234854 4234855 4234856 4234857 4234858 4234859 4234860 4234861 4234862 4234863 4234864 4234865 4234866 4234867 4234868 4234869 4234870 4234871 4234872 4234873 423487
4 4234875 4234876 4234877 4234878 4234879 4234880 4234881 4234882 4234883 4234884 4234885 4234886 4234887 4234888 4234889 4234890 4234891 4234892 4234893 4234894 4234895 4234896 4234897 4234898 4234899 4234900 4234901 4234902 4234903 4234904 4234905 42349
06 4234907 4234908 4234909 4234910 4234911 4234912 4234913 4234914 4234915 4234916 4234917 4234918 4234919 4234920 4234921 4234922 4234923 4234924 4234925 4234926 4234927 4234928 4234929 4234930 4234931 4234932 4234933 4234934 4234935 4234936 4234937 4234
938 4234939 4234940 4234941 4234942 4234943 4234944 4234945 4234946 4234947 4234948 4234949 4234950 4234951 4234952 4234953 4234954 4234955 4234956 4234957 4234958 4234959
CANNOT READ: BLK 4234960
CONTINUE? y
THE FOLLOWING SECTORS COULD NOT BE READ: 4234960 4234961 4234962 4234963 4234964 4234965 4234966 4234967 4234968 4234969 4234970 4234971 4234972 4234973 4234974 4234975 4234976 4234977 4234978 4234979 4234980 4234981 4234982 4234983 4234984 4234985 423498
6 4234987 4234988 4234989 4234990 4234991 4234992 4234993 4234994 4234995 4234996 4234997 4234998 4234999 4235000 4235001 4235002 4235003 4235004 4235005 4235006 4235007 4235008 4235009 4235010 4235011 4235012 4235013 4235014 4235015 4235016 4235017 42350
18 4235019 4235020 4235021 4235022 4235023 4235024 4235025 4235026 4235027 4235028 4235029 4235030 4235031 4235032 4235033 4235034 4235035 4235036 4235037 4235038 4235039 4235040 4235041 4235042 4235043 4235044 4235045 4235046 4235047 4235048 4235049 4235
050 4235051 4235052 4235053 4235054 4235055 4235056 4235057 4235058 4235059 4235060 4235061 4235062 4235063 4235064 4235065 4235066 4235067 4235068 4235069 4235070 4235071
CANNOT READ: BLK 4235072
CONTINUE? y
THE FOLLOWING SECTORS COULD NOT BE READ: 4235072 4235073 4235074 4235075 4235076 4235077 4235078 4235079 4235080 4235081 4235082 4235083 4235084 4235085 4235086 4235087 4235088 4235089 4235090 4235091 4235092 4235093 4235094 4235095 4235096 4235097 423509
8 4235099 4235100 4235101 4235102 4235103 4235104 4235105 4235106 4235107 4235108 4235109 4235110 4235111 4235112 4235113 4235114 4235115 4235116 4235117 4235118 4235119 4235120 4235121 4235122 4235123 4235124 4235125 4235126 4235127 4235128 4235129 42351
30 4235131 4235132 4235133 4235134 4235135
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
6 files, 12 used, 1989740 free (28 frags, 248714 blocks, 0.0% fragmentation)
# exi
script done on Mon Oct 28 23:09:20 1996
>From nobroin@esoc.esa.de Thu Oct 31 10:33:49 1996
Date: Tue, 29 Oct 96 08:31:57 GMT
From: Niall O Broin - Gray Wizard <nobroin@esoc.esa.de>
To: micah@smmedia.com
Subject: Re: fsck problem...
As the blocks which you cannot read are consecutive, I would guess that
when you formatted the drive, some of the drive parameters you used were
wrong. I may well be wrong, and if so, then I'm stuck . . .
Kindest regards,
Niall O Broin
UNIX Network Administrator, Stations and Communications Engineering Department
European Space Operations Centre nobroin@esoc.esa.de
Darmstadt, Germany Ph./Fax +49 6151 90 3619/2179
>From deane@dtmr.com Thu Oct 31 10:33:54 1996
Date: Tue, 29 Oct 1996 06:53:52 -0500
From: "Dean L. Eich" <deane@dtmr.com>
To: Micah Anderson <uunet!smmedia.com!micah@uunet.uu.net>
Subject: Re: fsck problem...
Micah Anderson wrote:
>
> Am I doing something wrong? I just put a 2gig HP scsi drive onto our sparc
> 5 for a home directory. I formatted it, newfs'd it and was able to mount
> it and even filled the drive up and removed everything from the drive
> (just to make sure I could), but when I unmount the filesystem and do a
> fsck I get an error about not being able to read certain sectors, is
> something wrong with the drive or did I miss something? My fsck errors are
> appended below, thanks for any assistance.
>
> Micah
Every disk has some bad blocks, that is what fsck is for. Give fsck the
-y option to answer yes to all the questions it asks you.
ex. fsck -y /dev/rdsk/c0t4d0s0
Dean
____________________________________________________________________
Dean L. Eich deane@dtmr.com phone(301-776-1300)
Systems Administrator/Engineer DTM Research fax(301-776-6154)
317 Main Street Laurel, MD 20707
"Opinions expressed are my own and not those of DTM Research"
____________________________________________________________________
>From jeffw@smoe.org Thu Oct 31 10:33:59 1996
Date: Tue, 29 Oct 1996 07:22:03 -0500
From: Jeff Wasilko <jeffw@smoe.org>
To: Micah Anderson <micah@smmedia.com>
Subject: Re: fsck problem...
Micah Anderson writes:
>
> Am I doing something wrong? I just put a 2gig HP scsi drive onto our sparc
> 5 for a home directory. I formatted it, newfs'd it and was able to mount
> it and even filled the drive up and removed everything from the drive
> (just to make sure I could), but when I unmount the filesystem and do a
> fsck I get an error about not being able to read certain sectors, is
> something wrong with the drive or did I miss something? My fsck errors are
> appended below, thanks for any assistance.
>
> Micah
>
> Script started on Mon Oct 28 23:08:19 1996
> # fsck /dev/rdsk/c0t4d0s0
> ** /dev/rdsk/c0t4d0s0
> ** Last Mounted on /usr/home
> ** Phase 1 - Check Blocks and Sizes
>
> CANNOT READ: BLK 4234848
> CONTINUE? y
>
> THE FOLLOWING SECTORS COULD NOT BE READ: 4234848 4234849 4234850 4234851 4234852 4234853 4234854 4234855 4234856 4234857 4234858 4234859 4234860 4234861 4234862 4234863 4234864 4234865 4234866 4234867 4234868 4234869 4234870 4234871 4234872 4234873 4234
874 4234875 4234876 4234877 4234878 4234879 4234880 4234881 4234882 4234883 4234884 4234885 4234886 4234887 4234888 4234889 4234890 4234891 4234892 4234893 4234894 4234895 4234896 4234897 4234898 4234899 4234900 4234901 4234902 4234903 4234904 4234905 423
4906 4234907 4234908 4234909 4234910 4234911 4234912 4234913 4234914 4234915 4234916 4234917 4234918 4234919 4234920 4234921 4234922 4234923 4234924 4234925 4234926 4234927 4234928 4234929 4234930 4234931 4234932 4234933 4234934 4234935 4234936 4234937 42
34938 4234939 4234940 4234941 4234942 4234943 4234944 4234945 4234946 4234947 4234948 4234949 4234950 4234951 4234952 4234953 4234954 4234955 4234956 4234957 4234958 4234959
>
> CANNOT READ: BLK 4234960
> CONTINUE? y
>
> THE FOLLOWING SECTORS COULD NOT BE READ: 4234960 4234961 4234962 4234963 4234964 4234965 4234966 4234967 4234968 4234969 4234970 4234971 4234972 4234973 4234974 4234975 4234976 4234977 4234978 4234979 4234980 4234981 4234982 4234983 4234984 4234985 4234
986 4234987 4234988 4234989 4234990 4234991 4234992 4234993 4234994 4234995 4234996 4234997 4234998 4234999 4235000 4235001 4235002 4235003 4235004 4235005 4235006 4235007 4235008 4235009 4235010 4235011 4235012 4235013 4235014 4235015 4235016 4235017 423
5018 4235019 4235020 4235021 4235022 4235023 4235024 4235025 4235026 4235027 4235028 4235029 4235030 4235031 4235032 4235033 4235034 4235035 4235036 4235037 4235038 4235039 4235040 4235041 4235042 4235043 4235044 4235045 4235046 4235047 4235048 4235049 42
35050 4235051 4235052 4235053 4235054 4235055 4235056 4235057 4235058 4235059 4235060 4235061 4235062 4235063 4235064 4235065 4235066 4235067 4235068 4235069 4235070 4235071
>
> CANNOT READ: BLK 4235072
> CONTINUE? y
>
> THE FOLLOWING SECTORS COULD NOT BE READ: 4235072 4235073 4235074 4235075 4235076 4235077 4235078 4235079 4235080 4235081 4235082 4235083 4235084 4235085 4235086 4235087 4235088 4235089 4235090 4235091 4235092 4235093 4235094 4235095 4235096 4235097 4235
098 4235099 4235100 4235101 4235102 4235103 4235104 4235105 4235106 4235107 4235108 4235109 4235110 4235111 4235112 4235113 4235114 4235115 4235116 4235117 4235118 4235119 4235120 4235121 4235122 4235123 4235124 4235125 4235126 4235127 4235128 4235129 423
5130 4235131 4235132 4235133 4235134 4235135
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 6 files, 12 used, 1989740 free (28 frags, 248714 blocks, 0.0% fragmentation)
> # exi
> script done on Mon Oct 28 23:09:20 1996
>
>
It sounds like your superblock may be trashed. Do you have
partitions that overlap? Check very carefully.
Jeff
>From rmills@atl1.america.net Thu Oct 31 10:34:04 1996
Date: Tue, 29 Oct 1996 07:25:14 -0500 (EST)
From: "Richard C. Mills" <rmills@atl1.america.net>
To: micah@smmedia.com
Subject: Re: fsck problem...
Hello Micah,
I've never seen that problem before. There are a couple of things you can
try. Go into format, and use repair to fix the sectors. If that doesn't
do the trick, you may need to low-level format your disk - run format with
a "-e" option, select scsi, and then format.
Good luck,
Rich
>
> Am I doing something wrong? I just put a 2gig HP scsi drive onto our sparc
> 5 for a home directory. I formatted it, newfs'd it and was able to mount
> it and even filled the drive up and removed everything from the drive
> (just to make sure I could), but when I unmount the filesystem and do a
> fsck I get an error about not being able to read certain sectors, is
> something wrong with the drive or did I miss something? My fsck errors are
> appended below, thanks for any assistance.
>
> Micah
>
> Script started on Mon Oct 28 23:08:19 1996
> # fsck /dev/rdsk/c0t4d0s0
> ** /dev/rdsk/c0t4d0s0
> ** Last Mounted on /usr/home
> ** Phase 1 - Check Blocks and Sizes
>
> CANNOT READ: BLK 4234848
> CONTINUE? y
>
> THE FOLLOWING SECTORS COULD NOT BE READ: 4234848 4234849 4234850 4234851 4234852 4234853 4234854 4234855 4234856 4234857 4234858 4234859 4234860 4234861 4234862 4234863 4234864 4234865 4234866 4234867 4234868 4234869 4234870 4234871 4234872 4234873 4234
874 4234875 4234876 4234877 4234878 4234879 4234880 4234881 4234882 4234883 4234884 4234885 4234886 4234887 4234888 4234889 4234890 4234891 4234892 4234893 4234894 4234895 4234896 4234897 4234898 4234899 4234900 4234901 4234902 4234903 4234904 4234905 423
4906 4234907 4234908 4234909 4234910 4234911 4234912 4234913 4234914 4234915 4234916 4234917 4234918 4234919 4234920 4234921 4234922 4234923 4234924 4234925 4234926 4234927 4234928 4234929 4234930 4234931 4234932 4234933 4234934 4234935 4234936 4234937 42
34938 4234939 4234940 4234941 4234942 4234943 4234944 4234945 4234946 4234947 4234948 4234949 4234950 4234951 4234952 4234953 4234954 4234955 4234956 4234957 4234958 4234959
>
> CANNOT READ: BLK 4234960
> CONTINUE? y
>
> THE FOLLOWING SECTORS COULD NOT BE READ: 4234960 4234961 4234962 4234963 4234964 4234965 4234966 4234967 4234968 4234969 4234970 4234971 4234972 4234973 4234974 4234975 4234976 4234977 4234978 4234979 4234980 4234981 4234982 4234983 4234984 4234985 4234
986 4234987 4234988 4234989 4234990 4234991 4234992 4234993 4234994 4234995 4234996 4234997 4234998 4234999 4235000 4235001 4235002 4235003 4235004 4235005 4235006 4235007 4235008 4235009 4235010 4235011 4235012 4235013 4235014 4235015 4235016 4235017 423
5018 4235019 4235020 4235021 4235022 4235023 4235024 4235025 4235026 4235027 4235028 4235029 4235030 4235031 4235032 4235033 4235034 4235035 4235036 4235037 4235038 4235039 4235040 4235041 4235042 4235043 4235044 4235045 4235046 4235047 4235048 4235049 42
35050 4235051 4235052 4235053 4235054 4235055 4235056 4235057 4235058 4235059 4235060 4235061 4235062 4235063 4235064 4235065 4235066 4235067 4235068 4235069 4235070 4235071
>
> CANNOT READ: BLK 4235072
> CONTINUE? y
>
> THE FOLLOWING SECTORS COULD NOT BE READ: 4235072 4235073 4235074 4235075 4235076 4235077 4235078 4235079 4235080 4235081 4235082 4235083 4235084 4235085 4235086 4235087 4235088 4235089 4235090 4235091 4235092 4235093 4235094 4235095 4235096 4235097 4235
098 4235099 4235100 4235101 4235102 4235103 4235104 4235105 4235106 4235107 4235108 4235109 4235110 4235111 4235112 4235113 4235114 4235115 4235116 4235117 4235118 4235119 4235120 4235121 4235122 4235123 4235124 4235125 4235126 4235127 4235128 4235129 423
5130 4235131 4235132 4235133 4235134 4235135
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 6 files, 12 used, 1989740 free (28 frags, 248714 blocks, 0.0% fragmentation)
> # exi
> script done on Mon Oct 28 23:09:20 1996
>
>
>
-- ------------------------------------------------------------------------------ Richard Mills - rmills@fair.net ------------------------------------------------------------------------------ >From esilva@netcom.com Thu Oct 31 10:34:09 1996 Date: Tue, 29 Oct 1996 11:30:48 -0800 (PST) From: "Eduardo E. Silva" <esilva@netcom.com> To: micah@smmedia.com Subject: Re: fsck problem...Micah,
When you ran format, it wasn;t just to partition the drive ? if so I suggest you do a low level format, specially if it was connect to a different UNIX box (HP, AIX) or a PC. If this doesn't work your drive is toast...
Micah Anderson wrote: > > > Am I doing something wrong? I just put a 2gig HP scsi drive onto our sparc > 5 for a home directory. I formatted it, newfs'd it and was able to mount > it and even filled the drive up and removed everything from the drive > (just to make sure I could), but when I unmount the filesystem and do a > fsck I get an error about not being able to read certain sectors, is > something wrong with the drive or did I miss something? My fsck errors are > appended below, thanks for any assistance. > > Micah > > Script started on Mon Oct 28 23:08:19 1996 > # fsck /dev/rdsk/c0t4d0s0 > ** /dev/rdsk/c0t4d0s0 > ** Last Mounted on /usr/home > ** Phase 1 - Check Blocks and Sizes > > CANNOT READ: BLK 4234848 > CONTINUE? y > > THE FOLLOWING SECTORS COULD NOT BE READ: 4234848 4234849 4234850 4234851 4234852 4234853 4234854 4234855 4234856 4234857 4234858 4234859 4234860 4234861 4234862 4234863 4234864 4234865 4234866 4234867 4234868 4234869 4234870 4234871 4234872 4234873 4234 874 4234875 4234876 4234877 4234878 4234879 4234880 4234881 4234882 4234883 4234884 4234885 4234886 4234887 4234888 4234889 4234890 4234891 4234892 4234893 4234894 4234895 4234896 4234897 4234898 4234899 4234900 4234901 4234902 4234903 4234904 4234905 423 4906 4234907 4234908 4234909 4234910 4234911 4234912 4234913 4234914 4234915 4234916 4234917 4234918 4234919 4234920 4234921 4234922 4234923 4234924 4234925 4234926 4234927 4234928 4234929 4234930 4234931 4234932 4234933 4234934 4234935 4234936 4234937 42 34938 4234939 4234940 4234941 4234942 4234943 4234944 4234945 4234946 4234947 4234948 4234949 4234950 4234951 4234952 4234953 4234954 4234955 4234956 4234957 4234958 4234959 > > CANNOT READ: BLK 4234960 > CONTINUE? y > > THE FOLLOWING SECTORS COULD NOT BE READ: 4234960 4234961 4234962 4234963 4234964 4234965 4234966 4234967 4234968 4234969 4234970 4234971 4234972 4234973 4234974 4234975 4234976 4234977 4234978 4234979 4234980 4234981 4234982 4234983 4234984 4234985 4234 986 4234987 4234988 4234989 4234990 4234991 4234992 4234993 4234994 4234995 4234996 4234997 4234998 4234999 4235000 4235001 4235002 4235003 4235004 4235005 4235006 4235007 4235008 4235009 4235010 4235011 4235012 4235013 4235014 4235015 4235016 4235017 423 5018 4235019 4235020 4235021 4235022 4235023 4235024 4235025 4235026 4235027 4235028 4235029 4235030 4235031 4235032 4235033 4235034 4235035 4235036 4235037 4235038 4235039 4235040 4235041 4235042 4235043 4235044 4235045 4235046 4235047 4235048 4235049 42 35050 4235051 4235052 4235053 4235054 4235055 4235056 4235057 4235058 4235059 4235060 4235061 4235062 4235063 4235064 4235065 4235066 4235067 4235068 4235069 4235070 4235071 > > CANNOT READ: BLK 4235072 > CONTINUE? y > > THE FOLLOWING SECTORS COULD NOT BE READ: 4235072 4235073 4235074 4235075 4235076 4235077 4235078 4235079 4235080 4235081 4235082 4235083 4235084 4235085 4235086 4235087 4235088 4235089 4235090 4235091 4235092 4235093 4235094 4235095 4235096 4235097 4235 098 4235099 4235100 4235101 4235102 4235103 4235104 4235105 4235106 4235107 4235108 4235109 4235110 4235111 4235112 4235113 4235114 4235115 4235116 4235117 4235118 4235119 4235120 4235121 4235122 4235123 4235124 4235125 4235126 4235127 4235128 4235129 423 5130 4235131 4235132 4235133 4235134 4235135 > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 6 files, 12 used, 1989740 free (28 frags, 248714 blocks, 0.0% fragmentation) > # exi > script done on Mon Oct 28 23:09:20 1996 > > > >
-- _ /\o/\ Thanks! / <_> \ /^^/ \^^\ -Ed /___\ >From casper@holland.Sun.COM Thu Oct 31 10:34:16 1996 Date: Tue, 29 Oct 1996 23:07:03 +0100 From: Casper Dik <casper@holland.Sun.COM> To: Micah Anderson <micah@smmedia.com> Subject: Re: fsck problem...
>Part Tag Flag Cylinders Size Blocks > 0 home wm 0 - 3360 2.02GB (3361/0/0) 4234860 > 2 backup wu 0 - 3361 2.02GB (3362/0/0) 4236120 >
Why the missing track? It shouldn't matter though.
>Running Solaris 2.5.1:
Should work fine.
># ls -l /dev/rdsk/c0t4d0s0 >devices/iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5,8800000/sd@4,0:a,raw
Raw device.
Well, if the errors continue after this last new fs, you may want to disect fsck with truss and see if seek errors are returned.
Casper
_______________________________________________________________________________ Micah Johan Eckman Anderson micah@smmedia.com Sr. Systems Administrator 1-888-614-3709 Schmidt Mead Media, Inc. pagemicah@smmedia.com -------------------------------------------------------------------------------
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:14 CDT