scsi-disks: did format-partition-prints, mkdirs, but mount fails
David Combs
So now I've hooked the two (old!) scsi disks up to controler 2,
followed your instructions (I think -- but perhaps clearly NOT),
and got error msg on the mount.
Probably (surely?) something simple that I either left out or
did incorrectly or misspelled.
Here's what I put together to show what happened:
(it's long, but it is as short as I can make it
without leaving out anything.)
(With luck, you can delete 90% of it in any followup.)
-------------------------------------------
----------------------------- I try to mount ONE of the partitions:
exiting .tcshrc
> su -
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
You have new mail.
# id
uid=0(root) gid=0(root) groups=1(other),2(bin),3(sys),4(adm),5(uucp),6(mail),7(tty),8(lp),9(nuucp),12(daemon)
#
#
# mount -F ufs -o ro c2t2d0s0 /export/home/dkc/mnt-c2t2d0s0
mount: c2t2d0s0 or /export/home/dkc/mnt-c2t2d0s0, no such file or directory
#
BUT, NO LUCK.
Please, what stupidity did I commit?
---------------------------------------------------------------------
---------------------------------------------------------------------
------------------------- Here are my actions PREPARING for that try:
---------------------------------------------------------------------
---------------------------------------------------------------------
---- Here is a record of my looking at the two (old, old) scsi-disks:
------------ ~/format--partition--print--12dec09.txt: (text was grabbed from *shell*)
# id
uid=0(root) gid=0(root)
#
#
#
#
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SEAGATE-ST3146807LC-0006 cyl 49780 alt 2 hd 8 sec 720>
/pci@1d,700000/scsi@4/sd@0,0
1. c0t1d0 <SEAGATE-ST3146807LC-6D03 cyl 49780 alt 2 hd 8 sec 720>
/pci@1d,700000/scsi@4/sd@1,0
2. c2t2d0 <IBM cyl 8250 alt 2 hd 6 sec 171>
/pci@1d,700000/scsi@4,1/sd@2,0
3. c2t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@4,1/sd@3,0
Specify disk (enter its number): 2
2
selecting c2t2d0
[disk formatted]
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format>
format>
format> part
part
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition>
partition>
partition> prubt
prubt
`prubt' is not expected.
partition> print
print
Current partition table (original):
Total disk cylinders available: 8250 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 - 598 300.08MB (599/0/0) 614574
1 unassigned wm 599 - 1796 600.17MB (1198/0/0) 1229148
2 unassigned wm 0 - 8249 4.04GB (8250/0/0) 8464500
3 unassigned wm 1797 - 8249 3.16GB (6453/0/0) 6620778
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
partition> q
q
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> disk
disk
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SEAGATE-ST3146807LC-0006 cyl 49780 alt 2 hd 8 sec 720>
/pci@1d,700000/scsi@4/sd@0,0
1. c0t1d0 <SEAGATE-ST3146807LC-6D03 cyl 49780 alt 2 hd 8 sec 720>
/pci@1d,700000/scsi@4/sd@1,0
2. c2t2d0 <IBM cyl 8250 alt 2 hd 6 sec 171>
/pci@1d,700000/scsi@4,1/sd@2,0
3. c2t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@4,1/sd@3,0
Specify disk (enter its number)[2]: 3
3
selecting c2t3d0
[disk formatted]
format>
format> part
part
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition>
partition> print
print
Current partition table (original):
Total disk cylinders available: 14087 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 25 129.19MB (26/0/0) 264576
1 swap wu 26 - 51 129.19MB (26/0/0) 264576
2 backup wu 0 - 14086 68.35GB (14087/0/0) 143349312
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 usr wm 52 - 14086 68.10GB (14035/0/0) 142820160
7 unassigned wm 0 0 (0/0/0) 0
partition>
partition>
partition> q
q
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> q
q
# suspend
suspend
Suspended
> id
id
uid=10101(dkc) gid=10(staff)
>
----------------------------------------------------.
------------------ Here are the mount-point directories I created:
/export/home/dkc:
total 1664703
drwxr-xr-x 45 dkc staff 204 Dec 13 20:45 .
-rw-r--r-- 1 dkc staff 2049 Dec 13 20:45 mount-them.sh
...
...
drwxr-xr-x 2 dkc staff 2 Dec 13 17:43 mnt-c2t3d0s6
drwxr-xr-x 2 dkc staff 2 Dec 13 17:43 mnt-c2t3d0s1
drwxr-xr-x 2 dkc staff 2 Dec 13 17:43 mnt-c2t3d0s0
drwxr-xr-x 2 dkc staff 2 Dec 13 17:43 mnt-c2t2d0s3
drwxr-xr-x 2 dkc staff 2 Dec 13 17:43 mnt-c2t2d0s1
drwxr-xr-x 2 dkc staff 2 Dec 13 17:43 mnt-c2t2d0s0
...
...
-rw-r--r-- 1 dkc staff 6422 Dec 12 23:36 format--partition--print--12dec09.txt
...
...
OH, FWIW, all the above is within a ZFS. (Everyone here (this group) says
that's immaterial.)
---------------------------- Here is what I WANTED to do:
mount -F ufs -o ro c2t2d0s0 /export/home/dkc/mnt-c2t2d0s0 <--- didn't work, gave error.
------ not yet tried, not until I get the above one to work:
mount -F ufs -o ro c2t2d0s1 /export/home/dkc/mnt-c2t2d0s1
mount -F ufs -o ro c2t2d0s3 /export/home/dkc/mnt-c2t2d0s3
mount -F ufs -o ro c2t3d0s0 /export/home/dkc/mnt-c2t3d0s0
mount -F ufs -o ro c2t3d0s1 /export/home/dkc/mnt-c2t3d0s1
mount -F ufs -o ro c2t3d0s6 /export/home/dkc/mnt-c2t3d0s6
-----------------------------
THANKS FOR ANY HELP YOU CAN GIVE!
David
Richard B. Gilbert
> Thanks to everyone for the help a few days ago.
>
> So now I've hooked the two (old!) scsi disks up to controler 2,
> followed your instructions (I think -- but perhaps clearly NOT),
> and got error msg on the mount.
>
> Probably (surely?) something simple that I either left out or
> did incorrectly or misspelled.
>
> Here's what I put together to show what happened:
> (it's long, but it is as short as I can make it
> without leaving out anything.)
>
> (With luck, you can delete 90% of it in any followup.)
>
>
>
>
> -------------------------------------------
>
>
>
> ----------------------------- I try to mount ONE of the partitions:
>
> exiting .tcshrc
>> su -
> Sun Microsystems Inc. SunOS 5.10 Generic January 2005
> You have new mail.
> # id
> uid=0(root) gid=0(root) groups=1(other),2(bin),3(sys),4(adm),5(uucp),6(mail),7(tty),8(lp),9(nuucp),12(daemon)
> #
> #
> # mount -F ufs -o ro c2t2d0s0 /export/home/dkc/mnt-c2t2d0s0
> mount: c2t2d0s0 or /export/home/dkc/mnt-c2t2d0s0, no such file or directory
> #
>
I think that first you should show us the output of:
# ls -al /export/home/dkc/mnt-c2t2d0s0
If it actually exists we can dig a little deeper.
Tim Bradshaw
> # mount -F ufs -o ro c2t2d0s0 /export/home/dkc/mnt-c2t2d0s0
> mount: c2t2d0s0 or /export/home/dkc/mnt-c2t2d0s0, no such file or directory
Did you make a filesystem on the slice?
Zfs..
>
> #
> # mount -F ufs -o ro c2t2d0s0 /export/home/dkc/mnt-c2t2d0s0
> mount: c2t2d0s0 or /export/home/dkc/mnt-c2t2d0s0, no such file or directory
> #
mkfs /dev/rdsk/c2t2d0s0
then
mount -F ufs -o ro /dev/dsk/c2t2d0s0 /export/home/dkc/mnt-c2t2d0s0
Oscar del Rio
>> #
>> # mount -F ufs -o ro c2t2d0s0 /export/home/dkc/mnt-c2t2d0s0
>> mount: c2t2d0s0 or /export/home/dkc/mnt-c2t2d0s0, no such file or directory
>> #
>
>
> mkfs /dev/rdsk/c2t2d0s0
No, that would destroy the data! I got the impression that David wants
to read an old drive.
> mount -F ufs -o ro /dev/dsk/c2t2d0s0 /export/home/dkc/mnt-c2t2d0s0
yup. David was missing the /dev/dsk path in the mount command.
Zfs..
Oops, I thought he wanted to create a newfs on some old disks..
David Combs
Hmmm.
I thought the filesystem existed on the DISK PARTITION?
Hmmm.
I guess that since this is a under an overall zfs, then yes
I have to do that. But I sucn an oldie (sun since 1986) newbie
(work alone, no classes, only this website and sun service -- which
seems to have deteriorated to like zero), so I really have no
idea how to do this.
Please give me a detailed (almost) idiot-proof set of instructions
and example -- THANKS.
Best if some OTHERS do some followups to that to say "yeah, that's what
you should do".
Thanks!
David
David Combs
I'll go do that right now -- plus the "ls" the first responder
asked for.
David
Zfs..
> In article <2009121408081216807-tfb@tfeborg>,
> Tim Bradshaw <t...@tfeb.org> wrote:
>
>
> >> # mount -F ufs -o ro c2t2d0s0 /export/home/dkc/mnt-c2t2d0s0
> >> mount: c2t2d0s0 or /export/home/dkc/mnt-c2t2d0s0, no such file or directory
>
> >Did you make a filesystem on the slice?
>
> Hmmm.
>
> I thought the filesystem existed on the DISK PARTITION?
>
> Hmmm.
>
> I guess that since this is a under an overall zfs, then yes
> I have to do that. But I sucn an oldie (sun since 1986) newbie
> (work alone, no classes, only this website and sun service -- which
> seems to have deteriorated to like zero), so I really have no
> idea how to do this.
>
> Please give me a detailed (almost) idiot-proof set of instructions
> and example -- THANKS.
>
> Best if some OTHERS do some followups to that to say "yeah, that's what
> you should do".
>
> Thanks!
>
> David
The filesystem on s0 is only 300Mb, are you sure this is what you
want ? Are you sure there is a UFS filesystem on it ?
If there is data on that slice then all you need to do is mount it
with the following command.
mount -F ufs -o ro /dev/dsk/c2t2td0s0 /mymountpoint
That will work. I'm not quite sure where zfs comes into this ? What do
you mean by "I guess that since this is a under an overall zfs"
What is the output of zpool list ?
Do you want to use these two new disks as part of a zpool ?
David Combs
THANK YOU!!!
IT WORKS!!!
I dired (emacs) to it, and it's there, subdirs too, etc.
THANK YOU!!!!!
And thank you guys for warning me away from the mkfs!!!!
David
PS: After playing with these disks for a while (looking
for old eg /etc/vfstab, my makeDumpTape.sh file to get
the order of what's on the tape, where (should have had
that printed out on paper! vfstab too!)
(and my 20 yrs of notes and tricks in one huge file, too)
After that, I'll come back to the group and ask about
reading a tape made under UFS into zfs directories (I
think that via ufsrestore it doesn't matter what it
gets extracted into?)
Thanks again!
David
Zfs..
>
> THANK YOU!!!!!
>
> And thank you guys for warning me away from the mkfs!!!!
>
Sorry about that David, that could of been disastrous had you listened
to me. Hope all goes well moving to zfs..
David Combs
Zfs.. <cian.s...@gmail.com> wrote:
...
...
>
>The filesystem on s0 is only 300Mb, are you sure this is what you
>want ? Are you sure there is a UFS filesystem on it ?
>
>If there is data on that slice then all you need to do is mount it
>with the following command.
>
>mount -F ufs -o ro /dev/dsk/c2t2td0s0 /mymountpoint
>
>That will work. I'm not quite sure where zfs comes into this ? What do
>you mean by "I guess that since this is a under an overall zfs"
>
>What is the output of zpool list ?
>
>Do you want to use these two new disks as part of a zpool ?
Golly -- never even crossed my mind!
I think that's way over my head -- these are to be only
*short term* mounts, just so I can grab a few files off
them. So I'd say no. (I mean, the two are like only
5gb each!)
=============================================== MOUNT RESULTS:
=============================================== MOUNT RESULTS:
================================ FAILED! FAILED!
================================ FAILED! FAILED!
================================ FAILED! FAILED!
Well, not entirely:
WORKED FINE FOR PARTITIONS ON ONE DISK,
BUT NOT FOR THE OTHER ONE:
I picked these few lines out of *shell* -- they show
what did and what did NOT work:
--------------- mount errors:::
#
# mount -F ufs -o ro /dev/dsk/c2t2d0s1 /export/home/dkc/mnt-c2t2d0s1
# mount -F ufs -o ro /dev/dsk/c2t2d0s3 /export/home/dkc/mnt-c2t2d0s3
# mount -F ufs -o ro /dev/dsk/c2t3d0s0 /export/home/dkc/mnt-c2t3d0s0
mount: I/O error
mount: Cannot mount /dev/dsk/c2t3d0s0
#
...
...
...
...
> pwd
/export/home/dkc
> id
uid=10101(dkc) gid=10(staff)
> fg
su -
# id
uid=0(root) gid=0(root) groups=1(other),2(bin),3(sys),4(adm),5(uucp),6(mail),7(tty),8(lp),9(nuucp),12(daemon)
# mount -F ufs -o ro /dev/dsk/c2t3d0s1 /export/home/dkc/mnt-c2t3d0s1
mount: /dev/dsk/c2t3d0s1 is not this fstype
#
----------------------------------- end of stuff from *shell*.
Being as it's now just turned to 4am -- my brain is
so fuzzy (and I don't really understand those
error messages), I decided to post this now,
so it'll be there available now, rather than
after I get some zzzz's and it's noon or so here.
Thanks!
(Thanks, actually, for bearing with me through all this;
you guys are really nice to be doing this! And it is
MUCH appreciated!)
David
Now I go read other "new" replies/followups
I haven't yet gotten to. (This I'm responding
to was the first one I saw.)
David Combs
No disaster -- as you could see, I got quickly warned off.
But being sleepy, and ignorant, I am stupid enough to
do that mkfs, even though it's OBVIOUS that I better not!
:-)
Thanks!
Say, up above, I have just posted the problem I now have.
One disk mounted just fine (its partitions, that is),
but not the other one.
I forgot to ask, but I'll do it now, what commands
does solaris-10 have to help figure out the problem?
David
Zfs..
> In article <6bb68fd0-183f-4ce9-a0fd-d8cf89782...@21g2000yqj.googlegroups.com>,
>
> Zfs.. <cian.scrip...@gmail.com> wrote:
>
> >> THANK YOU!!!!!
>
> >> And thank you guys for warning me away from the mkfs!!!!
>
> >Sorry about that David, that could of been disastrous had you listened
> >to me. Hope all goes well moving to zfs..
>
> No disaster -- as you could see, I got quickly warned off.
>
> But being sleepy, and ignorant, I am stupid enough to
> do that mkfs, even though it's OBVIOUS that I better not!
>
> :-)
>
> Thanks!
>
> Say, up above, I have just posted the problem I now have.
>
> One disk mounted just fine (its partitions, that is),
> but not the other one.
>
> I forgot to ask, but I'll do it now, what commands
> does solaris-10 have to help figure out the problem?
>
> David
David, man is your best bet.
man mount
man format
etc...
From your other post it looks as though the other disk does not have a
UFS filesystem on it, can you just try a mount without the -F switch ?
mount -o ro /dev/dsk/c2t3d0s0 /mnt
See what that gives you !
hume.sp...@bofh.ca
"Partition" versus "slice" is an unfortunate bit of confusion that I
think only we BSD and Solaris users have to deal with. When you're dealing
with SPARC gear, you can pretty much use them interchangeably (although
slice is the right term).
On x86/x64, you create a partition to hold the OS, and then slices within the
partition. Filesystems are created within the slices.
--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
hume.sp...@bofh.ca
> mount: Cannot mount /dev/dsk/c2t3d0s0
What does "prtvtoc /dev/dsk/c2t3d0s2" tell you? (Or you can pop into
format and take a look see that way...)
David Combs
<hume.sp...@bofh.ca> wrote:
>David Combs <dkc...@panix.com> wrote:
>>>Did you make a filesystem on the slice?
>> I thought the filesystem existed on the DISK PARTITION?
>
How about "on EACH of a disk's partitions (slices)" -- as what
I should have said -- yes, what I did say was ambiguous. Thanks!
>"Partition" versus "slice" is an unfortunate bit of confusion that I
>think only we BSD and Solaris users have to deal with. When you're dealing
>with SPARC gear, you can pretty much use them interchangeably (although
>slice is the right term).
Maybe. Maybe since solaris. But before that, back in the sunos days,
I recall only the word "partition". "Slice" was part of a saying
that began "best thing since .....d .....!". :-)
>
>On x86/x64, you create a partition to hold the OS,
and then slices within the
>partition. Filesystems are created within the slices.
Isn't M$ wonderful, creating its own language for everything
that already had perfectly good words:
like "folder", for instance.
Thanks!
David
David Combs
Zfs.. <cian.s...@gmail.com> wrote:
...
...
>
>David, man is your best bet.
>
>man mount
>
>man format
>
>etc...
>
>From your other post it looks as though the other disk does not have a
>UFS filesystem on it,
Jeez, it sure USED to. I mean BOTH of those disks were mounted
on my temporarily defunct blade-100 (until I can get someone
to come by and help stretch one of those wide ribbon-cables
just a bit farther so it can plug into the "recepticle" (is that
the correct term?) (I live in New Rochelle, NY, 914-632-1883 --
please someone call and come over and give it a yank...)).
Worked fine then. Unless it got destroyed also when the
(internal) boot disk crashed...
Any way to probe the thing?
There are SO MANY other neat commands for testing
scsi connections (I think!) -- I've read both
man pages recently, word by word, already.
But will try without the -F switch -- won't doing that
maybe cause the thing to catch fire? :-(
>can you just try a mount without the -F switch ?
>
>mount -o ro /dev/dsk/c2t3d0s0 /mnt
>
>See what that gives you !
Thanks!
David
Darren Dunham
c2t3d0s0'.
--
Darren
David Combs
Here's what I just brought downstairs to this xp machine, which is
what I currently use to get into panix (via putty), via sneakernet flash drive.
Here's what I have for now. Later I go back upstairs to the b2500-red
and do the fstyp and fsck:
First, here's this:
----------------------
> id
uid=10101(dkc) gid=10(staff)
>
>
> prtvtoc /dev/dsk/c2t3d0s0
prtvtoc: /dev/rdsk/c2t3d0s0: Permission denied
> j
[1] + Suspended (signal) su -
> fg
su -
# prtvtoc /dev/dsk/c2t3d0s0
* /dev/dsk/c2t3d0s0 partition map
*
* Dimensions:
* 512 bytes/sector
* 424 sectors/track
* 24 tracks/cylinder
* 10176 sectors/cylinder
* 14089 cylinders
* 14087 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 0 264576 264575
1 3 01 264576 264576 529151
2 5 01 0 143349312 143349311
6 4 00 529152 142820160 143349311
#
#
#
# prtvtoc /dev/dsk/c2t3d0s1
* /dev/dsk/c2t3d0s1 partition map
*
* Dimensions:
* 512 bytes/sector
* 424 sectors/track
* 24 tracks/cylinder
* 10176 sectors/cylinder
* 14089 cylinders
* 14087 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 0 264576 264575
1 3 01 264576 264576 529151
2 5 01 0 143349312 143349311
6 4 00 529152 142820160 143349311
#
#
#
# prtvtoc /dev/dsk/c2t3d0s6
* /dev/dsk/c2t3d0s6 partition map
*
* Dimensions:
* 512 bytes/sector
* 424 sectors/track
* 24 tracks/cylinder
* 10176 sectors/cylinder
* 14089 cylinders
* 14087 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 0 264576 264575
1 3 01 264576 264576 529151
2 5 01 0 143349312 143349311
6 4 00 529152 142820160 143349311
#
#
#
# mount -F ufs -o ro /dev/dsk/c2t3d0s0 /export/home/dkc/mnt-c2t3d0s0
mount: I/O error
mount: Cannot mount /dev/dsk/c2t3d0s0
# mount -F ufs -o ro /dev/dsk/c2t3d0s1 /export/home/dkc/mnt-c2t3d0s1
mount: /dev/dsk/c2t3d0s1 is not this fstype
# mount -F ufs -o ro /dev/dsk/c2t3d0s6 /export/home/dkc/mnt-c2t3d0s6
mount: /dev/dsk/c2t3d0s6 is not this fstype
#
#
#
# echo "Now, WITHOUT the -F":
Now, WITHOUT the -F:
#
# mount -o ro /dev/dsk/c2t3d0s0 /export/home/dkc/mnt-c2t3d0s0
mount: I/O error
mount: Cannot mount /dev/dsk/c2t3d0s0
# mount -o ro /dev/dsk/c2t3d0s1 /export/home/dkc/mnt-c2t3d0s1
mount: /dev/dsk/c2t3d0s1 is not this fstype
# mount -o ro /dev/dsk/c2t3d0s6 /export/home/dkc/mnt-c2t3d0s6
mount: /dev/dsk/c2t3d0s6 is not this fstype
#
# id
uid=0(root) gid=0(root) groups=1(other),2(bin),3(sys),4(adm),5(uucp),6(mail),7(tty),8(lp),9(nuucp),12(daemon)
#
#
#
#
# ls /export/home/dkc/mnt-c2t3d0s0
# /export/home/dkc/mnt-c2t3d0s1
/export/home/dkc/mnt-c2t3d0s1: cannot execute
# ls /export/home/dkc/mnt-c2t3d0s1
#
# ls /export/home/dkc/mnt-c2t3d0s6
#
# ls ljljljljlkjlk
ljljljljlkjlk: No such file or directory
# file /export/home/dkc/mnt-c2t3d0s{0,1,6}
/export/home/dkc/mnt-c2t3d0s{0,1,6}: cannot open: No such file or directory
# tcsh
# file /export/home/dkc/mnt-c2t3d0s{0,1,6}
file /export/home/dkc/mnt-c2t3d0s{0,1,6}
/export/home/dkc/mnt-c2t3d0s0: directory
/export/home/dkc/mnt-c2t3d0s1: directory
/export/home/dkc/mnt-c2t3d0s6: directory
#
Now I go walk the dog, then back and do the two things
you asked for.
Thanks!
David
David Combs
Darren Dunham <darren...@gmail.com> wrote:
The fstyp test: 0 was ok (said ufs), but for 1 and 6, said:
Unknown fstyp (no matches)
So, whereas the prtvtoc worked ok on 1 and 6, fstyp didn't.
Not looking so good....
The fsck test said:
Fsck could not find mountpoint /dev/rdsk in mnttab nor vfstab.
Maybe some other way to run the thing?
Thanks!
David
hume.sp...@bofh.ca
> In article <b13607f3-6256-4033...@u36g2000prn.googlegroups.com>,
> Darren Dunham <darren...@gmail.com> wrote:
>>Try running 'fstyp /dev/rdsk/c2t3d0s0' and 'fsck -n /dev/rdsk/
>>c2t3d0s0'.
> Fsck could not find mountpoint /dev/rdsk in mnttab nor vfstab.
I think he meant /dev/rdsk/c2t3d0s0 . The line wrapped.
David Combs
THANK YOU!
I saw it -- and then forgot it, and on re-looking at,
FAILED to see it that time.
I go try it!
David
David Combs
David Combs <dkc...@panix.com> wrote:
>In article <hgc6bq$ult$1...@Kil-nws-1.UCIS.Dal.Ca>,
> <hume.sp...@bofh.ca> wrote:
>>David Combs <dkc...@panix.com> wrote:
>>> In article <b13607f3-6256-4033...@u36g2000prn.googlegroups.com>,
>>> Darren Dunham <darren...@gmail.com> wrote:
>>>>Try running 'fstyp /dev/rdsk/c2t3d0s0' and 'fsck -n /dev/rdsk/
>>>>c2t3d0s0'.
>>
>>> Fsck could not find mountpoint /dev/rdsk in mnttab nor vfstab.
>>
>>I think he meant /dev/rdsk/c2t3d0s0 . The line wrapped.
>>
>>--
>>Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
>
>THANK YOU!
>
>
>I saw it -- and then forgot it, and on re-looking at,
>FAILED to see it that time.
>
>I go try it!
Not good:
# fsck -n /dev/rdsk/c2t3d0s0
fsck -n /dev/rdsk/c2t3d0s0
** /dev/rdsk/c2t3d0s0 (NO WRITE)
CANNOT READ: DISK BLOCK 143278112: I/O error
CONTINUE? no
Program terminated
# fsck -n /dev/rdsk/c2t3d0s1
fsck -n /dev/rdsk/c2t3d0s1
** /dev/rdsk/c2t3d0s1 (NO WRITE)
BAD SUPERBLOCK AT BLOCK 16: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? no
LOOK FOR ALTERNATE SUPERBLOCKS WITH NEWFS? no
SEARCH FOR ALTERNATE SUPERBLOCKS FAILED.
USE GENERIC SUPERBLOCK FROM MKFS? no
USE GENERIC SUPERBLOCK FROM NEWFS? no
SEARCH FOR ALTERNATE SUPERBLOCKS FAILED. YOU MUST USE THE -o b OPTION
TO FSCK TO SPECIFY THE LOCATION OF A VALID ALTERNATE SUPERBLOCK TO
SUPPLY NEEDED INFORMATION; SEE fsck(1M).
#
#
#
# fsck -n /dev/rdsk/c2t3d0s6
fsck -n /dev/rdsk/c2t3d0s6
** /dev/rdsk/c2t3d0s6 (NO WRITE)
BAD SUPERBLOCK AT BLOCK 16: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? no
LOOK FOR ALTERNATE SUPERBLOCKS WITH NEWFS? no
SEARCH FOR ALTERNATE SUPERBLOCKS FAILED.
USE GENERIC SUPERBLOCK FROM MKFS? no
USE GENERIC SUPERBLOCK FROM NEWFS? no
SEARCH FOR ALTERNATE SUPERBLOCKS FAILED. YOU MUST USE THE -o b OPTION
TO FSCK TO SPECIFY THE LOCATION OF A VALID ALTERNATE SUPERBLOCK TO
SUPPLY NEEDED INFORMATION; SEE fsck(1M).
#
#
--------------------- NOW try it without the "-n", but CAREFULLY:
# fsck /dev/rdsk/c2t3d0s0
fsck /dev/rdsk/c2t3d0s0
** /dev/rdsk/c2t3d0s0
CANNOT READ: DISK BLOCK 143278112: I/O error
CONTINUE? y
y
THE FOLLOWING SECTORS COULD NOT BE READ: 143278112 143278113 143278114 143278115
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? n
n
LOOK FOR ALTERNATE SUPERBLOCKS WITH NEWFS? n
n
SEARCH FOR ALTERNATE SUPERBLOCKS FAILED.
USE GENERIC SUPERBLOCK FROM MKFS? n
n
USE GENERIC SUPERBLOCK FROM NEWFS? n
n
SEARCH FOR ALTERNATE SUPERBLOCKS FAILED. YOU MUST USE THE -o b OPTION
TO FSCK TO SPECIFY THE LOCATION OF A VALID ALTERNATE SUPERBLOCK TO
SUPPLY NEEDED INFORMATION; SEE fsck(1M).
#
#
#
#
Nope, not good.
WHAT could have gone wrong?
You can see that I tried ONCE leaving off the "answer NO to every question" option,
but answered "yes" only once.
SUGGESTIONS?
(what was all that stuff about "via mkfs, via newfs"?
Yes, I'll go read the man page (newfs, I guess it is,
since mkfs is, I think I recall, just a simple
way to call it?))
Thank you, guys.
Oh, one hint: NEVER NEVER NEVER turn off the
computer via holding-in the start button
for the required 10 or 20 seconds! NEVER.
That's what I had done on the blade-100 some
months ago; screwed the boot disk, and maybe
this t3-one too. Hell, maybe also the OTHER
internal 20 or whatever gig disk it had --
no way to test it without someone giving me
a hand stretching that wide flat "cable"
that *I* am unable to plug in where it's
supposed to go. (Why didn't Sun give just
a *little* slack, huh?)
(no sun service possible, WAY past its end-of-
hardware-service-life date.)
(Like I say, I'm close (35min metro-north train from grand central, 25
from 125st), in new rochelle).
David
Darren Dunham
> Not good:
>
> # fsck -n /dev/rdsk/c2t3d0s0
> fsck -n /dev/rdsk/c2t3d0s0
> ** /dev/rdsk/c2t3d0s0 (NO WRITE)
>
> CANNOT READ: DISK BLOCK 143278112: I/O error
> CONTINUE? no
How about t2?
From your original post about c2t3d0:
0 root wm 0 - 25 129.19MB (26/0/0)
264576
1 swap wu 26 - 51 129.19MB (26/0/0)
264576
2 backup wu 0 - 14086 68.35GB (14087/0/0)
143349312
3 unassigned wm 0 0
(0/0/0) 0
4 unassigned wm 0 0
(0/0/0) 0
5 unassigned wm 0 0
(0/0/0) 0
6 usr wm 52 - 14086 68.10GB (14035/0/0)
142820160
7 unassigned wm 0 0
(0/0/0) 0
That is a "default" partition layout. It's what you expect to see on
a brand new disk. It is not reasonable for something with real data
on slice 0. The fact that the fsck gets started suggests that there
is a UFS filesystem on here, but it extends farther than the slice
defined in the VTOC. I would enlarge 0 and see if you can get fsck to
pass. You won't be able to access any other filesystems in this state
anyway.
> Program terminated
> # fsck -n /dev/rdsk/c2t3d0s1
> fsck -n /dev/rdsk/c2t3d0s1
> ** /dev/rdsk/c2t3d0s1 (NO WRITE)
> BAD SUPERBLOCK AT BLOCK 16: MAGIC NUMBER WRONG
Even if the VTOC were valid (and it doesn't look it), slice 1 would be
swap, and you can't fsck swap.
> # fsck -n /dev/rdsk/c2t3d0s6
> fsck -n /dev/rdsk/c2t3d0s6
> ** /dev/rdsk/c2t3d0s6 (NO WRITE)
> BAD SUPERBLOCK AT BLOCK 16: MAGIC NUMBER WRONG
Same problem. The label isn't valid, so the start of slice 6 isn't
pointing at a valid filesystem.
> --------------------- NOW try it without the "-n", but CAREFULLY:
I wouldn't do that in this state. You need to change the slice first.
> WHAT could have gone wrong?
Don't know, but the label looks toast to me. Extending to find the
details of the first filesystem is pretty easy. To find other
filesystems on there will be more tedious.
>
> You can see that I tried ONCE leaving off the "answer NO to every question" option,
> but answered "yes" only once.
>
> SUGGESTIONS?
>
> (what was all that stuff about "via mkfs, via newfs"?
> Yes, I'll go read the man page (newfs, I guess it is,
> since mkfs is, I think I recall, just a simple
> way to call it?))
Ignore it. Not applicable to your issue.
> Thank you, guys.
>
> Oh, one hint: NEVER NEVER NEVER turn off the
> computer via holding-in the start button
> for the required 10 or 20 seconds! NEVER.
Shouldn't cause problems like this.
Did the target2 disk look okay? That one has a non-default layout
that I assume is reasonable.
--
Darren