/dev/sda1 Is Not Active
by vtel57 from LinuxQuestions.org on (#5M0GV)
Well... Current had a kernel upgrade today.
I got it all taken care of, but something weird is going on with my /dev/sda1 partition (Slackware main). I could not get Porteus to mount the /dev/sda1 partition to make an rsync backup before upgrading the kernel. I had to mirror using Clonezilla, instead.
Everything looks fine, but I get a warning when I ran LILO that /dev/sda1 is "not active". What does that mean, pray tell? I ended up having to put LILO on the MBR instead of the 1st partition. I also had to do this a week ago when I installed Slack Current. Weird. Changing the boot flag (w/ fdisk) seems to have no effect, either.
Other than that, all seems to be working fine.
Any suggestions?
I got it all taken care of, but something weird is going on with my /dev/sda1 partition (Slackware main). I could not get Porteus to mount the /dev/sda1 partition to make an rsync backup before upgrading the kernel. I had to mirror using Clonezilla, instead.
Everything looks fine, but I get a warning when I ran LILO that /dev/sda1 is "not active". What does that mean, pray tell? I ended up having to put LILO on the MBR instead of the 1st partition. I also had to do this a week ago when I installed Slack Current. Weird. Changing the boot flag (w/ fdisk) seems to have no effect, either.
Other than that, all seems to be working fine.
Any suggestions?