I want to keet some data on windows dir. I have tried the below command and giving the below error.
[root@xyz0044 ~]# mount -t cifs //10.48.64.52/jata -o username=domainv.kumar3,password=xxxx /mnt/backup
mount: block device //10.48.64.52/jata is write-protected, mounting read-only
mount: cannot mount block device //10.48.64.52/jata read-only
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.
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:
Code:
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:
Code:
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:
Code:
# 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
[code]....
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?
I decided to take an old Gateway that I bought off a guy cheaply and turn it into a file and web server.I purchased copies of Debian 5.0.4 i386 disks (31 in all) on the advice of a friend, the disks weren't expensive, but now that Ive installed all the disks, I'm having a variety of errors
[443.110940 end request: I/O error, dev hde, sector 76021855 [443.111074] EXT3-fs error (device hde1): ext3_get_inode_loc: unable to read inode block - inode=2375715, block=9502724 INIT: cannot execute "/sbin/getty"
I used dual booting with Windows Xp and Ubuntu 10.04. Because errors, I reinstall Windows and then I could not enter GRUB, and Ubuntu partition disappear. I tried to reinstall ubuntu using live CD but I could not detect last ubuntu partitions. After I installed fresh Ubuntu on new partition, I got error message like this:
Unable to mount floppy0 Mount: block device /dev/fd0 is write protected, mounting read-only Mount: could not determine the file system type, and none was specified
I am running RHEL5.5 its a fresh install and we are testing Xen Virtualization. We are wanting to use our iSCSI SAN for the VMs. I have created the initiator iqn, and discovered the target address. We are connected to the target, but there is no new block device in /dev.
I get assigned an IP from the university's server. Every now and then, a student will plug in his router to the network trying to get wifi in his/her room.
And by doing so will start assigning IPs on the network, while rendering useless the university dhcp server, which has to cope with a higher number of pc's.
How can I specify to dhclient (or the linux system in general) NOT TO obtain IP addresses given by a specific mac address ?
I have a server that has a Fibre Channel mount that is having issues. When I can in this morning I found that it had switched to read only. Now looking through /var/log/messages I see that there are errors reported on the disk. I know that i will need to run fsck on it, but I do see lines about the device mapper failing for mpath0 first, which is the device which is mounted. I am wondering if someone can take a look and see if this is just a drive issue, or an issue with the fibre channel connection.
uname -a Linux server 2.6.27.25-78.2.56.fc9.x86_64 #1 SMP Thu Jun 18 12:24:37 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Mar 28 00:12:36 server kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK Mar 28 00:12:36 server kernel: end_request: I/O error, dev sdb, sector 314570452 Mar 28 00:12:36 server kernel: device-mapper: multipath: Failing path 8:16. Mar 28 00:12:36 server multipathd: 8:16: mark as failed [Code].....
I had my server going pretty good. Two sites being hosted. Wilmingtoncoc and Mikealrhughes. Last night we had Thunderstorms and Tornadoes come through. While I was out Tornado chasing. We lost power here for an instant and back on. When I came in the server was off. So I booted it back up. The mikealrhughes site is still working good. The Wilmingtoncoc site is giving me a Database read error, it is a WordPress site. Also I can't log into the Server using SSH. Where do I start to repair the problem? Do I reinstall SSH if so what is the command I use? Then how do I solve the WordPRess Database problem? Also when I try and issue a command from the Server with sudo in front of it I get an error message that says - sudo: must be setuid root - whatever that means. I couldn't find that in any of the books I have.
In a nutshell, our RAID 1 array was rendered broken and we were advised that core lib files were missing and the OS needed to be reloaded... a quote from our server host:"The OS is not healthy.This server will need a reinstall. Libs are missing." This was after having replaced what we though was a faulty /dev/sdb. So they reloaded the OS (Debian 5.0.2 x86_64) on 2 FRESH drives, and installed the old /dev/sda as /dev/sdc once the reload was completed. Here's the output of /etc/fstab on the fresh install so we know what we're working with:
The one problem I see myself running into is /dev/md1 and /dev/md2 are currently in use by the new system, so I cannot mount it there. I should also note, reloading the OS is a viable option if needed as we haven't started configuring the server yet. So if we need to reinstall the OS and assign the NEW RAID arrays to something other than /dev/md1 and /dev/md2 then we can do that.
I have a Windows 2003 server with fiber attached volumes (NTFS) that I would like to mount readonly on a linux system to back it up to tape. The fiber device will allow me to present the volume R/W to one host and R/O to another, however, the R/O system doesn't see any of the changes made by the R/W server. In other words, how can I make a readonly volume refresh, scan for changes, or update without un/re-mounting it?
Is the "mount -o --bind" option what I want? From the MAN is doesn't seem right... the option "sync" seems slightly more promising but I think I'm just grasping at straws here. The best I have come up with is a cron job to unmount then mount the volume periodically.
I'm having a consistent problem with instances on Amazon EC2, which a lot of searching including here has resulted in no solution.During boot I see the following message on the console (or "System Log" in the Amazon console):Code:Mounting local filesystems: mount: /dev/sdg already mounted or /apps busy(I'll append a extract from the full log below).Once I log into the instance, I can access the filesystem so it's mounted somehow but I can't figure out what's going on:
Code: # df -k /apps Filesystem 1K-blocks Used Available Use% Mounted on
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.
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)
My F12 installation, which was installed on an HP tx2500z laptop and has been operating relatively well since January, now fails to boot after a frozen screen precipitated a forced shutdown. On reboot, I was dropped into a shell with the error message "Error reading block 1546 (Attempt to read block from file system resulted in a short read) while getting next inode from scan." recommending to run fsck manually. During the fsck run, after a substantial number of Pass 1 inode count corrections, the "Error reading block" message reappeared, with the question "Ignore error<y>" to which I answered "y".
fsck responded with "Force rewrite<y>". Since I did not know what would be written here, I said "no". I then forced shutdown, rebooted into Windows, and searched for further guidance. One suggestion was to run fsck -y on the affected partition. My laptop drive has four partitions, the first two being allocated to Windows and an HP supplied repair partition. sda3 is a tiny boot partition (100 MB), and sda4/5 is the LVM remainder.
fsck -y /dev/sda3 told me the boot partition was fine. fsck -y /dev/sda4 stopped immediately and asked "Could this be a zero-length file partition?". Given the ext3 structure, I suppose the correct answer is yes. fsck -y /dev/sda5 told me fsck.LVM2_Member: not found.
Following this, I then attempted again to reboot, and ran fsck without options. Once again, during Pass 1, Block 1546 exhibited the short read error, again asking about a rewrite - which I once again answered no. Pass 1 completed with another substantial number of inode count corrections, and Pass 2 started - immediately generating the message:
'passwd' in /etc/pam.d (65556) has deleted/unused node 7831. Clear<y>
After some hesitancy, I said "yes", and of course a second similar message appeared. I was brave enough to answer "yes" six more times, with the first two referring to /etc/pam.d inodes, and the next four referring to /etc/security/console.apps inodes. The eighth message, also similar, referred to inodes elsewhere - but by now I did not dare to continue and forced shutdown. Is this repairable, and if so, how?
I am using Wind River Linux- 2.6.27.18-WR3.0bg_standard. The problem is whenever I execute "reboot, ls, cd" and many other commands the OS prompts me an error- "end request: i/o error, dev sda, sector "(different sector each time)" and EXT3-fs error (device sda1):ext3_get_inode_loc:unable to read inode block- inode-4088001, block-4097027 I also executed "dmesg", it also showed similar errors. Has the disk gone bad or the kernel is corrupted?
algorithm:breada input: file system block number for immediate read file system block number for asynchronous read output:buffer containing data for immediate read { if(first block not in cache) { get buffer for first block if(buffer data not valid) initiate disk read } if(second block not in cache) { get buffer for second block) if(buffer data valid) //line 1 release buffer else initiate disk read //line 2 } if(first block was originally in cache) //line 3 { read first block return buffer } sleep (event first buffer contains valid data) return buffer }
Here is an algorithm for block read algorithm. I have problem in line 1: If buffer data is valid why is it releasing the buffer? line 2: If buffer data valid why is it initiating disk read. It should have read directly from buffer? line 3: It should be the first condition as if it is there in cache then it should return it without delay?
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 want to test LVM+Raid. When I was testing ZFS on Solaris, I was able to create regular files, and use those as disks for testing.I tried creating a regular file full of zeros w/ dd, then partitioning that. fdisk seemed to be able to create a partition on the regular file, but mkfs and parted couldn't work with it. Is there any way to create fake block devices for testing?
How do you go about getting the raw size of a block device under Linux from within a C program? And I mean the raw size of the block device itself, not a file system that may or may not be installed on it. And I'd like to be able to get the raw size of any block device, from hard drives (e.g., /dev/sda) to LVM partitions (/dev/mapper/vg0-home) to loop devices to anything else that is a Linux block device.
I'm setting up a machine that's going to be used to test randomly connected tape drives one at a time, and as such, I'm writing the test routine using mt in a bash script, for user-friendliness. The problem is the block device name changes on occasion as tape drives are swapped out and busses are rescanned, so I can't "hard code" a block name into the script.
I know programs like lsscsi and hwinfo will give you block device names as part of their output, but I can't seem to grep anything in such a way as to have the final output be just the block name (ie /dev/st2, or optimally 'st2'), so that I can just have the script read said output, and drop it into the necessary variable.
I built a Raid5 volume with 3 SATA II hard disk drives. Further I have a system disk conected through IDE. During the first setup the IDE disk becomes sda, the SATA II disk sd[bcd] respectively. Now, sometimes the device names change after reboot - why ever... E.g. one of the raid5 disk become sda and so I got an error message during the boot procedure regarding the raid set. Curious, when the system is up and I stop and restart the Raid5 volume it comes up and runs fine. Because I'm currently at work I can't post any more detailed config files at the moment.
I am trying to debug the issue of a desktop that has for the last two weeks started having kernel panics at boot time. This machine has been running flawlessly for the last 8 years, and has had three OS upgrades. I am using memtest to try to understand the issue. The following is part of the memtest output: Reading all physical volumes Buffer I/O error device hdc logical block 0 Buffer I/O error device hdc logical block 15
Illegal node for this track or incompatible media (asc=0x64 ascq=0x00) The failed "Read 10" packet command was /dev/hdc: read failed after 0 of 4096 at 0 Input/output error and similar set of mesaages After this udev checks correctly, and hardware, storage and audio are initialized However sometime in the middle of the boot process, a kernel panic occurs with message Kernel panic -- not symcing : Fatal exception in interrupt