Home > Failed To > Failed To Identify Init_dev_params

Failed To Identify Init_dev_params

Reporting your findings on a bug report from someone else clearly stating the problem, where some module breaks down in conditions we all can reproduce, seems logical to me. Signed-off-by: Matt Johnson Signed-off-by: Jeff Garzik Joseph Salisbury (jsalisbury) wrote on 2012-05-29: #4 Would it be possible for you to test the latest upstream kernel? I try to mount it as msdos: mount -t msdos /dev/sdf /mnt/bob mount: /dev/sdf: can't read superblock I try to mount it as vfat: mount -t vfat /dev/sdf /mnt/bob mount: /dev/sdf: Subscribing... http://smartnewsolutions.com/failed-to/failed-to-execute-init-kernel-panic.html

Mark as duplicate Convert to a question Link a related branch Link to CVE You are not directly subscribed to this bug's notifications. Tango Icons Tango Desktop Project. So I agree in this case people should file a new report. The command is in /sbin and needs to be run by root.

Also, I've just switched from Ubuntu 12.04 amd64 to Linux Mint 13 MATE amd64, so I'm unable to file using ubuntu-bug. Self-test supported. Not the answer you're looking for? [email protected]:~/Desktop/disktype-9# ./disktype /dev/sdf --- /dev/sdf Block device, size 7.461 GiB (8010842624 bytes) disktype: Data read failed at position 0: Input/output error That's not good.

Can you check it on another MB or PC ...(in "ahci" mode) ?Plugged it into another machine with another known working cable and port, and it is still not getting recognized.Just I had no more good ideas, but thinking I have only a few days old backup on my server, I put my drive into aluminium bag (for storing tea) and put Please test the latest > v3.4kernel[1] (Not a kernel in the daily directory). Selected the device (/dev/sdf) and scanned for Intel partitions.

Connected and it was immediately recognized. You can tell they are 80 pins because there are twice as many wires, it probably says it in really small type on the cable, and the master/slave/mb ends are colorcoded Problem booting and detecting HDDs in kernel > 3.2.0. > > Status in “linux” package in Ubuntu: > Incomplete > > Bug description: > While HDDs conected to my SB950 controller http://askubuntu.com/questions/168765/how-to-figure-out-why-a-sata-hard-drive-wont-show-in-dev-and-therefore-wont Extended self-test routine recommended polling time: ( 43) minutes.

Failed to mount '/dev/sdf': Invalid argument The device '/dev/sdf' doesn't seem to have a valid NTFS. issue ?Other than the usual hardware checks, ..., including sata cable swapping, MB Bios updates, HDD pin assignments, if any?, ..., ?, then, it's very possible your "WD black" is problematic. Does anything show up in /media? Conveyance self-test routine recommended polling time: ( 5) minutes.

Anfang Ende Blcke Id System /dev/sda1 1 83220 41942848+ 7 HPFS/NTFS /dev/sda2 83221 290708 104573952 7 HPFS/NTFS /dev/sda3 * 290710 581418 146517336 7 HPFS/NTFS Platte /dev/sdb: 300.0 GByte, 300069052416 Byte 255 http://bbs.archbang.org/viewtopic.php?id=4014 Well I use NNTP and I run my MUA with increasing date at the top, so if I read that literally it would imply you haven't sent that post yet But Code: ata4: SATA max UDMA/133 cmd 0xc800 ctl 0xcc00 bmdma 0xd008 irq 18 input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input1 ata4: link is slow to respond, please be patient (ready=0) ata4: SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 200 197 051 Pre-fail Always

The Errors [ 84.477938] ata4.00: status: { DRDY } [ 84.477947] ata4: soft resetting link [ 84.823369] ata4.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 84.823372] ata4.00: revalidation failed (errno=-5) [ Check This Out Problem booting and detecting HDDs in kernel 3.2.0. HDDs attached to the Marvell controller were only recognized when IOMMU was disabled. Last edited by vegan6 (2013-01-01 09:17:18) Offline #2 2012-12-30 10:29:22 Mr Green Administrator Registered: 2010-11-07 Posts: 6,683 Re: [Solved] 64 bit Arch cannot see new 2tb Sata drive With drive connected

It also ups the heat of this bug making it more important. Brad Figg (brad-figg) on 2012-05-27 Changed in linux (Ubuntu): status: New → Confirmed madbiologist (me-again) wrote on 2012-05-28: #3 This device appears to have more than one PCI ID. On what may or may not be a related issue, I've also got a WD USB drive that the computer no longer sees, either. Source After connecting the drive, it seems to try about five times to establish a SATA link.

Advanced Search

Forum English Get Technical Help Here Hardware Need some help with hard drive issues Welcome! Thank you for your understanding. I've booted from SystemRescueCD and at least got some output from the Linux Kernel, trying to initialize the drive (it gave up after a while): [ 7.351024] ata2.00: link is slow

Will be marking as solved, thank you for your help!

mounting the warm drive at slower speed I looked at the label of the drive and saw that it had two jumper settings: enable spread spectrum clocking enable 150Mb/sec bandwidth limit SRST failed (errno=-16) Freezing it seems to have made it worse. Last edited by scjet (2012-12-30 13:00:52) Offline #5 2012-12-30 13:04:48 vegan6 Member Registered: 2012-08-10 Posts: 4 Re: [Solved] 64 bit Arch cannot see new 2tb Sata drive scjet wrote:It obviously sounds Penalver (penalvch) wrote on 2014-01-15: #30 M.

SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was IMHO, that's worth doing because you'll often get some warning of an impending failure. In this particular case the correlation is quite clear and seems to be identified as a Marvell SATA driver misbehaving which, in combination with VT-d and the IOMMU kernel module, results http://smartnewsolutions.com/failed-to/failed-to-add-entry-index-generation-failed-at-usr-sbin-smbldap-useradd-line.html But slowing down the drive from the default of 1.5Gb/sec sounds like a good thing to test.