I'm gonna buy a 1.5 TB HDD to put there backups, videos, and stuff like that, and i was wondering what Filesystem should i put there considering that it will be used for backups (mostly) and I must count with that drive in case of something going wrong.
View 9 RepliesWhen I try to boot to OpenSUSE I get the following error during boot-up: unknown filesystem type 'reiserfs' could not mount root filesystem - exiting to /bin/sh$
This only started happening quite recently - before this I could boot to Linux quite happily.
I want to backup a lot of files on an external 2TB USB and sit it in a cupboard for the next 10 years. Looking for the most reliable filesystem for this. I don't care about speed, journalling, UNIX permissions or any of that stuff. All I care about is in 10 years time when the hard disk plates are rusted and unreadable and the drive hardly functions, what filesystem will be the easiest to recover my data from. Not ruling out FAT32 either for its simplicity but maybe there's a better filesystem for the job?
View 12 Replies View Relatedin preparation for the update to Slackware64 13.1 I did a complete backup of my system with dd.
I used the Slackware 13.0 (not 64 bit) DVD to boot and executed the command:
# dd if=/dev/sda of=/dev/sdb
The command finished without any errors as expected. First I tried to boot the destination hard disk to check if the backup was successful and I can start with updating the source disk to 13.1. But at boot time I got the message that the last file system check is 197 day ago, the file system check started automatically and found errors which it could not correct. At this point I thought it was maybe a copy or a hard disk error and tried to boot the source disk. But the behaviour was exactly the same on the source disk. With the source disk I followed then the recommendation, logged in with root password and executed the recommended command which was something like e2fsck -v -h /dev/sda1. Then the system did a file system check and scrolled a lot of numbers over the screen. After a while it reported that it's ready and the system needs a restart.
I switched off and on again. Then the system bootet as usual, and seems to run okay at the moment. But now I'm unsure if really everything is okay.
What I'm confused of is, why the system reported that the last file system check was 197 days ago and why this was just after the dd backup. Shouldn't the automatic file system check at boot time run more often as every 197 days or mounts? I didn't change any default settings (as far as I know). The file system of the root partition is ext4 and my computer normally is switched on and off once every day.
My question now is, if this behaviour can have something to do with the dd backup.
Is my system after the file system check okay again, or should I expect further problems?
Suppose I have a good backup of the / root filesystem. How do I recover the / root area? Suppose I have modified the root filesystem, perhaps I do an update some of the packages and regret it, and I want to get back to the system at the time of the backup. How do most linux people recover the root area of a system from a backup?
1) I wondered if I might put a System Rescue CD in and boot off it?
2) And then NFS mount the directory containing the backup? -In my case, I have made a good backup using rsync, to a directory elsewhere on the network.
3) And then, still booted off the System Rescue CD, mount the partition that contains the / root area in question?
4) Would I then clear or empty or delete the contents from the / root partition?
5) And then copy across all the files from the backup into the / root partition?
I ask these questions because of the (very nice) way linux OS is built entirely from packages... Am I being too complicated? (By comparison, I can see it is easy to recover user data.)If, instead, I simply recovered the backup straight onto the updated root filesystem, I wonder what it would look like if I then tried to verify it with "rpm -Va", for example? Surely, all the packages would fail the verification, because it would think it has a later version of each package from the update, but the actual files would have been overwritten by the earlier version from the backup?
Using tar is it possible to backup different types of file system e.g.ext3, ufs, or any other file system. I know using dump it is not possible because it is reading through raw device. Then what about tar? Where I get more info about this? Means suppose I want to backup files from different file systems using tar then is it possible?
View 1 Replies View RelatedUsing redhat linux el5, when I had booted I had pbm repairing filesystem. So I run following commands
1. fsck -l
2. fsck
But I cannot solve the pbm. My pbm is I had important folder "backup" in root folder just I want to copy it in pendrive how to do it.
With the release of openSUSE 11.3 I decided to upgrade my three-year old computer which is running 11.0 and has been running out of disk for the last few months. I bought a new 500Gb HDD and installed it as the master drive, and moved my old drive to the slave. I installed 11.3 on the new drive. Too easy.Then I tried to mount my old drive so I could move my account files across. I wasn't able to mount the drive, which uses LVM (Logical Volume Manager). Is there any reason this wouldn't be recognised by 11.3?Then I tried to mount my new drive from my old system but 11.0 doesn't have support for the ext4 filesystem. I loaded the ext4dev kernel module with no joy:
Code:
samsara:/ # lsmod | grep ext4
ext4dev 222360 0
[code]....
I installed OpenSUSE 11.1 on a friends computer after having a lot of trouble from ubuntu, and because I use it. It was working great when she got it home, but it locked up randomly and wouldn't unfreeze so she turned it off and when she rebooted She got an error about there not being a file system present and that she needed to run a mount command, which didn't work. After that, now it just says that there is no files system present and you ge tthe basic prompt. I had her run a live cd and run Gpartd and check and repair the partitions, but it did nothing.
View 3 Replies View RelatedI have an encrypted filesystem that I've decided I don't want encrypted anymore. Seems the easiest way to do this is simply reformat the filesystem, but I can't. If I try to do it in YaST2 I get either system error code -3005 (unknown) or -3008 (apparently in use). When I try to do it from the command line I get:
Code:
frylock:/home/joel # umount /dev/sdb5
umount: /dev/sdb5: not mounted
frylock:/home/joel # mkfs -t ext4 /dev/sdb5
mke2fs 1.41.9 (22-Aug-2009)
/dev/sdb5 is apparently in use by the system; will not make a filesystem here!
frylock:/home/joel #
It's unmounted, I don't know how to make it any less in use than that.I can't delete the partition because it's not the last logical partition in the extended partition.
I am creating a raid10 for our studio. I just realized after creating the filesystem that I would like modify one of the parameters - the blocksize. My original command:mkfs.ext4 -b 2048 -L insightRAIDvol /dev/md0I know want:mkfs.ext4 -b 4096 -L insightRAIDvol /dev/md0Is it ok to just issue this command even though a filesystem already is in place?I am hesitant to try this without knowing what the ramifications of this might be for the superblocks or some other unknown parameter to me that might cause problems in the future.As well I know I could rebuild everything from scratch but that's a day and a half of rebuilding
View 3 Replies View RelatedI have a nfs exported filesystem but after each reboot I have to restart the NFS server twice to make it actually export the filesystem.
First restart always fails with:
Code:
Shutting down kernel based NFS server: nfsd statd mountd idmapd done
Starting kernel based NFS server: idmapdexportfs: Warning: /home/teradisk/Share does not support NFS export.
[code]...
I have double boot (windows7 and Opensuse) on my laptop.
My problem is when try to login Opensuse says Read only file system.(While booting a lot of things FAILS(written red) because of Read only file system). So i can't login.
Cause of this problem is want to reach my Opensuse filesystem from windows7.I installed Ext2fsd software to windows7.After installed software can see my opensuse filesystem.But it looks empty from windows7.So uninstalled the software.
After that day try to login my Opensuse.While booting alot of thing fails to load it says "FAILED".and when entered my password after entering my username cant login it says ..... Read Only File System.
How can i make the filesystem Read/write permissions to my opensuse operating system.
I can't use any command beceause can't login. (I will try to boot with Opensuse Dvd)
I am running 11.2, kde4. The day before yesterday, the system updated and I think there was kernal update within that. I had no problems immediately afterward. Then I did a total shutdown for the night, and turned it back on yesterday only to find this:
Mount: wrong fs, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error
In some cases useful info is found in syslog--try dmesg | tail or so
Could not mount root filesystem--exiting to /bin/sh
sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell
$
Besides the last updates from the other day, I did nothing out of the ordinary, no downloads or any system/configuration tweeks. Will I have to reinstall opensuse? or is there a way to reclaim my previous setup--or at least reclaim my files and documents? I'm running off of the 11.2 livecd.
OS openSuse 11.1
After boot its wrote: File system is clearn.
bootsplash: status on console 0 changed to on.
File system seems to have fatal corruptions.
Running with --rebuild-tree is required - failed
blogd: no message logging because /var file system is not accessible
enci-hcd ohci-hcd uhci-hcd usb-jhce fsck failed for least one file system (not /).
Please repair manually and reboot. The root file system is already mounted read-write.
What file I have to correct?
I'm a issue with a opensuse 11.4 guest VM. The root partition goes read-only while the VM was running normally.
I note this /var/log/messages:
Code:
Aug 22 10:57:02 guest1 kernel: [508161.475307] mptscsih: ioc0: attempting task abort! (sc=dc29c5c0)
Aug 22 10:57:02 guest1 kernel: [508161.475380] sd 2:0:0:0: [sda] CDB: Write(10):
Aug 22 10:57:02 guest1 kernel: [508161.475582] mptscsih: ioc0: task abort: SUCCESS
[Code]....
Upgraded from 11.1 to 11.2 using GUI (YaST and Wagon)
Machine stops on boot and says:
fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount, rw /
Attention: Only CONTROL-D will reboot the system in this maintenance mode. shutdown or reboot will not work.
Give root password for login:
I write: mount -n -o remount,rw /
And then reboot with CONTROL-D.
I have an application which uses 256k as blocksize. And I would like to have a filesystem which handles I/O blocksize as near as possible to this blocksize.
I can not use EXT3, because that will be to small blocks. I was getting into problem to use XFS; because that has some dependencies to the PAGESIZE in the kernel, it can not use bigger blocksizes than the PAGESIZE in the kernel.
What more opertunities do I have? Or how can I get XFS to work with bigger blocks.?
Whenever I try to write to /opt, /usr/src, or /usr/local, I get "permission denied."
How do I fix this? The portion of the fstab for the filesystems in question is:
Code:
/dev/sda9 /opt ext4 user,noauto,noacl 0 0
/dev/sda6 /usr/local ext4 user,noauto,noacl 0 0
/dev/sda10 /usr/src ext4 user,noauto,noacl,exec 0 0
/dev/sdf1 /mnt/hd2 ext4 user,noauto,noacl 0 0
[Code]....
While trying to boot into the normal user the system aborts the login and tells me that /home does not have write permission.
The login manager gives:
Code:
If I log in as root and do a
Code:
Or to open some files, it works and no problem seems to exist.
All this happened for the first time after running luckybackup to fusion the old files of one home directory under EXT4 with the new files from my notebook (ext3, Opensuse 11.1 KDE3) in order to come to a unified home. But then the system did not boot any more. I tried to change the owner but some files did not have write access (not even as root, "the file does not exist"). So I thought I might have a a file system problem.
So I thought: unmount the /dev/sdb1 and then do a fschk on it. Runs and was perfect. So I did run it with forcing to control inode per inode.
No error.
So I thought: you screwed up the system. I then decided to reinstall OpensSuse11.3 from the scratch and create the same user for home. I formatted the rest (/swap /boot /root) and left only /home. Installation runs brilliantly, all ok, it comes to the login..................
Code:
I have two ext3 partitions within an encrypted lvm2 volume. when i start up my system it says that there are 0.3% non contiguous blocks.
This is my steup:
When i want to repair with repair system from dvd it tells me that the repair and check operation for encrypted LVM devices is not supported. so how can i fix my filesystem?
Have been running 11.1 on a generic notebook (eRacks) just fine until a few days ago when CUPS couldn't be reached. Rather than futz more with 11.1, I decided to install 11.2 (which has been on my desktop). Using the same CD, which continues to check ok, the install has failed many times at about the same point: 87% through "copying root filesystem" in yast2.
Specs: Intel P4 2.4 GHz, 1.5 GB RAM, ATI radeon PV250Lf
The HD was partitioned into /, swap, /home, and an extended partition of /opt, /var, /usr. Only / was ext4 and the rest were ext3. Tried various options:
* no apic
* no acpi
* "noapic acpi=off" entered manually
* Vesa instead of 1024x768
Each time had to edit partition table to mount the extended partitions. Always formatted /. At first didn't format the extended patitions, later formated all but /home. Then set yast2 to format / as ext3, to match the other partitions. In the sysinfo page the / partition is now shown as /mnt containing 723.6 MB out of 7 GB, still formatted as ext4. On rescan by yast2 partition manager, / shows as ext3. The install halts every time with an error while "copying root filesystem." Tried booting from the CD direct to install and to the Live OS followed by install--same result. So, hours later, went back to 11.1--which installed in minutes.
I am running Suse 11.0 and the system had stopped working. I booted from the disk and chose repair system. Now I can get to the Give root password for login and it accepts the password, but I get the line
(repair filesystem) #
I have win 7 ultimate. I would like to install opensuse but with the option to revert back to my old MBR in case things don't work out. my win 7 dvd gives a version error everytime i try to restore the MBR so i end up having to reinstall windows 7 in it's entirety Is there a tool that allows me to reload my MBR without going into windows? i recently botched an install and got a grub 17 error lol so i could not go into windows. That was funny. Also is there a way to install opensuse without touching my MBR at all. (it's going on a separate drive by itself). I want win 7 as my main, and i'm good with just an entry for opensuse, which i can remove at my pleasure if i'm tried of it
View 6 Replies View RelatedSome people say it is better to do a new install than a upgrade. FOr no specific reason I agree with them (I have not enough expertise to agree or disagree, but lets ignore that.)So I want to install 11.4.What should I back up?
View 9 Replies View RelatedI have opensuse 11.3 installed, and my motherboard has the intel i845 chipset,
one day windows had enough of the intel graphics chip and would not let me have anything but 640x480 pixels, well you cant do much with that so I put an ati card in and disabled the intenal graphics. windows was happy enough but suse could not boot - more specifically could not mount the root filesystem, saying it had errors (did a very quick fsck), could not find the journal, and I had a bad superblock. the "failsafe kernel" was no better. If I take the ati card out suse boots fine. however I do swap frequently between windows and linux and changing graphics cards between boots is somewhat irritating.
when I am pressing the shut down button inside kde I receive this nice black screen with the green status messages indicating what was done successfuly. At the unmounting file systems though I have to wait for a 20-30mins duration to finished. I have two or three network shares but even a timeout would not take more than 1 min to appear.
View 6 Replies View RelatedI want to backup all the data in my /home folder/partition (before upgrading).
1. In How to migrate to a new openSUSE version - openSUSE it is only written how to backup *one* users data.
If you know the path to your external harddisk, just open a konsole and do:
Code:
$ su
1. cd /home
2. cp -b -vvv username_to_be_backed_up /media/<folder_of_your_external_harddisk>
How can I backup *all* users' data in one folder "home-double"?
2. Has the external disk have to have any special file system?
I have an 500 GB disk in fat with some data already on it. Can this be used? Or do I have to make an new (ext3?) partition on my external hard disk to preserve permissions? Do I have to worry about big files under FAT?
3. Should I make anything to get sure that all data is the same in "home-double" as in "/home"?
Now I am using (on my Samsung X20) openSuse 11.1 and Gnome 2.24.1 (mostly, 1 account is using KDE) and Kernel Linux 2.6.27.45-01.1-pae. "/home" is on an separated partition (as part of an extended partition). I have also 2 NTFS partitions for Windows XP (System and Data), and a FAT, a root (/) and a swarp partition.
I'd like to know if there is a way to backup mail folders, as they are. I already tried trough the "file" menu saving function, but it seems to be available for single messages, otherwise it saves more selected messages as unique file. I'd like to manage mails directly on backup support, one by one if I need...
View 9 Replies View RelatedI do regular full and incremental backups using dar. All disk volumes are labeled and mounted by label. There is no other operating system installed. I built a new system but due to having to RMA a disk, I built the openSUSE system on a disk from the backup cycle. This Maxstor disk has problems which is why it was moved into an external box and the backup system. I now have a replacement disk and wish to replace the Maxstor before it dies. I initially tried a disk to disk clone with clonezilla but this died complaining that a small target partition was smaller than the source partition. It had created the partition and the start and end sectors were identical. There are no problems with the new disk.
I decided that it would be a good opportunity to test a full system disk restore from the backups. I have in the past restored individual files and partitions but have never restored onto a bare boot disk. I have restored and labeled all 6 partitions. The partition containing / has been marked as active. /boot is included in the partition containing /. fstab is valid, menu.lst is valid, device.map needs editing but this is not a problem.
What do I need to do to make this disk bootable. I have looked through the GRUB documentation but if you try some standard GRUB commands in 11.3 you get messages saying don't do this use YAST. I have seen other suggestions ranging from trying to start the not supported system repair option to using dd to copy the MBR which seemed to trash the partitions in the users extended partition.
The YAST bootloader displays "boot from the root partition". I assume that this is currently what is happening rather than what YAST thinks might be a good idea for next time. I suspect that all I have to do is dd the first 512 bytes of the root partition. If this is the case I can add this to the backup process. While I automate backups I do not automate restores. Each restore tends to be different and I am not sure of the best way getting grub to work on a bare disk restore.