Found a raw device for my card when reading through the /proc/partition list but got a "no device" message when mounting the card - mount -t vfat /dev/sda1 /var/card though there is sda in the list.How to know if sda1 exists?
This morning it would not boot; when I tried to wake up the system, it gave me a bunch of errors, the last ones being as follows: "mount error: could not resolve address for servername: No address associated with hostname mountall: mount /media/shares  terminated with status 1" I am writing this in Win 7 since I lost ubuntu. I am using ubuntu 11.04.
what now trying to mount partition get this error this is the partition ubuntu 9.10 is installed on and upon reboot error no device with a long string. mount: can't find /dev/sda6/mnt in /etc/fstab or /etc/mtab
so now that I believe I've successfully mounted the partition how do I direct the bootloader to this partition /dev/sda6 on /media/11076e45-e27d-470b-bb6d-6894f7809a0c type ext4 (rw,nosuid,nodev,uhelper=devkit)
I virtualized a PC with VMware vCenter Converter. But when I boot my virtual PC, I have an error.I found this link but I can't mount /dev, /sys and /proc. I have this error message : mount: /dev is not a block device.
why I'd be receiving this error. I have created a partition and filesystem and put the label in fstab. Everytime I reboot the server it is unable to mount the filesystem. However I am able to mount it manually.
Ubuntu was a good choice for free server O/S. I am currently downloading it. My ISP wants to bind my static IP to a MAC address of the device that will be making my connection for me. Should my server be behind my router or in front of it? I kinda wanted it to be the access point and be able to monitor the usage from all the terminals in my house. We have 4 other PC's, a laptop and a PS3. My server is a Acer Altos G530 with 3.2 Xeon Processor, 4 gb of ECC DDR,
How can I find which /dev/? device to mount my USB hard drive on redhat 3 taroon, I've been googling a lot and checked log files and still no clue. I'm trying my last chance with you experts, # /sbin/fdisk -lgives nothing about the USB drive
# lsusb -vv Bus 004 Device 005: ID 059f:0951 LaCie, Ltd Device Descriptor:
I'm not really sure this is the right category for this post...
I've been thinking and reading but I really don't find a solution, and this is why I decided to post here. I'm not a newbie using Linux but I know absolutely nothing about nfs and related stuff. If explanations are not clear/precise I'm sorry and absolutely open to explain myself better (I'm really desperate, at this point).
I'm running a Debian in a VirtualBox inside a RHEL5. To supply space to the virtual machine I'm trying to mount a disk (? maybe not?) that I created in the RHEL.
In RHEL: I created a directory /some/path/dir and I granted access to it from the VM (edit /etc/exports file and restart the nfs service)
In Debian: I created a directory to be used as mounting point (mkdir /other/nice/path/dir) and I tried to mount (mount -t nfs -v redhat:/some/path/dir /other/nice/path/dir). What happens next is the following:
mount.nfs: timeout set for Thu ... mount.nfs: text-based options ... mount.nfs: mount(2): Input/output error mount.nfs: mount system call failed
Now, this Input/output error is too vague to trace where the problem is, but I really have no idea about how to go more in depth (are there logs somewhere? What should I look for? ... ...).
I've got the F13 LiveCD that I was able to boot and use using the "nomodeset" boot option. From the desktop I'm trying to perform an Install to Hard Drive. I've read the Install from LiveCD post regarding the creation of a /boot partition and a / root partition. I've tried creating them without the LVM group and with. But every time I appempt to install I get...
An error occurred mounting device proc as /proc: mount failed: (9, None). This is a fatal error and the install cannot continue.
Hardware is a Sager 8887 (P4, 3.06HT, 60GB HDD, Radeon 9000 graphics adapter)
I have a Corsair R60 ssd disk which is a disk with both sata and usb connectors. But the usb thing seems to be a bit non-standard, or maybe its just my fedora linux.When I insert the disk using a usb cabel to a running Fedora 14 linux system, a device called /dev/sg3 is added but that is all. No new /dev/sd* device is created so I can't mount the disk.
So the disk is there. (The last entry) but my linux will for some reason not see it as a usb hard disk. When I insert other usb disks they work fine. It is only this specific disk which causes problems. I have tried on 3 different computers with the same result.
A hint to the problem may be that if I add the disk to a windows system(With usb) the disk is called "A fixed disk" and not a portable disk as expected. The disk works fine with linux If i connect it with the sata cabel, but I would really like to have it working with usb too. (To mount it on computers without sata).
Added:I did try to mount /dev/sg3 but mount say that its not a block device. (File say Its a character special device).
Added output from dmesg:
[ 97.454073] usb 7-1: USB disconnect, address 2 [ 105.913055] hub 2-0:1.0: unable to enumerate USB device on port 3 [ 107.048054] usb 2-3: new high speed USB device using ehci_hcd and address 5 [ 107.162900] usb 2-3: New USB device found, idVendor=1b1c, idProduct=1ab8
I found an other guy with exactly the same problem [URL] so I think its beginning to look like a bug in the drives firmware or in the linux kernel.
Final update:Corsair have said that the disk design is broken and there does not seem to be any way to make it work.
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:
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 install kernel rpm after i boot that kernel network not working kernel name : kernel-rt-trace-18.104.22.168-132.el5.centos.i686 [URL] error "Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring."
I am developing a device that will run Linux as its operating system.The device is a small form factor X86 device with a flash drive exposed as a SATA-device. So it is not very dissimilar from any other PC running Linux.For several good reasons I am building my own "distribution", instead of using an existing one.What confuses me is how mount/umount of the root file system is handled.I boot my kernel with the commandline "root=/dev/sda1 rw" which works fine. But everytime I do poweroff or reboot Busybox complained about no /etc/fstab, so I decided to build one.Should I have an entry for my root file system? It seems like this is shadowed by the rootfs anyway. I.e. if I have the fstab entry "/dev/sda1 / ext2 1 1" mount still reports rootfs on / type rootfs (rw)/dev/root on / type ext2 (rw,relatime,errors=continue)My questions are:Do I need to worry? Will the drive be correctly unmounted by the kernel on poweroff/reboot?If I want to perform file system checking on boot, can I do that without resorting to an initrd?
I have a program which mounts /dev/sdb1 for which I lack the source code. This device does not exist on my RedHat 9 system and I want to create /dev/sdb1 such that it's an alias for /dev/hdb1 Can I do this? with MAKEDEV?
I need to have an alias which will allow it to mount, not create a symbolic link to an already mounted directory. i.e. 'mount /dev/sdb1 /mnt/harddrive' should actually mount /dev/hdb1
I'm using an external USB drive to perform system backups. The script I'm using has a mount command - mount /dev/sdcx /systembak, it works fine until the external drive is mounted into a different USB port which causes the device path to change and the script needs to be modified to reflect that change. Looking in the /dev/disk/ directory I see ./by-id ./by-label ./by-path ./by-uuid. I've been able to mount the disk using one of the device pointers in those directories; are any of those device pointers static or do they change every time the USB disk is plugged into a different USB port.
How can I mount a device with specific user rights on start up? I still have some problems figuring it out. I would like to mount the divide with uid=1000 and gid=1000. My current entry to the /etc/fstab/ file looks like this:
I am working on implementing a protocol on NS2.34 .I really need help to solve this problem . Actually , I don't now whether the problem is generated by the tcl code or the c++ code when I run the simulation, I get this result :
Code: num_nodes is set 64 INITIALIZE THE LIST xListHead 34 45 channel.cc:sendUp - Calc highestAntennaZ_ and distCST_ highestAntennaZ_ = 1.5, distCST_ = 550.0 SORTING LISTS ...DONE! code....
I have one hard disk (call her HDA) that contains nothing but a single ext4 partition containing a backup of all my important data. Last night I did a clean install of Ubuntu 10.10 on my primary hard disk (call her HDB) and from there proceeded to upgrade directly to Ubuntu 11.04 upgrade. In 10.10, I was able to read HDA just fine. However after the upgrade, I can no longer mount this drive. When mounting from file browser:
Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/sda,missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so The end of dmesg said the following:
dmesg | tail [ 82.130904] EXT4-fs (sda): bad geometry: block count 122096646 exceeds size of device (122096381 blocks)
my hard disk has a block count greater than the size of my device. I've done my background searching on this and tried a command line utility I've never heard of before:
# sudo e2fsck /dev/sda e2fsck 1.41.14 (22-Dec-2010) The filesystem size (according to the superblock) is 122096646 blocks The physical size of the device is 122096381 blocks
this is as far as I've gotten. This drive holds over a decade's worth of work for me and is extremely valuable. I really didn't think that the Ubuntu upgrade process would mess with this drive, seeing as the Ubuntu install was contained on an entirely different drive. What is it that I need to do to restore my drive to working status?