2007-08-29_20:50:49-0400 Ron Peterson <debian-user@lists.debian.org>:
> I was cloning a software raid system to a hardware raid system (Dell > 2650 to 2850). I took out the mdadm startup scripts, but apparently > software suspend was somehow trying to restore some kind of state > information about the system that was no longer valid. BTW, this is the where the boot process stops: Begin: running /scripts/local-premount kinit: name_to_dev_t(/dev/md8) = md8(9,8) kinit: trying to resume from /dev/md8 Attempting manual resume I/O error reading swsusp image Of course there is no swsusp image on my swap partition, because this is a newly cloned system. The new machine also has more memory, so I booted, with 'noresume', and installed a bigmem kernel, but that really crapped out. I went home after that, so I don't have much more detail, but from what I'm reading, it sounds possible that my filesystems were corrupted by what I was doing. This is starting to remind me of how tightly coupled Windows is to the hardware it's installed on. Yuck. -- Ron Peterson Network & Systems Manager Mount Holyoke College http://www.mtholyoke.edu/~rpeterso -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
