Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Disk problem can't stat device
- Thread starter dandan123
- Start date
The "can't stat" message is because the fsck command cannot open the disk device, because the specified filesystem does not exist... I am guessing you had a file system and data on this disk.
As root, run the format command and see if the OS see the 2nd drive...
As root, run the format command and see if the OS see the 2nd drive...
- Thread starter
- #3
Format sees this drive and the partition table is intact.
The drive has two slices on it s0 and s7, both had file systems on them. The s7 slice has some data I'm trying to preserve. Both slices give me the "can't stat" message. I did a newfs on s0 and now it's ok and I can mount it.
Is there any way I can fix the s7 slice without newfs as this would destroy all my data.
TIA
The drive has two slices on it s0 and s7, both had file systems on them. The s7 slice has some data I'm trying to preserve. Both slices give me the "can't stat" message. I did a newfs on s0 and now it's ok and I can mount it.
Is there any way I can fix the s7 slice without newfs as this would destroy all my data.
TIA
Seems real strange that both slices are bad... Are you using the following commands:
fsck /dev/rdsk/c#t#d#s7
mount /dev/dsk/c#t#d#s7 /mnt
Just want to make sure you are not trying to mount a raw device or trying to run fsck on a static device.
fsck /dev/rdsk/c#t#d#s7
mount /dev/dsk/c#t#d#s7 /mnt
Just want to make sure you are not trying to mount a raw device or trying to run fsck on a static device.
- Thread starter
- #5
Other than you hard drive being bad or the partition table being changed, the only thing I can think of is the super block is corrupted. Why this happened on both partitions seem to point to the hard drive is bad. You can try using an alternate super block to see if you can read the read the disk... The command is:
fsck -o b=32 /dev/rdsk/c#t#d#s7
fsck -o b=32 /dev/rdsk/c#t#d#s7
- Thread starter
- #7
- Thread starter
- #9
- Thread starter
- #10
Peculiar problem.
I was able to do a newfs on c0t1d0s7 but I can't fsck the raw devic.. I keep getting "can't stat"
I can even mount the partition.
Finally I re-partitioned the drive deleted the s7 partition and allocated all the space to the s6 partition and everything works fine.
For some reason it doesn't seem to like the s7 partition.
Anyone know why ?
I was able to do a newfs on c0t1d0s7 but I can't fsck the raw devic.. I keep getting "can't stat"
I can even mount the partition.
Finally I re-partitioned the drive deleted the s7 partition and allocated all the space to the s6 partition and everything works fine.
For some reason it doesn't seem to like the s7 partition.
Anyone know why ?
- Status