i trying to recreate(after zero-superblock) raid 10 but get stuck with near=1, far=2 layout, how i can setup this layout using mdadm.
View 2 Replies
After several crashes during videos it seemed like a good idea to fsck root. Downloaded the latest systemrescuecd and ran it at boot. The error message was 'bad magic number, corrupt superblock' with a suggested command to try another superblock. That failed with the same message. Tried tune2fs to force fsck at boot and got the same message. The drive is less than 6 months old and the installed system is working more or less ok. The command I used was 'fsck.ext4 /dev/sdc2'. What am I doing wrong?
View 9 Replies View RelatedI have acer aspire one netbook i'm using ubuntu 10.04 on my desktop but i wan't to install ubuntu on the netbook. i made usb installer ubuntu will run from the usb drive but when i try to install it gets stuck on step 3 of 7. wth? tried over and over again
View 2 Replies View RelatedHow do I recreate an LVM raid 1 partition, without destroying data on the discs? I have a 650GB data partition which is a raid 1 array with ext3. Two days ago, the system (Ubuntu 9.04) started to refuse to write to it, claiming no space left on device - even if there is ca. 102GB free left, if the disk is 85% full (according to df)! Interestingly, removing a couple of GB did not help, after reboot the disk was again full..
I did the "tune2fs -m 0" trick and then forced file check on next reboot by "sudo touch /forcefsck" .. and the result is that the raid partition is gone. I have the two physical drives /dev/sd*, unmounted, but the /dev/md1 is no longer there. What can I do to re-create it, without losing the data? I realized that I ran tune2fs on the physical partitions /dev/sd* - was I supposed to run it on /dev/md1?
I have installed opensuse 11.3 a couple of weeks ago in 2 computers and both suffer of the same problem.In my asus laptop, i have a german keyboard. It is correctly recogniced as german keyboard by ev-dev, i guess. (ev-dev managed). But i need to write some spanisch symbols too, like accents (á © í ³ ? ñ¬ ·hich in a normal linux, they do work. For some reason, after rebooting, or after some time of having it running, the keyboard layout resets to an invalid setup, here accents get not over the letter (?a ?e ?i ?o ?u), so i have to select my layout again in the gnome control center.
With my other computermore or less the same.Its a desktop PC with an spanisch keyboard. But i thinck i picked German keyboard during installation and now it starts always with german with some sort of 5 secs delay when setting it. I have to pick spanisch and i always delete the german layout, but after some time having it running, it resets to the previusly deleted german layout.
I rebuilt a server and am now trying to recover my large data arrays. The server was ubuntu 10.04lts before. I decided to rebuild it with CentOS simply because I am more familiar with it. I had 2 raid-5 arrays on the old server:4 x 1tb -> md0 5 x 2tb -> md1 The newly built server does not know about these arrays yet. How can I reassemble the arrays without loosing my data? I know the data can still be accessed because booting the server with a live-cd mounts and shows the arrays just fine. Should I boot with a live cd and copy the mdadm config file?
View 5 Replies View RelatedOne of my raid disks (was a software raid5 with 4 drives) failured. I wanted to buy a new 1.5TB harddisk anyway so i i copied all the Raid data onto the new disk and disconnected the old ones. But then the new Disc crashed right before i could mirror it with another 1.5TB disk. So i need to reassemble my old Raid 5 now. I connected the drives in the former order except the first one, because this was the failed disk. The problem is, mdadm can't find the raid, no superblocks. Fdisk doesnt show mdraid superblocks, too. But fdisk has never showed superblocks. The thing is, this raid was crypted, but i crypted the /dev/md0, so this doesn't affect anything here, or?
some infos:
Code:
server:~# mdadm --misc -d /dev/sda
mdadm: option -d not valid in misc mode
server:~# mdadm --misc -t /dev/sda
[code]....
Disk /dev/sdc doesn't contain a valid partition table But fdisk always said there is no valid partition table and the raid was working.
I bought a disk to a friend that used it in a raid array, using the entire disk for the raid usage. To put that disk on service, i used dd-rescue to copy my old disk entirely, and managed to grow and setup a the partition table without losing any data. My last step was to create a RAID between my entire old disk, with a single partition and a partition of the same size on my new disk. I ran into some problems, but i manage to somehow fix it imperfectly, but now this setup is working properly. The problems (and imperfection) came from an issue it did not suspected : at some point, the original RAID superblock of the new disk, living in /dev/sda, resisted to dd-rescue, and so it is scanned by mdadm that tries, obviously unsuccessfully, to use it.
Partition layout :
Code:
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[code]....
this setup is working properly besides this raid5 declared on sda, so that is shows up here and there. Since it is using the same device name that my other, proper raid setup, i don't know how to deactivate it since mdadm uses the /dev/mdx name to identify arrays.
I recently upgrade to Fedora 14 from 13. It was an in-place upgrade. I can't recall for sure, but I do believe I had these problems in F13 before the upgrade. The F13 install was from a Live CD. Anyway, I have a three drive RAID 5 array setup - 3x 750GB. For some very annoying reason, each time I reboot my F14 system, it hangs with an error about not being able to find a superblock on /dev/md126 and /dev/md127. I have tried to stop and remove /dev/md126 and /dev/md127 but they always seem to come back. I have also noticed in the output of fdisk -l that drives sda and sdd like to swap places sometimes for an unknown (to me) reason. Any other output that is needed, please ask. I recreated the array just yesterday with:
Code:
mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1
I would cat mdadm.conf in /etc, but I removed it previously to try to figure out the problem and it was not
[code]....
I have a x64 OpenSUSE server with two hard drivers installed. The first one is used for the / and /home partitions and the other is for backups. Ironically enough it is the backup hard drive I am having trouble with. I was having trouble writting to the drive and unmounted it to preform a fchsk, however now when ever I try to mount it I get the following error:
[code]...
how I can repair the drive and retrive data?
I decided I needed to expand my openSUSE partition because I was running out of room. There was some unallocated space following my /home and swap partitions that I wanted to assign to my / partition.
So after taking note that bad things could happen (as I've read everywhere), I got myself a copy of GParted (since Yast! partitioner doesn't move partitions, does it?) to start getting the thing to work. Well, actually, I got PartedMagic which has GParted (I realize it could be a problem NOW if they didn't have the latest version).
So the first step was to move the swap partition. I decided to do it one step at a time and only moved the swap partition to the end. That turned out fine...no problems whatsoever.
The next step is where the problem came in. It was moving the /home partition. It took a while to move but once it got to the end, it showed a message that was similar in nature to "error detected" without giving a long list of error messages. If it did, I probably would have copied it down. There wasn't anything in the "logs" either in GParted besides what it showed. Looking back, I probably should've went into /vars/logs to get additional log information but I guess I wasn't smart enough to do so (provided that GParted does leave log messages there which I think it does).
After that, it refreshed the drive and it ended up showing no partitions with an error and saying the only thing it can do is create a new partition table. After that, openSUSE wouldn't boot. After loading, (both normal and failsafe modes) it gives me the message in the link at the bottom. I can still access those partitions fine. Nothing's corrupted. Windows also boots up fine (it's on a different drive though) and reads the affected drive fine. Linux-based LiveCDs (including openSUSE 11.3) reads the partitions fine too.
I've tried using e2fsck on my ext4 partitions with commands I found during a search and they seemed to "fix" those partitions but it still won't boot and gives me the same message. Looking at it carefully, it seems the reason it can't find a superblock is because it can't find part8 of whatever that thing under /dev/disk/by-id/ is.
I would very much prefer a failsafe (or at least mostly failsafe) solution that won't (or is unlikely) to result in requiring the restoration of a backup but I do understand that there is always the chance of something going wrong that will kill everything. Considering that I can still access the data on that drive, I don't believe the data is corrupted. Maybe the drive itself (as in whatever signatures it may leave) but not the filesystems.
This is what I end up with trying to boot into openSUSE (sorry, I don't know how to get the log when it doesn't put it in logs directory: https://docs.google.com/leaf?id=0B3A...ut=list&num=50
what is the correct way/procedure to re-create a user home directory. For instance, on a Mac/Windows machine, i would just rename the existing user profile [home dir], and then just log back in as the user - job done. On OpenSuse/Linux, it seems it does not work that way..?! When i try to rename my home folder to say me.old via root, and log back in as me, i get all kinds of errors. Opensuse does create a new home dir, but it appears not properly.
View 9 Replies View RelatedI have a x64 OpenSUSE server with two hard drivers installed. The first one is used for the / and /home partitions and the other is for backups. Ironically enough it is the backup hard drive I am having trouble with. I was having trouble writting to the drive and unmounted it to preform a fchsk, however now when ever I try to mount it I get the following error:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Does anyone know who I can repair the drive and retrive data?
I have a UK keyboard, so I selected the United Kingdom layout on installation of OpenSUSE 11.3.However, something keeps automatically adding the USA layout, and switching to it ! How can I prevent this annoying and intrusive behaviour ? Deleting the USA layout is not enough, it seems. It just restores it again.
View 2 Replies View RelatedI updated from 11.1 to 11.2. Before some intelligent person says, I should never update but do a new install: a new install isn't better, then I have other problems to tackle. And I really would like updates to work.Well, I have the following problems and I hope you don't mind me listing them all in one post *it's difficult for me to type on this keyboard layout):1. home isn't found or set up. I have modified fstab to mount /dev/sda6, which is home, but it won't mount it at startup, and also not when it's just using the disk/by-id line that had been put in.
2. the keyboard layout is american, while the system language is set to German (I'm German and would like also my keyboard to know that). I had no chance to change that, even a loadkeys de-latin1 doesn't help3. OpenOffice drives me crazy. It just doesn't start properly, or at all. It doesn't open a number of documents, but it doesn't also give any error message. Sometimes soffice.bin is in the list of processes, but OOo is nowhere seen. After killing the process (or terminating it), I can start it, but have only the opening screen and cannot really open a document.4. printing doesn't seem to work, either.Needless to say that everything worked fine before the update
I have a keyboard layout built in Korean language, and when i installed openSUSE 11.3 by network installation i keep keyboard layout to Korean. But after installation can't write Korean but still see Korean font in Firefox, cuz i added its font on firefox configuration settings. What shall i do? I want installed in English but still need to use Korean fonts to write something.
View 2 Replies View RelatedOpenSUSE 11.2 server, Gigabyte GA-MA790X-UD4P sda for system, 3 ext4 partitions, working fine.sdb promise RAID1 for data, 1 ext4 partition, working fine.sdc is an eSATA docking station for data backup, 1 encrypted ext4 partition -- here lies the problem.
This configuration has been functional for months until I decided to add two more external drives (sdc) to rotate through backups. I had difficulty with encyption on the first new drive and eventually decided to start over. Using the gui Yast Expert Partitioner, I deleted the single partition. That began a real nightmare...
Since deleting the partition, the system detects drives inserted in the docking station, but does not report them (including a different fully functional drive and a brand new unused drive). I have tested all drives on other computers and they function perfectly. I have rebooted the system several times while troubleshooting this issue.
Could not recreate the partition on server (since it does not recognize the drive), so I used Gparted on another computer - it all went without a hitch, formatted ext4. But when I placed the drive in the dock, the drive still was detected but not recognized.
Details:
BIOS lists the eSATA drive
Entering Yast Expert Partitioner, error message follows:
The partitioning on disk /dev/sdc is not readable by the partitioning tool parted, which is used to change the partition table.
You can use the partitions on disk /dev/sdc as they are. You can format them and assign mount points to them, but you cannot add, edit, resize, or remove partitions from that disk with this tool.
Yast partitioner shows drives: sda, sda1, sda2, sda3, sdb, sdb1 sbc is not listed.
# fdisk sdc results in: Unable to open sdc
# dmesg | grep tail reports:
[48442.370779] sd 0:0:0:0: [sdc] Unhandled error code
[48442.370793] sd 0:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
code....
So how did partition deletion cause this issue, and how do I correct the problem? It is possible that my difficulties encrypting the first new drive are related (it's not my first time doing it successfully). It seems the problem is in the Kernel or configuration. I have invested many hours in forums and on google - tried dozens of possible fixes. I'm beginning to suspect system corruption or a bug, however all other system functions are working perfectly.
I can't get my usual gui now. I had videocard problems which I was attempting to solve by uninstalling the proprietary ATI driver. While doing this the card failed completely and I had nothing on the screen at all. So I had to shut it down by killing the power. I now have a new video card in the machine but I've lost KDE. I'm not sure how it happened but when I tried to log in I was presented with the login screen one usually gets when you choose to log out of your account after a normal boot up using, in my case, KDE.
Logging in normally in that screen as my usual user didn't work. It simply went back to the login screen after a few seconds. But this screen also gives you various options to log in that aren't KDE and I chose one of those. I don't remember which. It sort of worked. I get a small cli window in the upper left corner of the screen. However, I can start programs from there, including Firefox, which I'm using to post this. I have the gui within those programs. How do I get my usual KDE gui back? I'm using 11.3 and an ati 4350 card.
I was able to login until i did change some appearence settings.Now I cannot do anything.. I cannot find anyway except uninstalling it
View 9 Replies View RelatedI logged out of KDE and started a new session in IceWM just to check it out. When I logged out of IceWM my system crashed and I had to restart. Now it logs in automatically to IceWM. If I log out of IceWM it crashes and I have to hard restart it. When I log out of IceWM it just shows a messed up nvidia logo.
View 1 Replies View RelatedI have had to reinstall SuSE 11.2. After its successful completion it got into a strange situation: the boot loader identified a boot record on the hard drive and displayed the appropriate message on the screen - but then nothing happened. When I restarted the system with the live CD and chose "boot from hard drive" it got to the normal boot menu without difficulty. I have no idea why the second method succeeds while the first fails
View 3 Replies View RelatedI was able to login openSuSe/KDE. Now, every time I enter my username and password the system hangs half-way through the Boot Logo.
View 4 Replies View Related11.4 Boot Freeze That is there is a BUG: soft lockup - CPU#0 stuck message and the boot hangs.The modprobe/migration codes are not identical with the linked thread. I'm stuck with CPU#0 at [modprobe:138] and #1 stuck at [migration1:8]. Generally after 61 or 63s.
This is a zypper dup from latest 11.3.The machine boots with acpi=off, luckily. But I'd like to have it all working.The forum says I can't post attachments; hwinfo output seems a bit copious to quote inline. But I'd be happy to provide any additional info obviously.
i'm new to linux, i installed fedora 12 first. These are my partitions
Device Boot Start End Blocks Id System
/dev/sda1 1 192 1536000 27 Unknown
Partition 1 does not end on cylinder boundary.
[code]...
In the process of installing 11.2 over 10.2 everything goes fine until I reach a login screen. There I provide my previously supplied username and password and the result is logon failed. I have tried the install several times. The result is always the same.Login also does not work from console. Some surfing has provided the suggestion that the old Grub may still exist on the machine. If so, how do I get rid of it?
View 8 Replies View RelatedI cant seem to get Opensuse 11.4 to install I am stuck using a USB drive but using the imagewriter program that Suse provides to do a usb installation. Everytime I try to install i get LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE and some I/O error also if i DO the Check Disk thing its always perfect. Not sure it thats because im using usb.. idk.
View 9 Replies View Relatedi ve run into problems while installing 11.3 x64. Installer stops at search for linux partitions... to solve it i ve had to go back to 11.2. Anyway, i have installed 11.3 on another hdd (3hdds in raid 5 had to be disconnected). When i go into partitoner (11.3) and device graph, i see two of three raid hdds ok with sda1, sda2.... but the third one is without any partitions./ if i do the same in 11.2 all three hdds are with all partitions in that graph. Anyone know the solution except not installing 11.3? .)
View 2 Replies View RelatedNew install on Compaq Presario F700 (F756NR)The install went fine. I was able to get the Nvidia drivers working too. The problem I have is when the system boots. I get the OpenSuse splash screen, and the system just hangs.I found that if I press <Esc> and hit <Enter> a few times, the system will eventually boot. I also found if I wiggle the mouse during the splash screen, the progress bar will begin to move, and the system will boot.Seems to be something about detecting hardware during the boot phase, and it seems to be input related.
My Computer
Folders, Harddisks, Removable Devices, System Information and more...
Disk Information
[code]....
I've tried to install opensuse in a dual boot with xp. I've got an extended partition with root home and swap and primary partitions for xp and boot. The installation freezes at 92% while installing the bootloader, I've tried installing from cd and from usb, with or without boot partition and nothing changed.
View 3 Replies View RelatedI downloaded x86-64 hybrid DVD and done everything according to instructions from Installation without CD - openSUSE.After booting from USB HDD, the first page took about 3 minutes to switch menu to the installation media option then afterwards the installation got stuck on Hard drive detection (probably 2 hours before i rebooted into windows 7). Installation scenario is:
Machine: Compaq presario C767TU
HDD: 320 GB with Windows 7 Ultimate on root partition, all other partitions NTFS
Free Space for Linux: 30 GB (Extended partition) currently having Mandriva 2010 with /swap 2GB, / 10GB,
[code]...
