On Jan 10 00:21:12, p...@jbechtel.de wrote: > Ten years ago I installed OpenBSD 5.[?] which included setting up a > small partition of 2 GB, including the full OS with kernel, programs, > web-related data, etc..
Why did you install everything in one small partition? > What also may be noted is that the ufs magic 0x00011954 (or, > 1954 0001, in hexdump switched 2-bytes) was present at position 0x255c > and 0x455c and several times at larger offsets. Could these be copies of the superblock? > (very helpful, this > post: https://bugzilla.kernel.org/show_bug.cgi?id=197733; looked > similar to mine few days ago) That says "unable to mount UFS", while yours was a perfectly fine system, AFAIU. > This weekend I installed OpenBSD 7.4. Where? Into that same small partition? On another disk in that same machine? On other partitions on that same disk? > Finally I reconstructed the partition table What partition table? You had one partition. > (fresh MBR pointing to the still intact disklabel) > assigned a mount point to the old partition, "/oldbsd5", which worked > on first boot. I just saw the usual files usr, mnt, ... when invoking > "ls /oldbsd5", assumed it was working then. To be clear: you installed 7.4 somewhere else and just mounted the old small partition from the new 7.4 install, seeing the old data. > Automatic fstab entry was > [hash].j /oldbsd5 ffs rw,nodev,nosuid 1 2 What do you mean by "automatic"? Surely the installer didn't create an "/oldbsd5" mountpoint. > Then I deleted "rw," Why? > from fstab and maybe rebooted the system once or > twice. I'm pretty sure that I never made rm -rf on that directory. "Pretty sure," he said. You cannot rm a mounted point, so if it was indeed mounted, "rm -rf /oldbsd5" wouldn't work. (But "rm -rf /oldbsd5/*" would.) > Then > I found out (with df -h) that the partition is empty. Show the df -h output. > Really actually > empty, so theres no hidden file, no file, no lost+found, just nothing. Show the fstab and the disklabel and output of mount -v > The data, however, is still scattered on disk. I can see the lines of > known text files with grep. Grepping what, the /dev/sdXj ? > I also can see the signature at 0x455c, but > not any more at 0x255c. fsck doesn't find anything problematic. So what does fsck /oldbsd5 actually say? Is the partition actually mounted? Jan
