I have two partitions in LVM. They are added in /etc/fstab to mount automatically. But, they are not working. The process to mount partitions seems to be happening before the service /etc/init.d/lvm2 is started. I can get it mounted using "mount -a" command, but not during the boot time. What should I do get it automatically mounted on every boot?
Does anybody know how to have partitions (not removable media) auto-mounted at boot?It would be great so I do not have to click them for first use.By the way, may it be pre-configured in ubuntu to do that for everyone?
as far as i know Debian "Squeeze" has a disk check utility, but you can't run this on a mounted filesystem. Is there a way to trigger this during boot (before filesystem is mounted) ? I can run this once a month to keep filesystem healthy....
I am trying to encrypt partitions on a usb stick using squeeze. I will be installing Arch on that stick, but as I am using Debian as the OS to do the encrypting I thought here was the best place to ask. I've not had any dealings with encryption before so i'm a little lost. It's not working as I would expect basically - here is the error mssge :
spoovy@peony ~ $ sudo cryptsetup -c aes-xts-plain -y -s 512 luksFormat /dev/sdb5 WARNING! This will overwrite data on /dev/sdb5 irrevocably. Are you sure? (Type uppercase yes): YES Enter LUKS passphrase: Verify passphrase: device-mapper: reload ioctl failed: Invalid argument Failed to setup dm-crypt key mapping for device /dev/sdb5.
I have two disks, sda and sdb. Each has a partition that is part of a mdraid array for /. Each one also has a swap partition, and both are used by linux. I've heard that hibernation won't work with two swap partitions. Is there any workaround, other than only using one swap partition?
Actually, the /root- filesystem still gets mounted, for all the others I get the following message:
When I type
But this only happens when using my custom kernel (22.214.171.124). When I use the kernel which was automatically installed (2.6.32-5-amd64), the problem doesn't occur.
Is there a kernel option I should have turned on?
I checked the UUID-numbers from the error messages with the output of "blkid" - they match. The rootfs is on sda2 (which gets mounted without error) - so I tried applying the fstab mount options of sda2 to the other partitions - same problem still. what makes the root partition so special? Is it because it's defined by grub.cfg?
After a fresh install of 7.7.0 (amd64), I'm unable to boot into Debian. I get the following error constantly when booting in recovery mode:
(snip) [drm] nouveau (snip) PMC - unhandled INTR 0x44000000
A bit of Googling seems to indicate that this is due to my video card (Geforce GTX 750Ti). Unfortunately, my motherboard doesn't have any monitor ports, so I'm forced to use a video card in order to use a monitor. Something I didn't foresee being an issue, but what can you do. How should I resolve this? Is there an ISO that has the (presumably non-free) drivers included? A way I can add the drivers during boot (I am able to boot into my Windows partition by changing the boot order, don't know if I can do anything useful from here)? Or do I have to do something crazy like buy/borrow an older video card just so I can properly boot into Debian, and then install the drivers?
I've got a secondary problem: GRUB has my Debian install as the only option, even though I had Windows 8.1 installed first. I don't know if this is related to the problem above, or it's a known problem with newer versions of Debian and/or Windows (and I have to update the menu.lst or whatever myself), or if it's due to the way I set up partitions. My current setup is:
SSD: - Windows boot partition - Windows main partition - Debian / partition - Debian swap partition HDD: - Debian EFI partition - Debian /home partition - Unallocated space (will eventually be a NTFS partition for shared storage)
This is the first time I'm using a motherboard with EFI/UEFI. It's also the first time I have an OS taking up partitions on multiple physical devices. I don't know if either is the cause of GRUB not detecting Windows.
Whenever I reboot, I get GRUB and the _ pinking, and that's it. With rescue cd I can have chroot shell, to troubleshoot I did the upgrade-from-grub-legacy and installed it to both /dev/sda and /dev/sdb In recovery I redid the upgrade-grub and grub-install commands but still have the same "GRUB and _ blinking".
Because the text "GRUB" and then nothing I didn't enouncter while googling, I need to ask here for further troubleshooting.
I tried installing a live version of Debian Squeeze 6.0.0 for the i386 architecture. I am using a first generation MacBook Pro (Intel Core Duo, not Core 2 Duo).
I managed to boot the live cd and install everything using the "guided installation" option, using the whole drive for Debian (I don't have the Mac OS X Snow Leopard disc so I just wanted to install a strictly Debian system). I installed GRUB to the master boot-record, but after finishing the installation and rebooting I was confronted with the dreaded "question mark". After doing a bit of reading, I found that I should have installed the EFI LILO bootloader to the MBR instead of GRUB, so I reinstalled everything, choosing this option instead. But that didn't work either. More question marks. I imagine I must have to configure either of these bootloaders in the shell, but I don't know how to go about doing this.
How to do this without using a Mac OS X installation disc.
i'm used eeepc here the situation i've already install squeeze AMD64 KDE but i want to try using i386 gnome which is more friendly for my eeepc spec. problem is there other boot in my pc. i'm currently using win7, ubuntu 10.10 32 gnome, and ubuntu ultimate 64 gnome and i don't have external HDD.
Question is i want to remove all linux OS and keep my win7 is it ok if i'm using Gparted to delete all linux OS and then installing deb squeeze i386. my next project is to build portable server on eeepc.
'rolling' release as redoing install /upgrade every 6 months is getting 'old' My machine is triple boot
Hard drive is 320 GB Windows 7 - 167 GB Ubuntu - Maverick - 73 GB Ubuntu - Natty - testing version - 65 GB
I do not want to screw up my 'grub' as it's been trashed a couple of times recently and had to re-install everything, which went great with install setting up partitions. I am not sure where 'grub' is installed to. I did install Windows 7 first then let installer split hard drive in half to put Ubuntu on then while installing my second Ubuntu, I let installer split the Ubuntu partition in half, hence the 167 GB Windows and the 2 smaller partitions for Ubuntu.I was thinking to maybe let Debian install over my Maverick install. Would that work and not mess up my Grub and cause me to not be able to boot and have to fix the drama?
I have just installed Squeeze on my laptap with a radeon mobility equipped laptop. When it boots, I see the following message:r600_cp: Failed to load firmware "radeon/RV635_pfp.bin".and some others, too, but it stalls at that point, and I cannot use CTRL-ALT-F2 to get a text-based prompt - in fact, I can only seem to get it back with a ALT-SYSRQ (R-E-I-S-V-B) sequence to force a reboot. It is a multi-boot system, with a windows partition, Ubuntu partition, and the new Debian partition. The Ubuntu and Windows partitions will still boot, only the Debian stalls.
When I boot into Ubuntu, I can see the Debian partition, and can see (for instance) the /var/boot/dmesg file, but it only says:"(Nothing has been logged yet.)"So, being new to debian itself (even though, I know, that Ubuntu has a debian base), how can I make it boot without X, which is I presume, the center of the difficulty? Can I change some file on the debian partition using Ubuntu to get the debian partition to boot in text only mode, and then try to fix the radeon driver?
Alternatively, can I put the proper files for the radeon driver *from* the Ubuntu partition *to* the debian partition and expect it to load and boot correctly? I did, at one point, download and install the proprietary ATI driver files on Ubuntu, so can I put them in a proper place on the debian install?
I have Windows 10 and Deb 8 dual boot, and I need to re-install Windows but want to avoid (or at least plan for) losing Grub/Linux boot.
Last time I re-installed Windows after Linux I ended up having to re-install Linux again afterwards as well, because I couldn't recover it (seemingly due to complications from encryption). So this time I'm wanting to plan and avoid that.
CURRENT DISK PARTITIONS:
Code: Select allsda1 | 550M | EFI System sda2 | 128M | Microsoft reserved sda3 | 175.8G | Microsoft basic data sda4 | 286M | Linux filesystem (Boot) sda5 | 28.2G | Linux filesystem (Root) sda6 | 91.3G | Linux filesystem (Home) sda7 | 1.9G | Linux swap
As there is a "Microsoft Reserved" partition and a separate Microsoft directory within the EFI partition, if I just go ahead and reinstall Windows will it install it's boot loader/image to one of it's own partitions? And NOT affect anything else like Grub and other Linux things?
Logic tells me yes, but there seems to be many issues on the internet about installing Windows after Linux.
My primary concern is whatever happens with Windows or anything to do with dual loading etc, is that Linux will still just boot, or I can get it working again without much hassle.
Why is there a reserved Microsoft partition AND a Microsoft directory in the EFI partition? Which one boots Windows?
Why is there a separate Linux Boot partition AND a Linux directory in the EFI partition? Which one boots Linux? Where is Grub invoked from, is one redundant, etc?
How these work. It is possible I've set them up wrong, or with redundant partitions, but both systems have been booting ok for months.
I've had Windows XP Home installed on my netbook (Toshiba NB205) and I've just tried to install squeeze via net install. In particular, I installed grub. Everything seemed to go ok during the installation, but when I boot up, all that appears is a blank screen with nothing but at "j" and a cursor. One thing I can think of that might offer a clue, is that when asked to installed grub, the installer said it recognized two operating systems: Microsoft Windows XP Home, and Windows NT/XP. The latter is not really an operating system, but the backup partition.
I don't know how this might affect grub's functioning. What does this "j" mean? Looking at this: [URL]. Could this have some thing to do with boot flag? Should I switch it to my NTFS partition instead of my root partition? Doing that at least let's me boot into Windows. But that's not what I want. I've never dual booted before. So I booted back up with my USB, intending to reinstall Debian, and it loaded grub instead. So apparently grub is now on my USB. Then it booted me into Debian.
I cannot count how many times I have re-installed squeeze, and do all kinds of fixes to grub, but no joy. Every time, there is this ntoskrnl.exe error, and to re-install it. I thought my WIN XP may be corrupted, so I reinstalled it, and updated it with sp3 and all updates. Then I re-installed squeeze (reformatting all partitions). At the end, the installer ask if I want to install grub to mbr. I replied yes. After reboot, only the 126.96.36.199-amd64 and the recovery kernels show up on the grub screen, no winxp.OK, I booted into squeeze kernel and looked at the /boot/grub/grub.cfg file, and there winxp is not included in /etc/grub.d/30_os-prober section. In terminal, I typed
#os-propber and it found winxp in /dev/sda1 then I typed #update-grub
and now /etc/grub.d/30_os-prober now show winxp.I rebooted, and winxp shows on the grub screen, and I chose winxp.It came back with "ntoskrnl.exe ...error... re-install ntoskrnl..."Here are the details:
I have installed vmlinuz and initrd.gz (squeeze) in /boot/newinstallation and added to Grub the lines:titleNova Instalaçãoroot(hd0,0)kernel/boot/newinstall/vmlinuzinitrd/newinstall/initrd.gzNevertheless, when I choose this option at the grub, it begins to start the kernel vmlinuz and thus restart the system. The installed Debian Lenny boots in a normal way.
Some thing quite bad happened to me , i installed debian jessie about 2 month ago. Today I wanted to try what a gnu/linux is like so I installed dragora 2.2 on one of my free partitions , (sda 1 is my debian root , sda2 is my debian home, I had sda4 which nothing was on it so i installed dragora on it. But something bad happened , during boot time you get this page which asks you what distro you want to enter in past I had just one choice and it was debian jessie, I expected after installing dragora I will see 2 distros on this page, but i get just 1 , and that's dragora ... but maybe i should mention this that when entering dragora i can access all my previous files , debian systemfile , debian home , they are still there but i can't enter debian jessie ...
I'll start at the beginning. The problem i am about to describe occured in ubuntu 9.10 for the first time (https://bugs.launchpad.net/ubuntu/+bug/480850) and is ironically partly responsible for my switching to debian. which i don't regret, but it seems i can't run from the bug any longer because now it's in squeeze, so i want to fix it or make a proper bug report:
Steps to Reproduce: 1: Suspend Laptop to RAM 2: Resume from Suspend 3: Wait and see, preferably monitoring top: At some random time, ranging from immediately (black screen after resume) to several hours later, the system will become unresponsive. Switching to tty1 or Alt+Print+K does not work, Alt+Print+REISUB does work. Each freeze is anticipated by a random process (this time it was mandb, was installing something) hogging 100% of CPU, then the System becomes gradually unresponsive within a minute or so (panel, metacity, finally mouse cursor freezes too). Alternatively, in case of a black screen immediately upon resume, Alt+Print+K works (EDIT: or not), and the system remains usable. Additionally, i don't know if this is related, i noticed one process using 9999% of CPU for a second according to top, just thought i'd mention it. This bug constitutes a regression, suspend does work flawlessly on this Laptop in Lenny.
The above is how it presented itself at the beginning on a fresh squeeze install, however, after two days of trying, i additionally get kerneloops messages i did not get before (again, after at least one suspend to ram) and after that the system becomes generally unstable (random applications won't properly open or terminate, including nautilus, evolution, iceweasel). Can this be due to secondary damage from the freezes and alt+print+reisubbing repeatedly?
The good news is, apart from this probably already damaged squeeze install, i have another one on one of my playground partitons, where i avoided suspend so far, so i can still try things out there. (it's kde, but i don't think it's related to the desktop environment).
My swap is not mounted at boot. get it to mount again? I CAN make it mount after booting but I need to hibernate. I read that I have to edit /etc/fstab but I'm not quite sure as to what I have to do specifically.
I'm just wondering because I'm going to to test out just how many partitions I can make and mount on GPT. Is there a theoretical limit on the amount of partitions or mounts allowed? I was thinking there would be depending on if you were running i386 or x86_64 because both can only handle up to a certain interger.
Created partitions, some of them LVM, in a server, say A. Did the same for another server, B, but created one more LVM partition.
Installed RHEL in A, and some other applications. Made dump files for each partition of A and restored all of them them in B. No error in that process, except B wouldn't boot. Did chroot /mnt/sysimage and grub-install /dev/sda--still no good. B came to a halt with GRUB> dispalyed. <tried many things many times.. searching Googles..but w/o luck) Gave up, and restored the bootloader part using OS CD -- I say restored because now B boots ok and I can see application that I had installed in A. So far so good.
Problem: that extra LVM partition is missing! I did not knowingly overwrite it, so where did it go? Somebody is keeping it from being displayed!
Is it the grub.conf that tells the OS what to mount and what not to? If yes, problem is , grub.conf is missing in B. In A, it is in /boot/grub/. df -kh shows other partions (some of them LVM) just fine.. what is going on?
I tracked a file called menu.lst in a strange place, in /usr/share/doc/grub-0.97.. but I didn't see any entry that loads partitions.
i reinstalled opensuse yesterday.when i turn on my system every time i need to enter my root password to mount my partitons.please see the following image.i want to automount all partitions on startup without giving root password(before reinstalling opensuse it didn't ask root password to mount my partitions)
My Laptop has Ubuntu 9.04 and I am using it for the past one year. I have four partitions. Gparted Screen Shot attached. /dev/sda5 was mounted as "Laptop 2" /dev/sda6 was mounted as "Laptop 3"
But from today morning I was not able to access any of the files from my hard disk. When I press the "Computer" Menu Item from the "Places" menu I could access all the files on my hard disk. It shows an error message attached with this thread. The system boots perfectly and work perfectly. "Laptop 2" and "Laptop 3" disappeared.
I searched the net and found ways to mount the Partitions with these following commands. sudo nano /etc/fstab # /etc/fstab: static file system information. # Use 'vol_id --uuid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5) .....
Is there any way I could use "Laptop 2" and "Laptop 3" as my mount points as it was earlier.