pablo@mrspoc.Transact.COM (Pablo Sanchez) (08/20/90)
Hi, I spent this lovely weekend replacing our primary disk on an Everex 386/25. The problem is that when I try to mount the two partitions on the second disk I get a mount error: mount: cannot access special file mount: No such device or address Oh yeah, the first time that I try the mount I get a message as follows: %disk - - - cyl: xxxx head: xxx sec/trk: xxx something like that. Anyway, was there something stored on the primary disk besides the special files in /dev that wasn't restored when I restored the files? Do I have to run ``mknod'' or something like that? I do not want to run mkdev hd because I'll loose my data on the second drive (well, I have it on tape but it'll be a pain getting it...). Please respond to me because I need to fix this as soon as possible. Thanks! -- Pablo Sanchez ``Can I touch you to see if you're real...'' Transact Software, Inc - Payolas
barton@holston.UUCP (Barton A. Fisk) (08/22/90)
In article <PABLO.90Aug19191521@mrspoc.Transact.COM>, pablo@mrspoc.Transact.COM (Pablo Sanchez) writes: > Hi, > > I spent this lovely weekend replacing our primary disk on an Everex > 386/25. The problem is that when I try to mount the two partitions on the > second disk I get a mount error: > > mount: cannot access special file > mount: No such device or address > Unless it's changed, it used to be: 1. cd / 2. fixperm -c -dHD1 /etc/inst.perms 3. fdisk -f /dev/rhd10 4. Write down numbers of partitions that contain Xenix 5. exit fdisk 6. divvy -b 1 -c 1 -p 1 -v <partition number> 7. name all divisions you wish to preserve (ie. /u /usr2 etc.) 8. quit divvy 9. i to install table 10. mount should now work 11. mkdev fs /dev/devicename /directory I think this should all be documented in your release notes, so check me on this incase I had a memory lapse. Bart -- uucp: holston!barton