Tiny Core Linux

Tiny Core Base => TCB Talk => Topic started by: picnic on May 14, 2013, 02:46:18 PM

Title: Can't mount sda1 to backup
Post by: picnic on May 14, 2013, 02:46:18 PM

Hello, new TC and fairly new Linux user here...

I've managed to set up a wireless connection as per the wiki and would like to create a backup so it's automatically restored on next boot. I've edited the necessary file and added the .conf file to the back-up list. The problem is I can't seem to mount the hard drive - it consists of a 38gb partition with Vector Linux and a 2gb swap (in VL these appear as sda1 and sda3).

When I click it's (red) button in the mount tool nothing happens and I can't seem to do it in a console either.

I seem to recall the partition is Resier format, is that the problem or have I missed a step somewhere?

TIA

picnic

Title: Re: Can't mount sda1 to backup
Post by: tinypoodle on May 14, 2013, 02:55:18 PM

Load the filesystems*.tcz extension for reiserfs support.

Title: Re: Can't mount sda1 to backup
Post by: gerald_clark on May 14, 2013, 02:57:36 PM

Your tce ( also the default backup ) directory must be readable at boot, and reiserfs is not supported.

You might try adding reiserfs to the initrd.

Title: Re: Can't mount sda1 to backup
Post by: picnic on May 14, 2013, 03:47:03 PM

Thank you, which of the three filesystems* extensions do I need, just the latest? (3.0.32-x1-rt52.tcz ?)

Actually there isn't much on the hd... maybe reformatting would be a better idea so I don't have to load this extension every time? Is there a recommended format and a tool do do this from within TC?

Cheers

picnic

Title: Re: Can't mount sda1 to backup
Post by: gerald_clark on May 14, 2013, 03:52:33 PM

If this is going to be a TC only hard drive, use the tc-install.
It can format it for you.

Title: Re: Can't mount sda1 to backup
Post by: picnic on May 14, 2013, 04:02:15 PM

Thanks for the quick reply :) Trying out a frugal install....

Title: Re: Can't mount sda1 to backup
Post by: tinypoodle on May 14, 2013, 04:12:13 PM

In general, you always need the kernel modules for your running kernel, to determine with

Code: [Select]

uname -r