I want to be able to change the root device, say from sda to sdb, so that I am able to remove sda. I don't believe this is possible with chroot, as I am changing the root folder to a mount point that exists on sda (sdb is not on fstab), so removing it would lock up the system.
Any thoughts how I can do this?
An old machine in our office, running Ubuntu 6.06 all of a sudden will not boot up. I get the following info during boot:
Uncompressing Linux... Ok Booting the kernel
mount: Mounting /root/sda1 /root failed: No such device
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory
[code]....
I haven't changed anything on the system as far as I'm aware, and I ran some HD diagnostics and everything seems fine. however when I try to mount the drive with the following command:
sudo mount -t ext3 -o rw /dev/hda1 /mnt
I get the following error:
mount: wrong fs type, bad option, bad
superblock on /dev/sda1, missing code
page or helper program, or other error
In some cases useful info is found in
syslog - try dmesg | tail or so
I ran fdisk -l and it says the partition type is Linux. The output after running dmesg | tail :
[12207.483801] init_special_inode: bogus i_mode (101)
[12207.483809] EXT2-fs: corrupt root inode, run e2fsck
[12260.427078] init_special_inode: bogus i_mode (101)
[code]...
Update: After running e2fsck -p /dev/sda1, I get the following info:
/dev/sda1: clean, 142449 / 9584640 files, 5402711 / 19161520 blocks
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:
[Code]....
I created a chroot jail in /SECURITY/Jail. But when I used the command 'sudo chroot /SECURITY/Jail' to enter the fake root, I got an error message likegroups: cannot find name for group ID 105groups: cannot find name for group ID 119.
View 1 Replies View RelatedNSA's Guide to the Secure Configuration of Red Hat Enterprise Linux 5 recommands restricting device ownership to root only.
So my question is why should we restrict device ownership to root? And what does device ownership mean anyway in Linux?
I need to change a filename but when I boot up I get the message root device is read-only. Is there a way of changing this so that I can change the filename. I have a Mac Pro running Leopard OSX. The graphics card an NVIDIA 7500GT or driver has failed. It was suggested elsewhere that I change the relevant kext files to filename.kext.old, which I did, now when I try to boot start in OSX I get a message in various languages telling me to restart. I have tried booting in safe mode and from original Installation CD. In Safe Mode I get the same multi language splash screen, from CD I still have the graphic card problem, screen freezes and artifacts appear. So I boot up straight into CLI by holding down CMD-S hoping to be able to change filenames back but it says device read-only.
View 2 Replies View RelatedI've installed Ubuntu 9.10 server on old hardware. The boot seems to have a problem. See the screenshot attached. When I see that and type "exit" the normal login is displayed. There was nothing special about the install. Anyone has an idea how to fix it?
View 1 Replies View RelatedI've taken the kernel 2.6.33.3 and edited the .config file to take out most of the compatibility etc. that I will not be using. I'm run the makes and updated grub. I go to boot it runs through most of the way until I get the following:Quote:/bin/plymouthd: symbol lookup error: /bin/plymouthd: undefined symbol:ply_chara could not read byte from child: SuccessNo root device foundBoot has failed, sleeping forever.'m fairly new to Linux and still more of a dabbler. (Though this seemed more difficult than "Who is root" so I didn't put this in the newbie thread.)Any ideas for what might be wrong?I've tried looking in the config file from something that relates, but they have all been included (Y) in the module.
View 2 Replies View RelatedIn Linux, Is there a way to remember/change a path to a USB device? In my case, I need linux to remember that my USB serial adapter will stay on /dev/ttyUSB0, but when I unplug it and plug it back in, it switches to /dev/ttyUSB1. I'm using a debian-based distro(mint)
View 1 Replies View RelatedFor example /dev/loop*, /dev/raw/*, etc., they are automatically reset to root/root after rebooted.Change the owner/permission of device files maybe not a good idea, though. I just want to know if it is possible and how?
View 1 Replies View RelatedIm trying to run this program and they say I should not run it as root but as a diff user. how to change from root to dif.user. I am using linux CentOS 5.5. Is it a terminal command? How do i create a diff user and log in as it?
View 5 Replies View RelatedFor a user on a Linux host, I need to make everything inaccessible besides his home directory. I have heard that this is usually done by changing the root directory for the user (and setting it to the user's home directory), however I couldn't find the way to do it.
I thought about the chroot command, but it seems it just runs the specified command, considering the specified directory as the root directory. So it seems chroot is not what i need. So my question is: what is the command which changes the user's root directory?
Why would I need to be root to change the ownership of a file? Example: I'm logged in as dwadmin and I've created a file:
-rw-rw---- 1 dwadmin dgw 0 Jun 17 07:46 testing.txt
I want to change the ownership to another user, but am getting the following error: chown 511 testing.txt chown: changing ownership of `testing.txt': Operation not permitted
regarding the file permissions of /etc/passwd in fact it has permissions like rw-r--r--so it says others have only read only permissions but my questions is if others has read only permissions on /etc/passwd file.how they are able to change their password i.e others are able to change their passwords then how it is possible.
View 3 Replies View RelatedAccidentally I changed the ownership of all the directories under / to my own instead of root:root. Now I am unable to use sudo and many bad things are happening. Is there a way to revert the changes or change the permissions again to root:root or make sudo work ?
View 3 Replies View RelatedI was unable to change the permissions for root node and for other users also. WE have tried all the possibilities like chmod and chmod -R 777 filenem. But we are unable to change that.
View 4 Replies View RelatedHow to change user to root user in obuntu 10.04
View 6 Replies View RelatedInstalled Maverick last night... the system has been working fine all day... then on a reboot tonight got the following.
RAMDISK: gzip image found at block 0
usb 1-2: new high speed usb device using ehci_hcd and address 2
uncompression error
VFS: Cannot open root device "mapper/mylaptop-root" or unknown-block(0,0)
[code]....
Then it gives the Kernel Panic
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper not tainted 2.6.35-22-generic #35-Ubuntu
Then a call trace...This is a brand new install of Maverick I copied my files onto a USB and did a fresh install on the whole drive using the alternate CD (the desktop and netbook editions both failed to read on my system) was previously using Karmic with no issues. I tried to e2fsck the dev/sda1 from the CD in "repair broken system" mode but the return was "clean" I read that as the file system being intact but this is an area that I have no real knowledge in.
I installed ZTE MF 626 modem in my F10 with kernel 2.6.27.12-170, i run usb_modeswitch and so far things happened normally. Watching through /var/log/messages it says that F10 detects two port device for this modem: ttyUSB1 and ttyUSB2, and in the sequence it disable port ttyUSB1 BUT Network Manager still set this port.I mean, when i connect via wvdial appointing to ttyUSB2 i get connection, but Network Manager fails to do it appointing to ttyUSB1. How to change device port in Network Manager?
View 1 Replies View RelatedI have pc/os linux 2009 installed and I recently got the following message while trying to boot up my system:
*checking root file system...fsck 1.41.4 (27-Jan-2009) dev/sda1 contains a file system with errors, check forced. /dev/sda1:Inodes that were part of a corrupted orphan linked list found. /dev/sda1:Unexpected inconsistency;run fsck manually. (i.e., without -a or -p options) fsck died with exit status 4
*An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode.
*The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. after performing system maintenance press Control-D to terminate the maintenance shell and restart the system.
Give root password for maintenance:
The problem is, when I enter my password I get an incorrect password prompt. How can I change my password so that a manual fsck can start? Why did this message error message appear in the first place?
I created 2nd root (root2) by running useradd -o -u 0 root2 is it possible to deny root2 to change password of original root?
View 11 Replies View RelatedI need to edit the system time as a not-root user. I am carrying out the following actions in my program.
1. Read the User Id of the process. User_ID= getuid()
2. Printing Capabilities(Permitted, Efffective, Inheritable)of the process
3. Setting UID = 0, using setuid(0)
4. Calling the prctl(), function to keep capabilities
5.Switching the UID from root to User_ID of the process
6. What we have now is a process with root capabilities as a non root user
7. On printing Permitted, Effective, Inheritable capabilities, I get the following
--> Permitted = 0xfffffeff = Effective
Inheritable = 0x0; with UID = 1001;
8. I then try and set the system time with --> system("date -s 10:00");
9. I get an error: date: cannot set date: Operation not permitted
10. I am unable to understand as to why I cannot set the time even thought the capability bit CAP_SYS_TIME in the Permitted and Effective sets are SET.
I am trying to create a jailed shell for a user Don($UID '500') using my own method(I don't want to use any ready-made "jailkit"). The user don should get a home directory /jail/don instead of /home/don when he login via SSH (So that he will not able to see any other files/directories on the system)
This is what I have done.
Quote:
Code:
It works without any issue ....Home directory changes to /jail/don when I ssh to the system as user don. ie: #ssh don@192.168.0.66
Then I added a chroot command to this code.
Code:
Unfortunately , now I am getting an error message saying that "chroot: cannot change root directory to /jail: Operation not permitted" .. I am not sure how to rectify this error... Is my approach correct to get a jailed shell using /etc/profile file ?
I got a problem with my kernel. The initramfs source is busybox, python and gcc from ubuntu. The busybox have i compiled it self. Python and gcc is from /usr/bin. I gonna install my kernel on a i586 machine. Old yes. On the xTerm (termial) it stand "root device 8,1).
Quote:
VFS: Cannot open root device "sda1" or unknow-block(0,0) append a correct "root=" boot option; here are the available partions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)Pid: 1, comm: swapper Not tainted 2.6.38.3 #1
Call trace: This is my syslinux.cfg
default menu.c32
prompt 0
menu title BOOTLOADER
[code]....
I got a HP LH 3000.Current OS release is RH9 2.4.20,and I wanna update it to RH9 2.6.5 While updating,I met the problem followed:
VFS:Cannot open root device "hdxy" or unknow-block(0,0)
Followed are packages I used:
device-mapper-1.00.19-2.i386.rpm
linux-2.6.5.tar.bz2
mkinitrd-4.1.18-2.i386.rpm
lvm2-2.00.25-1.01.i386.rpm
module-init-tools-3.2.tar.bz2
First I installed the mkinitrd-4.1.18-2.i386.rpm, then compiled the kernel and installed it.
Now I know that in order to change the colors in your terminal you have to play around with ~/.bashrc But the effects don't stay in place after a change-root is taken affect. It just reverts to black. Is there any way I can change that too in .bashrc?
View 3 Replies View RelatedI needed to use CIFS for accessing a NTFS network share. I decided to include CIFS in the kernel and tried compiling and installing it. Now when I (try to) boot in my new kernel with CIFS support, I get the message: gave up looking for root device.
View 5 Replies View RelatedI have been working with a project pc. I have a new HD loaded with Linspire. After loading the o/s I replaced the motherboard and cpu. I now have a Biostar A780L (Didn't see it listed on the HCL) and an AMD Athalon II Multi-Core Processor. Now when the pc boots I get an error:VFS: Cannot open root device "343" or 03:43 append a correct "root" boot option Kernel panic: VFS: Unable to mount the root fs on 03:43 I tried reloading the o/s but the disk won't read from the DVD ROM. Checked my BIOS and it appears to me that it should read from the DVD ROM first but it goes to the HD and tries to load the o/s there.
View 6 Replies View RelatedI'm very new to Linux, i'm running Ubuntu and i'm trying to install a program. In the instructions it says "Check that you ARE NOT root, never run similar tools as root! just change file permissions". How do i check if i'm root or what am I supposed to do here?
View 7 Replies View RelatedI have a redhat ES3 I want virtualized.the virtual machine encounters a problem starting when it is virtualized
There are this message :
RAMDISK : couldn't find valid RAM Disk image Starting at 0.
VFS: Cannot open root device "LABEL=/" or 00:00
please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00