I was wondering if it can be possible to boot debian from micro sd card and have it persistent. I have checked the bios of my laptop and there are options to boot from USB and HDD (and from floppy, cd, network and hard disk), but not from sd card. Would it be a problem or could there be workarounds. That is of course if the whole thing is a good idea at all.
I have already booted the laptop from USB, but I would like to use it for everyday work and USB sticking out is bound to get snapped off. Sd card on the other hand would go inside in the slot. The hard disk is dead and is a bit expensive to replace (and unnecessary in respect of the volume, I only need a couple of gb for work)
I have a persistent pendrive of Ubuntu: [URL] It has a file where it saves the configuration of my computer: casper-rw
But if I boot this USB flash drive in another computer I would like to do it in a fresh way, that is, without loading the configuration of my computer (saved in the casper-rw file). For example, in Puppy Linux this can be done easily, just putting pfix=ram in a boot option of syslinux.cfg and selecting this option when booting.
I think this is important because I think that otherwise the Ubuntu (at least in some cases) cannot open if used in a computer different to the one where casper-rw was configured. It happens to me that I cannot run Ubuntu with my pendrive when inserted in a different computer (I think the reason is what I've said).
So i installed debian squeeze in virtualbox with xfce and i thought that it was persistent. when i powered down the virtual machine and started it up again later I only had the option of installing it again. Do i use save state to keep it in the installed stage? would i have to do that each time i made a change? i want to make sure so that i don't keep having to re install it.
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.
I was installing Debian Squeeze into a G5 with an Nvidia Geforce FX 5200 ultra video card. The install went well but the system would not display any output. I did some research looking into the module configuration files in the /etc directory and dmesg log files and discovered that it was incorrectly identifying the video card as a "nouveau" card. I put the name "nouveau" in the modprobe.d blacklist file and it booted fine after that.
I'm trying to create a persistent live Jessie system on my 8GB USB drive.
If that matters, I'm currently on an Arch Linux system, and I partly followed what's on the relative wiki (Pages Create a new MBR for a USB stick, Manually create a USB flash installation and Install Syslinux), plus a CrunchBang post explaining how to make a persistent live USB out of any Jessie-deriving distro (like their BunsenLabs Hydrogen).
The problem is, even if Debian boots up more than fine, the system isn't persistent at all.
Here's what I did (I know some passages are redundant, but still...):
Downloaded the Cinnamon flavor of Jessie via torrentErased the old MBR
Code: Select all# dd if=/dev/zero of=/dev/sdb bs=512 count=1 && syncCreated a 1.1G W95 FAT32 (LBA) active partition and used the remaining space on a Linux partitionFormatted the first to FAT32 and labelled it "Debian64". Formatted the second to ext4 and labelled it "persistence" Code: Select all# mkfs.vfat -n Debian64 /dev/sdb1 # mkfs.ext4 /dev/sdb2 -L persistence Mounted the first partition and the iso
I have created live persistent usb-hdd (fat32) image, put into USB stick, but now I should create persistent live-rw partition. How this persistent partition should be formatted? Should I format with ext2, or fat32?
I've created live squeeze usb-hdd and if I boot first time the udev system writes the MAC address of the network interfaces into /etc/udev/rules.d/70-persistent-net.rules.Because I use full persistence, the file is there on the next boot and I don't get network running automatically on other computers. My problem is, howto remove 70-persistent-net.rules every time during the startup?
I need to have a persistent Debian install on a thumbdrive to run a computer that is currently diskless (dead hard drive). So far I've managed to get it to boot Squeeze live beta by setting up the thumbdrive with UNetBootin, but it's not persistent. I found this, but step 6 is a mystery to me, as I can find no such command or package.
Since removing the deprecated usblp driver from my kernel I no longer have a /dev/lp0 device, or /dev/usb/lp0. I use these for sending files directly to my printer. Should these be created by udev? If so, why might they not be being created? If not, how can I get a persistent device name for my usb printer?
Yes, I know, I know, there are lots of instructions out there on how to create a persistent Linux USB drive. However, I've been having a really hard time finding if it's possible to create the WHOLE thing persistent.For example, I want to turn my 8 GB thumb drive into a portable Debian Squeeze where I can install (persistent) apps and make root-level changes to the filesystem. Is this possible?
I installed debian 8 on a 16 GB usb drive using this guide. I used a debian 8.2 64-bit image with mate. If I were to get a larger usb drive, would I be able to transfer everything from the 16GB drive to it? How?
How to enable persistent logging with systemd? I find it really weird that all this machinery that is systemd doesn't store persistent logs, what if I'm trying to retrieve some information regarding previous boots?
For instance: I have random suspend issues, after rebooting the computer there's no trace left in the logs of what happened, and furthermore (at least in Jessie) I can no longer see a pm-suspend log.
So, at first it sounds like all you have to do is edit journald.conf setting #Storage=auto to "persistent" and create the /var/log/journal directory, but then reading here /usr/share/doc/systemd/README.Debian
Code: Select allEnabling persistent logging in journald =======================================
To enable persistent logging, create /var/log/journal and set up proper permissions:
There are two main reasons why I decided to not enable persistent logging just yet ....
We did get corrupt journal files in the past where the journal then no longer worked at all [1]. With volatile you can just reboot and have a clean state again. Admittedly, the journal has seen a lot of improvements in the mean time and hopefully is more robust, so this point is no longer true.
We still install rsyslog by default. That means we get store them twice. This is something we don't want to do atm.
I have a problem defining persistent device naming on a Debian Lenny server.I have:RAID1 controller on the server machine with two SCSI disks.external storage with RAID5. I have / mount on the first partition on the server SCSI disk and /storage mount on the external storage.
I'm experiencing a problem: The system recognizes the system disk (RAID 1), as sda or sdb - randomly.I want: To control the recognition, and tell the system that sda (sda1) will always be the system disk.The motivation: GRUB is configured to work with sda, and when the system disk doesn't, boot process fails, and I end up in the initramfs shell-like interface.
Booting the kernel . . . mount:mounting /dev on /root/dev failed: No such file or directory mount:mounting /sys on /root/sys failed: No such file or directory
I should create a sqeeze image and install it on other computers.Udev should detect network card (NIC) module and load it automatically at startup.How I understand /lib/udev/rules.d/75-persistent-net-generator.rules runs when udev starts, then writes to /etc/udev/rules.d/70-persistent-net.rules.The problem is, udev searches for this NIC on other hardware and the network cannot start.I can solve this problem easily using a startup script to delete /etc/udev/rules.d/70-persistent-net.rules file.
I've upgraded the generic kernel of my Xubuntu Karmic AMD64 persistent USB installation with the ubuntustudio realtime kernel (2.6.31.9.10). The thing is that the generic kernel is still loading as default and I don't have the option on the boot menu to choose the new one. I don't know how to edit this Grub2 version (grub-pc 1.97 beta 4).I haven't found a GUI package for this either.
I installed few days ago Debian Jessie (Linux server-1 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux) for some tests.I tried to install iptables-persistent with the command "apt-get install iptables-persistent".During the install process, I got the following message :
Some talks about cups, acpid, ipv6 or systemd but nothing has solved the issue in my case.I used iptables-persistent many times with older debian versions.
I want to customise an amnesic Debian environment (like Kali Live CD) with everything (Users, background, icons, etc.) set up to work the way I need. This OS should be inside a memory stick, and, most important, it has to have an encrypted partition I can mount and unmount whenever I want to save persistent data.
I recently changed from Gentoo to Debian Squeeze. All went fine but I have an ALSA issue. I have an AMD Athlon II X4 board with a Nvidia (Realtek) sound chip. After installing I got a lot of "no such device" errors, so I installed the Realtek driver the Debian way and the errors vanished. I could successful run alsactl init and alsamixer.
At this point there is no sound neither in games nor system. alsaplay says (on the screen) that it is playing a wav file but there is no sound. My test ''dd if=/dev/urandom of=/dev/dsp'' complains "/dev/dsp : no such file or directory". Well, all clear. modprobing the snd-*-oss modules brings sound alive but I have to do this after every restart. I have no clue how to make this persistent the Debian way.
I have a 16 GB Sandisk Cruzer Blade USB drive. My aim is to create a portable LMDE operating system. Both for the challenge and to spread the word amongst my friends. Just today, I've converted another mate with an old Dell with stand alone LM9 LTS. On another thread, I recieved a lot of help trying to use GRUB with no real progress other than finding out that needed someone with a lot more knowledge.
viewtopic.php?f=46&t=64335 bear with me for the long description of what I have done so far. I'm trying to avoid us doing things twice. I have used Startup Disk Creator in LM9 to set up my usb. There is still a problem with persistence. Creator uses casper and syslinux to boot. In setup, it gives the option of persistence up to 4 GB file or discard.
The progress window indicates it creates a persistence file. Everything seems to go smoothly to completion and reboot. The boot-up avoids the usual live dvd menu and goes all the way to the live desktop with install Mint shortcut. Change the keyboard to USA Colemak with CapsLock an additional backspace. Reboot the PC, no remove drive and enter request on shutdown, and back to live desktop. No Persistence. Reboot. I go to users and groups and create my own user desktop. Logout of Mint and into my desktop. Change keyboard settings and go to reboot. It wouldn't let me. Needed a root password. Back to the forums to change that. More research tells me that the program creates a seperate ext2 partition labelled casper-rw to generate persistence. Some sites have called it casper.rw Run GParted. dev/sdd- Sandisk 16GB- has a single FAT32 Partition sdd1. No casper-rw ext2 partition. Amongst other things I created the casper-rw and casper.rw partitions to help it along. No effect. I removed the pendrive, and booted up normally. Re-inserted the pendrive to determine the included files.First level-
I have Lenny installed. How to create, using live-helper customized Live USB with a persistent /home partition on this USB stick, to save changes between boots?
I have a problem defining persistent device naming on a Debian Lenny server.I have:RAID1 controller on the server machine with two SCSI disks.external storage with RAID5. I have / mount on the first partition on the server SCSI disk and /storage mount on the external storage. I'm experiencing a problem: The system recognizes the system disk (RAID 1), as sda or sdb randomly.I want: To control the recognition, and tell the system that sda (sda1) will always be the system disk.The motivation: GRUB is configured to work with sda, and when the system disk doesn't, boot process fails, and I end up in the initramfs shell-like interface.
Code:
Booting the kernel . . . mount:mounting /dev on /root/dev failed: No such file or directory mount:mounting /sys on /root/sys failed: No such file or directory
I am a linux newbie and want to try to run Fedora 13 from a 4Gb USB flash drive for a while until I decide to do a permanent install.My problem is that although I selected to create persistent storage using the liveusb creator, nothing is being saved after rebooting.For reference, I downloaded the 64bit version using bittorrent, and I created the live usb on windows 7.Is there some setting I must set to enable persistent storage?
I am currently running Windows 7 and would like to "play around" with Linux and learn how to use it, but am not willing to entirely "jump ship: as of yet. Thus, I would like to be able to use my USB key (32 gig) that is persistent. I have had no success in being able to get this to work; I went to http://www.pendrivelinux.com/ and attempted several different times and the only one I could get to work was not persistent.
My desktop is a Dell XPS 630i. It has a SD card reader on the front panel.
It used to work until about a few months ago (I guess, I don't use it that often). Now, the SD card is undetected when inserted.
If inserted before boot, then the existing partitions are available in thunar. I can remove and insert back the card in the reader without it being detected. I can mount and unmount the partitions. But if I "eject" the partition, then the card is not detected anymore even if pulled out and pushed in again.
Not much in dmesg (the drive is /dev/sde, and there are two partitions in the card, it is a raspian OS) :
When I click "eject" or manually remove the card, it says "capacity change from 2013265920 to 0".
I'm using Jessie, with the latest 3.11 kernel from experimental, but the issue was there with 3.10 and most probably older kernels. I tried to go back in time using older kernels (down to 2.6, I think the reader worked at that time) without succes, which may indicate it does not depend only on the kernel.
I don't have any "power saving" setting in the BIOS I could disable. And I didn't modify the BIOS, even the BIOS settings, in the last months.
I'm pretty sure it is a software issue as it worked with a knoppix 7-something.
Code: Select allecho 1 > /sys/bus/pci/rescan
command I've read about does not seem to work. It is supposed to force the detection but nothing in dmesg and no volume available in thunar.
I found a workaround yesterday. If I launch gparted (needs admin privileges), the SD card is detected. Like if it forced the detection. Sometimes, I have to specify the path explicitely to get it to appear :
Code: Select allgparted /dev/sde
Besides, I'd like to have this bug fixed, but I don't know against which package I could file a bug. Could it be some misconfiguration on my side ?
I just installed the Debian testing release(with LXDE) from this week. Everything works great except the network card. I know the network card works because Windows and the Parted Magic Live cd recognize it. Also "lspci" seems to list the card, but when I fire "ifconfig -a" it is not listed there.
I would like to make all directories except /home non persisent this way any changes are undone by a reboot. (this will be used by kids)Where do I start?I've worked with Linux for years, but never tried this.
I would like to know if I can update a live USB version of 10.04I am, unofficially, running ubuntu 10.04 live USB version from a partition on my 250GB USB HDD at work.All the apps I use are web bassed except for zeacom and groupwise which I run from a virtual machine I created using virtualbox ose, this machine is one the network running AD and novel and also MS office and uniflow printing
Everything at the moment is running quite well: I tried this a while ago (9.04 or earlier) but I tried enabling update manager and this killed the boot for my live USB and I don't what to risk toying with a system that is running well but I also want to be up to date.
