I knew how to mount it and I was able to view files and folder in it but I don't know how to copy files using CUI (Command not GUI) mode. I have six separate iso files and I want to make a DVD in the removable device.
I have an External HDD which has a Data directory in it and I want to move to this directory to use the script mkdvdiso.sh to combine six separate iso file (of CentOS, of course). The syntax of this script is:./mkdvdiso. sh /source /destination/DVD.iso.I don't know what to replace source and destination parameters with.
I'm trying to get fstab to auto-mount a removable device when its plugged in? Is this possible and if not what is the easiest way to auto-mount a removable device?
I have an external hard disk drive and I would like it to be recognized with the same name (e.g. /dev/sbd) after each boot. Is there any way to make that?
I have a samsung removable hard drive, which have 3 fat32 partitions on it. When I plug into the usb. nothing happened and i just see a sdc was added in /dev/...so, there's nothing wrong with the drive, because i can use it on windows and ubuntu.
When CentOS boots up, it tries to determine the IP for a network device (eth0) and fails. 'Determining IP information for eth0... failed; no link present.' I'm curious to know how, after booting up, I could set the IP information for a wireless device, wlan0, manually. Another way of putting this questions is: if CentOS is able to determine IP information for a network device on bootup, what settings is it configuring exactly?
I have installed live cd on usb pendrive. Everything works great. How can I find out which device driver it is using? Where are the device driver files stored? How do you specify the device driver when mounting a device?
I have a 500GB external drive I want to use on a couple of Linux systems, and looking for a filesystem for it. External drives are frequently formatted in FAT32, but I don't need to interoperate with Windows and would rather avoid the ugly limited kludge that is FAT.
Since I only need to use it on Linux, I would use ext4 or XFS, but they store ownership information. Ideally, I'd use a proper Unix file system that doesn't track ownership (files are owned by whoever mounts the device, like they are when mounting a FAT32 partition), but I do not know of any file system that does that.What would be a good file system for this disk?
I have 2 USB drives connected to an XP machine that I rotate twice a month for backups. On my CentOS box, I have that drive mounted at /home/backup using cifs.
Because the drive is mounted on the Linux box, Windows XP complains when I try to "Safely Remove Hardware". As a result, I have to "umount /home/backup", then "Safely Remove Hardware". After connecting the new drive, I then have to "mount /home/backup" in order to use it again on the Linux box.
Now, this question may be a Windows XP question, but I was wondering if there is anything I can do on the Linux box first. Is there anything that can be done on either end, so that I won't have to "umount /home/backup" first?
Ubuntu 9.04 Gnome Desktop (although I have seen the same situation in other versions).When I have a removable media device installed such as a USB flash drive, a CD/DVD or an SD card in the built in reader I have a corresponding icon on the desktop. So here is my situation...I have a 16 GB SDHC card installed in the reader in my netbook as additional storage. As the main solid state "hard drive" itself is only 16 GB I leave the card in at all times. I would like to do away with the desktop icon as I never use it to access the SD card. Any way to do this? I believe it appear as part of the HAL process so perhaps it will go away with 10.04.
Recently set up root encryption with a couple of LVM volumes inside one LUKS volume, and I am just a little confused as to how I would go about getting it to automatically unlock using a keyfile stored on a USB flash drive, I presume I would have to put the drive in the fstab inside my initramfs (if there is one), and add a hook for USB device support.
But I digress, essentially, I want to know what I have to do to enable my LUKS volume (containing all of my partitions sans /boot) to unlock using a keyfile stored on a USB flash drive, rather than a manually entered passphrase.
I have an internal disk with Linux installed and a removable drive bay for swapping out my windows disks. I'd like to get grub to map one option to the bay and be able to boot whatever disk is in there.
Right now it's mapped by id "/dev/disk/by-id/ata-ST3250310AS_6RY00KB61" but I noticed there is a by-path option. I am not sure how to use it and the documentation isn't very detailed. Is by-path a good way to do this or is there some other way to get this to work?
my laptop, which i run ubuntu on, is getting a bit old and i find it's getting slower and slower at running applications. My desktop computer is stronger, but I can't give up on the portability of my laptop.I was thinking of installing a HD drawer for both my laptop and desktop. and when I come home just pull the HD from the laptop and plug it into the desktop.
I have had a Supermicro X7DCL-3 motherboard based machine, running CentOS 5.2 x86_64, recently upgraded to 5.3.Strangely enough, although I must have installed the 5.2 using DVD disk, the running system does not show the DVD drive. The machine was not used very much so I noticed that only today, after the update. There is no trace of it in 'dmesg', thera are no /dev/cd* and/or /dev/dvd* devices. The IDE controller is IT8213 (as shown by 'lspci'). In 5.2 kernel (2.6.18-92.el5-x86_64) lspci says "unknown device". I have checked the /usr/src/kernels/*/.config files and both kernels (5.2 and 2.6.18-128.el5-x86_64 of 5.3) seam to have the support for that controller added into the kernel:CONFIG_BLK_DEV_IT821X=yAny idea why it is not working? The Supermicro has apparently noticed this also as their OS compatibility chart lists the IDE interface for that motherboard as supported up to RHEL 5.1 but not for 5.2.
I'm experimenting with a K8055 board, connected through USB to our Asterisk server,running on CentOS. If I connect the device I can see it being connected by watching /var/log/messages. Also the device is mentionned in /proc/bus/usb/devices. But when I do lsusb the device isn't showing up and it should be showing up! If it is not listed with lsusb, I can't connect to it through the k8055 executable...
I have been using SLES 10 SP1 so far with about 6TB Raid system without problems.I have upgraded the OS to CentOS 5.3 i386 and I have noticed the kernel can not recognize raid system larger than 2TB.Is there any parameters that I have to set ? or the i386 distribution simply does not support larger raid, so I have to use x86_64 version, instead?
Not sure if this is a networking issue or not but I have a Buffalo drive NAS device that I have my mp3 on. I can see it from my Ubuntu laptop, I can see it from my windows laptop. However when I go to my centos system and the networking option under the places menu nothing comes up. I do see a workgroup and a network option. I tried both but just opens a blank folder. How can I get this drive to mount to my centos system?
We are having issues with LVM on CentOS 5.4 both 32bit and 64bit on one particular machine. I just can't get my head around it. Usually a device in /dev/ is created when a LVM Volume Group is created. e.g. if you add a volume group called foo, you would have /dev/foo to work with to access LVs inside the volume group.
For some reason it's not being created. The udev service is running, the volume group is created ok, I cant see anything strange in logs or strace.
I just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site. Now I tried to boot it, I ended up failing with this message: Code: Waiting 10 seconds for device /dev/sda1 ... Root device '/dev/sda1' doesn't exist, Attempting to create it. ERROR: Unable to determine major/minor number of root device '/dev/sda1' Here is the important part of my menu.lst:
[Code]....
I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:
I have added CentOS5.5 x86-64 to a linux box that already contains installations of Ubuntu 9 and SL 5.2. Grub2 was installed with Ubuntu and is on the MBR of the disk. I did not install grub with anaconda/Cent. Grub update in ubuntu finds the Cent install and addes it to the grub.conf, and Cent appears in the grub menu at boot. If I select Cent, I get the following error. VFS: Cannot open root device "sda7" or unknown-block(0,0) Please append a correct "root=" boot option
Below is the output of boot_info_script, which gives the relevant boot file data. There are still grub conf files on the SL install, but grub is not installed there anymore. Boot Info Script 0.55 dated February 15th, 2010 => Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #6 for /boot/grub ..... sda3/boot/grub/grub.conf: # grub.conf generated by anaconda # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means that all kernel and initrd paths are relative to /, eg. # root (hd1,2) # kernel /boot/vmlinuz-version ro root=/dev/sdb3 # initrd /boot/initrd-version.img
i have 5.4 installed on a super-micro server motherboard (has two gigabit ether ports). when i boot while its initializing everything it gets to the "starting eth0" and just stays there?
right before it boots up and says press any key for options i press a key and choose "centos (2.6.18-164.el5)" and it boots up fine but when i choose "centos (2,6,18-164.el5xen)" the problem occurs. and that is the default boot option.
I have a LVM snapshot that triggers these kernel errors when any LVM-related commands run:
Jul 6 10:31:38 itmanager kernel: attempt to access beyond end of device Jul 6 10:31:38 itmanager kernel: dm-28: rw=0, want=66156996183394672, limit=25165824
dm-28 is the snapshot volume in device mapper. I think this error is generated because most LVM commands will check the first 4K of various drives and volumes for LVM metadata and labels, but attempts to read any of the first eight sectors (ie: 4K) of this particular snapshot logical volume trigger this error.The most interesting thing is that the snapshot is 25165824 sectors long (12G), but attempts to access the first eight sectors result in an attempt to access sector 66156996183394672!I've obtained an info dump from getinfo.sh disk, and added the output from lvs. You can find the results here:URL.. It's not as if the sectors that back the first 4K of the volume are corrupt, either: the read request never hits any hardware because the read request is attempting to read a non-sensical sector, instead of the correct sector. Perhaps the COW metadata for the snapshot is corrupt?
How do I find the cause of this problem?Is this a critical error that I should file a bug report for?I first noticed this some time after turning the machine on Sunday afternoon.As far as I can tell from the logs, the shutdown the previous evening was normal.I use LVM fairly heavily on this machine, and this is the first time I've ever seen this kind of problem..I've worked around the problem by copying the first eight sectors from the Origin volume, and the rest from the Snapshot volume, to a new normal logical volume.However, I'm still concerned about how this error occurred in the first place.