I have an external WD drive (model WD800B015) that works fine under Windows. When I try to mount it under Slack 12.2 (kernel 2.6.27.7-smp), I get a message saying "/dev/sdc1 is not a block device." WD categorically does not support Linux. A google search has not produced any useful results.
View 7 RepliesInstalling in external drive at the point where to put the GRUB loader I have these choices :
1. Master Boot Record (MBR) at -dev/sda (internal HDD)
2. First Sector of boot partition - dev/sdc1 (external USB HDD)
How can I put MBR in sdc instead of sdc1?
The external hard drive which contains all my photos and where I backed-up all my important documents is no longer recognized. It is a three month old 500GB Iomage Prestige Desktop Hard Drive.When I plug it in, it is recognised as a USB device, because it shows up when I type lsusb, but dmesg gives this error message.
[19712.013250] usb 2-2: new high speed USB device using ehci_hcd and address 21
[19712.145347] usb 2-2: configuration #1 chosen from 1 choice
[19712.147214] scsi25 : SCSI emulation for USB Mass Storage devices
[code]....
I popped the disk out of the casing put it on a SATA connect internally and then tried the file recovery programs testdisk/photorec and SpinRite, but both failed because they couldn't recognize the external hard disk.
Im running Centos 5.4 with a sftp server, and I�d like to allow all 172.16.0.x ip and 192.168.0.x ip and block everything else. Does someone have a good way to do this with IPTables or any other opensource FW?
View 10 Replies View RelatedIs there an easy example of a block device driver I could follow as a guide to write my own module?
View 5 Replies View RelatedI 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?
View 4 Replies View RelatedWhen I try to mount the /dev/sdd1 device then it give errormount -t ext3 /dev/sdd1 /4hdmount:/dev/sdd1 is not a valid block device
View 9 Replies View RelatedI created LVM and formatted it. But at the time of mounting it getting this error message ".....not a block device".
View 3 Replies View RelatedHow 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.
View 3 Replies View RelatedIs it possible somehow to block some bluetooth device with specif address (mac) ?
(like iptables block by mac)?
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.
View 2 Replies View RelatedI 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
* I am implementing mass storage device on a test board.
* It contains NAND flash.
* Using corresponding "udc driver" and "g_file_storage" I could make my test board enumerate as mass storage device on my Linux machine.
* my 16 MB pen drive (test board) is now ready for read/write.
But there are some Bad Blocks on the NAND.Hence copy is not complete. Although on Linux machine there is no error message. Now , what is there in a normal pen drive which manages the Bad Block or what am I missing so that such Bad Blocks are managed.
Here is the error I get on my test board :
mtdblock: erase of region [0x2c0000, 0x4000] on "Bon 2" failed
end_request: I/O error, dev mtdblock2, sector 5664
Buffer I/O error on device mtdblock2, logical block 708
[code]....
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 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.
[root@xxxxxxxx etc]# netstat -a | grep iscsi
tcp 0 0 *:iscsi-target *:* LISTEN
tcp 0 0 xxxxx-netapp.okc-:44840 xxxxxx-iscs:iscsi-target ESTABLISHED
tcp 0 0 *:iscsi-target *:* LISTEN
[Code].....
I have a write call to a ttyACM serial device that blocks after several hundreds bytes are written.I'm writing in ~25 byte chunks, so I have 5-8 successful writes, then the next write blocks forever.I can bypass the blocked call using select, but I can never call write again without closing and re-opening the port.
The serial port is opened correctly because I can read from it just fine. Write permissions are correct, and it's opened RW.The code is likely correct because I tested the same code using the same device on a pure RS-232 serial port, and it worked fine - no block. Is there anything to know about the linux ACM module?It's my understanding that write calls basically shouldn't block.They're supposed to return -1 if there's an error.
I have 2 hdds, with encrypted / and /home. Besides there are four other (encrypted ext4) partitions I use rarely. In Fedora 11 at boottime I gave the luks passphrase for / and home and the system booted as intended.
Whenever I needed those extra encrypted partitions I mounted them in Nautilus. Now, in Fedora 12 at boottime dracut tries to open all the encrypted partitions, / and /home are mounted fine, but opening all the other partitions gave the following messages in messages.log:
Quote:
dracut: luksOpen /dev/sdb6 luks-02a0e706-a26f-4019-a2a0-88a0366a994d
kernel: Buffer I/O error on device dm-0, logical block 124
kernel: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-304
kernel: Buffer I/O error on device dm-0, logical block 124
kernel: Buffer I/O error on device dm-0, logical block 124
[code]....
...and these messages are repeated with the other partiitions, and the boot time takes very, very long. How can I tell dracut to ignore those extra encrypted partitions at boottime?
I can browse the iso image easily enough with a loopback mount, but when it comes to mounting the actual CD (which I did first), I get:
Code:
$ sudo mount -t udf,iso9660 /dev/dvd /mnt/dvd
mount: block device /dev/dvd is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/dvd,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
/var/log/messages isn't very helpful, either:
Code:
Jul 15 15:15:56 bkorb-dt kernel: attempt to access beyond end of device
Jul 15 15:15:56 bkorb-dt kernel: sr0: rw=0, want=68, limit=4
Jul 15 15:15:56 bkorb-dt kernel: isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
$ md5sum openSUSE-11.3-DVD-x86_64.iso
adf5d2a0a03c1e3aaf102fd6a4771b87 openSUSE-11.3-DVD-x86_64.iso
I burned it with K3B and it gets the same result trying to mount it. K3B seems to know that the image is an iso9660 and is able to display the various 9660 id fields just fine. It just won't mount.
i have a inspiron 1520 laptop which is starting to slow down some so i thought linux would help because all i do is internet use, so i download it from another computer and mount it to a usb flash drive like the site says, (netbook remix latest version) then i put it in my laptop and it loads all the way and i press try and after about 10 minutes of loading it lets me try. so that was ok really slow but i thought id install it to hard drive to see if it improved speed. so the next time i start my laptop i get Buffer i/o error on device loop0 logical block xxxxxx so i redo the usbflashdrive no errors switch usb ports and same thing, ive done the switch usb ports and redo the flash drive about 4 times im really getting mad at linux before i even have it installed.
View 1 Replies View RelatedI'm trying to upgrade my kernel. When i get to the step where i should build the img for grub (i guess the command below is doing that) I get this error: yaird error: bad device link in /sys/block/sda (fatal)Since I installed debian using a USB drive, HDD1 was /dev/sdb and HDD2 was /dev/sdc, the USB was /dev/sda. Is there a way to force mkinitrd.yaird to build the img for /dev/sdb?
View 1 Replies View RelatedI had installed the CENT OS 5.3 it is installed when i rebooted it gives me error continuously.
Buffer I/O Error on device sda, Logical Block 0
ata4.00 : exception Emask 0x0 SAct 0x0 action 0x0 frozen ......
ata4.00 : status: { DRDY }
why it has giving the error.i have Intel based hardware Core II Duo with 1 GB ram check with sata hard drive 120 GB.
I just downloaded an iso of the latest CentOS dist (5.3) and burned it to disk. I booted from the CD and received the following error:
Memory for crash kernel (0x0 to 0x0) not within permissible range
Illegal mode for this track or incompatible medium -- (asc=0x64, ascq-0x00)
The failed "read 10" packet command was:
Buffer I/O error on device hdd, logical block 176935
(This error message repeats for another 9 or 10 times then it says the following)
Red Hat nash version 5.1.19.6 starting
Setting up new root fs
(Then there are some unmounts which are old /dev, /proc, /sys. At this point a series of steps begin).
Setting Clock
Starting udev
Loading default keymap (us)
Setting hostname local host.localdomain
Setting up logical volume management
Checking file systems
These are just some of the steps that appear after the above error is displayed, all of the steps that load have an ok status. After those are completed I get to a text prompt - localhost login: At this point my keyboard does not seem to respond, pressing enter or any of the other keys seems to have no effect. I noticed that during the load process I could toggle the light for caps and num lock, but at the login screen it does'nt work. So at this point I'm not sure if I'm having a technical issue or if its just another case of an user error.
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.
View 2 Replies View RelatedCreate symlink /dev/root and then exit this to continue the boot sequence.
Buffer I/O error on device sr0, logical block *******
sr 4:0:0:0 [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sr 4:0:0:0 [sr0] Sense Key : Medium Error [current]
sr 4:0:0:0 [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1395920
Clocksource tsc unstable (delta = -499902943 ns)
loops that during install. new hard drive fresh out of box. WD 320GB 7200 Toshiba Qosmio intell core duo i've installed with this same disk before previous hard drive died. installed over windows vista. this time im trying to install solo no windows disk to reinstall with, F10 only. I've tried other distros as well, Mandriva one 2009, Dreamlinux, and this one. i've suspected hard drive controller went out but i can format and partition the drive. also the cd/dvd drive is bad but im booting from cd fine. tried removing the cd drive and booting from an external usb cd rom, same errors.
im about to deploy and need my computer up and running ASAP. 7 months no entertainment is not good. when i use a linux boot disk from Ultimate Boot Disk (UBD) i get an error of - hda status no response and something about invalid heads dreamlinux pushes past the error till i get the error about cant start x server. about my graphics
I created a start up USB and I try to install it on a computer I have, however, everytime I try I get the following error repeated...
[35.877830] end_request: I/O error, dev fd0, sector 0
[35.877869] Buffer I/O error on device fd0, logical block 0
emulate the USB using the force FDD option. I tried emulating a hard drive instead but then it doesn't boot up into ubuntu.
I'm having trouble mounting hard drives and partitions - and am rather nervous about using Yast partitioner to do this. Is there something that would tell me about mount points in Yast partitioner? So far I haven't been able to find that information anywhere. I don't want to lose information on existing drives and partitions but do want to be able to access them.Some of them appear under disk information in "My Computer" but if I try to mount them I get this error message.There is no application installed that can open files of the type block device (inode/blockdevice).I was trying to edit fstab,his didn't seem straightforward either. I've been hacking this about in other Linux distros - so not entirely clueless
View 6 Replies View RelatedI 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 had found the following error messages one of my Linux server. the file system using for this partition is EFI GPT. Is this cause because of RAID controller incompatibility or Driver mismatch? PHP Code:
[Code]..