Error: Can't open /dev/rdsk/c0t0d0s0
Rudy Hillen
I have moved disk0 from one Ultra1 to another Ultra1
Upon boot, the new machine is trying to fsck /dev/rdsk/c0t0d0s0
(dispite entry in /etc/vfstab to the contrary)
The root password is given to attempt to fsck the disk manually.
The error message is that the device cannot be opened.
At this point, the filesystem is mounted read-only, so no
changes can be made.
I have put the disk0 into another machine and run fsck, finding no
errors.
I have mounted to the 2.6 intallation cdrom, then I can
fsck the disk or mount /dev/dsk/c0t0d0s0 to /a
Can anyone help me bypass the fsck at boot?
TIA
Rudy
Andrew Gabriel
Rudy Hillen <ru...@nortelnetworks.com> writes:
> Hey
>
> I have moved disk0 from one Ultra1 to another Ultra1
> Upon boot, the new machine is trying to fsck /dev/rdsk/c0t0d0s0
> (dispite entry in /etc/vfstab to the contrary)
Did you change _both_ columns in /etc/vfstab?
--
Andrew Gabriel
Rudy Hillen
#device device mount FS fsck mount
mount
#to mount to fsck point type pass at boot
options
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs - no -
Darren Dunham
> Hey
> I have moved disk0 from one Ultra1 to another Ultra1
> Upon boot, the new machine is trying to fsck /dev/rdsk/c0t0d0s0
> (dispite entry in /etc/vfstab to the contrary)
> The root password is given to attempt to fsck the disk manually.
> The error message is that the device cannot be opened.
> At this point, the filesystem is mounted read-only, so no
> changes can be made.
You could force the remount, but I'll bet you'll get a similar error.
mount -o remount,rw /dev/dsk/c0t0d0s0 /
What does 'format' show for installed disks?
--
Darren Dunham ddu...@taos.com
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< Please move on, ...nothing to see here, please disperse >
Rudy Hillen
an error, prompts for you to enter root password and run fsck manually.
upon entering the root password, fsck /dev/dsk/c0t0d0s0 (and rdsk)
says no device file found.
format says no disk found.
boot to the cdrom and I can fsck and mount and format shows the disk.
the device files seem to be there when c0t0d0s0 is mounted /a
(also did touch of /a/reconfigure while I had c0t0d0s0 mounted at /a )
Rudy
Rudy Hillen
Now, the errors indicate: cant open this/that/the other...
I assume because the whole filesystem is now mounted readonly.
I believe I am in the bad part of town at this point
and something is wrong from earlier in the boot process.
Rudy Hillen wrote:
>
> Hey
>
> I have moved disk0 from one Ultra1 to another Ultra1
> Upon boot, the new machine is trying to fsck /dev/rdsk/c0t0d0s0
> (dispite entry in /etc/vfstab to the contrary)
>
> The root password is given to attempt to fsck the disk manually.
> The error message is that the device cannot be opened.
> At this point, the filesystem is mounted read-only, so no
> changes can be made.
>
Rudy Hillen
I reinstalled the bookblk to c0d0d0s0.....Same thing.
Darren Dunham
> (also did touch of /a/reconfigure while I had c0t0d0s0 mounted at /a )
That doesn't do anything because reconfigure can't write anything until
root is mounted read/write.
>> mount -o remount,rw /dev/dsk/c0t0d0s0 /
Did you try that?
The other thing that some have done is to copy the /dev tree from the
cdrom boot onto /a/dev. I've never tried it, but it may work for you.
Darren Dunham
You can't just 'get by' it. The fsck failure is a symptom of an error,
not a cause.
The problem is that the disk devices aren't working properly.
> Now, the errors indicate: cant open this/that/the other...
> I assume because the whole filesystem is now mounted readonly.
Correct.
> I believe I am in the bad part of town at this point
> and something is wrong from earlier in the boot process.
Well although you say these are both Ultra 1's, it seems like there are
some differences between them. Are you certain you've inserted the
drive into the exact same slot and everything? I don't know why all the
devices aren't working for you.
In my previous message where I suggested you could copy /dev from the
cdrom, you'd probably need to copy both /devices and /dev.
I'd keep a backup of the old directories if you don't want this disk to
become even worse than it is.