Hi all,
I am running 4.3 on an ALIX board, with filesystems laid out as
Filesystem SizeUsed Avail Capacity Mounted on
/dev/wd0a 120M 49.1M 64.5M43%/
/dev/sd0a 3.9G3.1G623M84%/usr
/dev/sd0d 1005M 28.0K955M 0%/tmp
/dev/sd0e
On Sun, Jun 22, 2008 at 08:57:00AM +0200, Jan Stary wrote:
...and then the obligatory newfs on /dev/sd1X, cd into it, and restore.
Everything went fine.
Then I rebooted with only the new disk plugged in, which gets
recognized fine as sd0 (now), the system boots ok, and I get
log in.
BUT
On 2008-06-22, Josh Grosse [EMAIL PROTECTED] wrote:
Perhaps you neglected to write MBR bootcode? (fdisk -u)
this isn't needed here...
On Sun, Jun 22, 2008 at 08:57:00AM +0200, Jan Stary wrote:
Please note that the system does not boot from
the new disk.
compare files on the two USB disks
Hm ...
compare files on the two USB disks and check they copied correctly.
if they were mangled, you can fix system files by untarring from fresh
sets, but you also need to look at /home etc and check your own files
are ok.
I did the same thing again, exactly. Really.
Now everything works.
On Jun 22 06:22:35, Josh Grosse wrote:
On Sun, Jun 22, 2008 at 08:57:00AM +0200, Jan Stary wrote:
...and then the obligatory newfs on /dev/sd1X, cd into it, and restore.
Everything went fine.
Then I rebooted with only the new disk plugged in, which gets
recognized fine as sd0 (now),
5 matches
Mail list logo
