Solved - D Series Hard Drive Tray interchange

All,
I think I've solved the mystery of the hard drive tray interchange for at least the D10 (I don't have a D20 or D30 to compare with, but I think they're similar).
When I was taking my system apart for spring cleaning to evict all of the dust bunnies, three of the five hard drive carriers/trays/brackets broke on the way out. Bad design? I'd have to agree... however, there's an upside.
On a whim, I had my old IBM IntelliStation Z Pro (Model 6221) apart and decided to try the tray from that system in my D10... fits like a charm. The casting is slightly different in that the Lenovos are black (IBMs are blue) and the markings on the sides of the rails are different. Functionally, exactly the same.
And now, the challenge ... I've been looking for these trays for my Z Pro for a while now and haven't been able to find a sane price for these trays. IBM's CRU part number is 23P1328.
Here's the page that shows the details:
http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-45808
For those who are thinking that there's a very similar blue tray out there that was used in the NetVistas, that tray (markings UL:T1055 23-931P(5) 2000A515) does NOT fit. The rails themselves are too thick to work in the rail spaces provided in the D10 or my 6221.
So, if anyone has a source for well-priced 23P1328s for those of us who are out of warranty, I'm all ears. I'd rather not spend a lot of money on a miscellaneous parts kit (41R5630) when I only need one part out of it.
Thanks,
--- A

Guess I broke the trays wrong since the three that I broke all snapped between the indicated pull surface and the rail spar.
Under appropriate pull tension, the curved center area didn't have the rigidity to pull the rail spars in far enough to allow the drives to disengage from the chassis (in my experience).
My only question was why there wasn't a pseudo-hot swap backplane used - turn the drives around and have them snap into the connectors on the far side of the removable door. Seems like that would have been simpler and you could do your cable runs from the SAS or SATA to a sort of patch-panel in order to make sure things were on the right controllers.
And honestly, if that's my only complaint with the D10... (and it is)... it's one hell of a machine.
--- A
IT Professional with 20+ years of experience and a fleet of Lenovos (and an occasional SGI)

Similar Messages

Thinkserver RD230 401116U Hard Drive Tray / Carrier / Sled

I have an RD230 server with no hard drives, and four bare Western Digital 3.5" SATA drives. All I lack are the trays required to install the hard drives. A fellow with technical support tells me that the hard drive trays do not have an FRU, are not sold separately, and that they are available only when purchased as part of a Lenovo branded hard drive.
This fellow is selling OEM trays but I am not sure whether they will work with the RD230. Do all the R-series servers use interchangeable hard drive trays? In other words, if this fellow asserts these trays are compatible with the RD240, can I have some reasonable level of confidence that they are compatible with the RD230?
http://www.ebay.com/itm/New-OEM-Lenovo-ThinkServer-RD240-T350-G7-R520-T260-T280-G3-3-5-SAS-LFF-HDD-T...
Thanks very much for any information you can share.
Best,
Zac
Solved!
Go to Solution.

Well as it happens the server actually included the hard drive trays. In spite of the fact that both our distributor and Lenovo tech support said the server did not include hard drive trays! So never mind.

Hard Drive Tray will not fit after attaching hard drive

(From Davin Oishi)
Issue: After installing the hard drive onto the hard drive tray, the tray will not longer fit into the Smart Storage hard disk drive slot.
Using hard drive tray screws from the legacy NSS2000, NSS3000, NSS4000, or NSS6000 may encounter this issue.
Resolution: Be sure to use the hard drive screws that are supplied with your Smart Storage device. Smart Storage ships with screws for both 3.5" SATA drives and 2.5" SATA drives.

If they are still on your Mac's drive then you should be able to add them back into iTunes via File > Add To Library

LaCie d2 thunderbolt series hard drive reliability

I am considering purchasing a LaCie d2 Thunderbolt series hard drive for my Time Machine backups for our household. We have two MBPs, one is running OS X Yosemite, the other is running OS X Mavericks.
I have read a few older reviews noting that the LaCie drive keeps dismounting during Time Machine backups.
Has this continued to be a problem?

Ryan,
Check drive volume name and also the Computer name. Apple released a tech note recommending that both be limited to only the characters A-Za-z0-9 (no dashes, hyphens, or other special characters.
If you can, send the Apple System Profiler report to me at the addres in my profile. Imay be able to see something there. I have helped another user with similar problems, but with a LaCie USB drive. He got things working by repeating the recommended steps, and double checking everything.
As others have rported, this should work, so there may be something else preventing proper operation.
If the drive is usable from Finder, but Time Machine cannot use it, there is something related in how Time Machine is viewing the drive.
Mike

Pravilion dv7 series hard drive replaced after recovery disc fail

I tried to use the recovery portion of my hard drive when my Pavilion dv7-4173 US laptop failed to operate. After trying the recovery portion of the hard drive several times I got a error message saying the bootmgr was missing. I Tried using the Recovery disks I had made at the store I purchased the computer before taking it home and they failed. They worked up to 32% and then stopped. I took the laptop and the Recovery discs (6 discs) to another retail store's tech department. After several days I was told the Recovery Disc where no good/damaged. When I contacted the purchased store I was told I needed to bring in the laptop and recovery discs. They replaced the hard drive, saying that was the problem, but did not partition it. They decided to up graded the OS system from Windows 7 Home Premium 64 bit to Windows 7 Professional 64 bit., but did not try the Recovery Discs. Can I use the Recovery Disc they made me, if the are good, to restore the laptop back to factory fresh? I know it will place Windows 7 Home OS system back on the computer, but I'd like all the programs back that came with computer. Will I be able to upgrade the OS to Professional? I have the Windows 7 Professional disc. If my recovery disc will not work, can I use the Recovery Disc, only 2 discs as opposed to 6, that I can purchase from HP and then upgrade to Professional?
This question was solved.
View Solution.

Hello skip61. I want to make sure I understand. A shop replaced the hard drive for you and installed Windows 7 Profession 64-bit in the process. They also replaced your bad recovery media with a new set of Windows 7 Profession recovery discs. is this correct?
If you want the notebook to revert back to the factory defaults you will need a set of discs from HP directly. This will properly partition the hard drive and set the notebook back up with Windows 7 Home and the software that came with the notebook.
You can upgrade your version of Windows 7 at any time you'd like. This is a feature built into Windows itself. So check out this Microsoft article on how to update.
To order a set of recovery discs from HP just give them a call. The number is 1-800-474-6836 for the US/Canada. If you're outside of this area check this site to get your region's contact information.
I hope this is helpful; have a great weekend!
Please click the white star under my name to give me Kudos as a way to say "Thanks!"
Click the "Accept as Solution" button if I resolve your issue.

[Solved] E4200 - External hard drive not recognized

My external hard drive, a 2TB WD Elements, does not appear in the storage list in the web utility of my E4200. The drive is formated as NTFS, single partition. It works fine if I connect it to a computer.
If I connect a 4GB USB flash drive (FAT32) to the router, it does appear in the list.
I'm using the latest firmware, version 1.0.02.
Edit: Down(up?)grading to firmware version 1.0.01 fixed the problem.

Carborundum wrote:
Edit: Down(up?)grading to firmware version 1.0.01 fixed the problem.
not surprised. I was going to reccomend you dropped down too. But I see you fixed it. Kudos to you. Im glad it works. Lots of drives dont work with the E4200.
please fix the E4200 media server in .02 firmware

[SOLVED] Possibly dead hard drive or bad raid setup...

I have a 4 drive raid5 running. Just recently one of the drives kept removing itself from the array. I have re / formated / partitioned the drive multiple times, but either mdadm doesn't accept the drive, or it accepts, resyncs, and when i try to access the raid it fails again.
I eventually pulled the drive out and plugged it into my desktop machine. That machine recognized the partition fine. However after putting the drive back into the raid i receive these sort of errors on startup:
Jun 8 17:04:41 localhost kernel: [ 213.942913] ata3.00: failed command: READ DMA
Jun 8 17:04:41 localhost kernel: [ 213.942922] ata3.00: cmd c8/00:08:40:10:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 8 17:04:41 localhost kernel: [ 213.942924] res 51/40:00:40:10:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 8 17:04:41 localhost kernel: [ 213.942928] ata3.00: status: { DRDY ERR }
Jun 8 17:04:41 localhost kernel: [ 213.942931] ata3.00: error: { UNC }
Jun 8 17:04:41 localhost kernel: [ 213.979780] ata3.00: configured for UDMA/133
Jun 8 17:04:41 localhost kernel: [ 213.979794] ata3: EH complete
Jun 8 17:04:44 localhost kernel: [ 216.508311] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 8 17:04:44 localhost kernel: [ 216.508316] ata3.00: BMDMA stat 0x24
Jun 8 17:04:44 localhost kernel: [ 216.508321] ata3.00: failed command: READ DMA
Jun 8 17:04:44 localhost kernel: [ 216.508330] ata3.00: cmd c8/00:08:40:10:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 8 17:04:44 localhost kernel: [ 216.508332] res 51/40:00:40:10:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 8 17:04:44 localhost kernel: [ 216.508336] ata3.00: status: { DRDY ERR }
Jun 8 17:04:44 localhost kernel: [ 216.508339] ata3.00: error: { UNC }
Jun 8 17:04:44 localhost kernel: [ 216.538146] ata3.00: configured for UDMA/133
Jun 8 17:04:44 localhost kernel: [ 216.538160] ata3: EH complete
Jun 8 17:04:47 localhost kernel: [ 219.073696] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 8 17:04:47 localhost kernel: [ 219.073701] ata3.00: BMDMA stat 0x24
Jun 8 17:04:47 localhost kernel: [ 219.073705] ata3.00: failed command: READ DMA
Jun 8 17:04:47 localhost kernel: [ 219.073714] ata3.00: cmd c8/00:08:40:10:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 8 17:04:47 localhost kernel: [ 219.073716] res 51/40:00:40:10:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 8 17:04:47 localhost kernel: [ 219.073720] ata3.00: status: { DRDY ERR }
Jun 8 17:04:47 localhost kernel: [ 219.073723] ata3.00: error: { UNC }
Jun 8 17:04:52 localhost kernel: [ 224.093967] ata3.00: qc timeout (cmd 0x27)
Jun 8 17:04:52 localhost kernel: [ 224.093972] ata3.00: failed to read native max address (err_mask=0x4)
Jun 8 17:04:52 localhost kernel: [ 224.093976] ata3.00: HPA support seems broken, skipping HPA handling
Jun 8 17:04:52 localhost kernel: [ 224.093980] ata3.00: revalidation failed (errno=-5)
Jun 8 17:04:52 localhost kernel: [ 224.093989] ata3: hard resetting link
Jun 8 17:04:52 localhost kernel: [ 224.567030] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 8 17:04:52 localhost kernel: [ 224.587154] ata3.00: configured for UDMA/133
Jun 8 17:04:52 localhost kernel: [ 224.587174] sd 2:0:0:0: [sde] Unhandled sense code
Jun 8 17:04:52 localhost kernel: [ 224.587177] sd 2:0:0:0: [sde] Result: hostbyte=0x00 driverbyte=0x08
Jun 8 17:04:52 localhost kernel: [ 224.587182] sd 2:0:0:0: [sde] Sense Key : 0x3 [current] [descriptor]
Jun 8 17:04:52 localhost kernel: [ 224.587187] Descriptor sense data with sense descriptors (in hex):
Jun 8 17:04:52 localhost kernel: [ 224.587190] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Jun 8 17:04:52 localhost kernel: [ 224.587202] 00 00 10 40
Jun 8 17:04:52 localhost kernel: [ 224.587207] sd 2:0:0:0: [sde] ASC=0x11 ASCQ=0x4
Jun 8 17:04:52 localhost kernel: [ 224.587212] sd 2:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 00 10 40 00 00 08 00
Jun 8 17:04:52 localhost kernel: [ 224.587223] end_request: I/O error, dev sde, sector 4160
Jun 8 17:04:52 localhost kernel: [ 224.587228] Buffer I/O error on device sde1, logical block 512
I have tried using SMART to test the drives, however all the drives seem to fail with some sort of error. I believe this is a false positive as I have read elsewhere that the 1TB Green Western Digitals (WD10EARS) seem to have problems with SMART.
Is this drive dead? Its only a year old... and unfortunately just out of warranty.
Last edited by passbe (2011-06-24 08:52:16)

Ok so i zero filled /dev/sde, and re-added it back to the array. It synced (for 2 days), and then my RAID5 completely failed. I can't bring it back up at all now. My BIOS says one of the hard drives is dead (SMART error). Fair enough drive is dead. But now i cant get the 3 drives back up and running in the RAID.
I have attempted the following:
sudo mdadm --assemble -vv /dev/md127 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: looking for devices for /dev/md127
mdadm: cannot open device /dev/sdb1: Device or resource busy
mdadm: /dev/sdb1 has no superblock - assembly aborted
It complains that every device does not have a superblock?
A mdadm --examine on each drive:
/dev/sdb1
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e3da6078:d4699e2d:c1da42cc:d58a42bf
Name : myhost:0
Creation Time : Sun Feb 27 09:27:39 2011
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953517954 (931.51 GiB 1000.20 GB)
Array Size : 5860552704 (2794.53 GiB 3000.60 GB)
Used Dev Size : 1953517568 (931.51 GiB 1000.20 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 95618add:2d0b86be:d06cc198:1a5e101f
Update Time : Tue Jun 14 20:44:51 2011
Checksum : 51b4a80f - correct
Events : 4808
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 0
Array State : A.A. ('A' == active, '.' == missing)
/dev/sdc1
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e3da6078:d4699e2d:c1da42cc:d58a42bf
Name : myhost:0
Creation Time : Sun Feb 27 09:27:39 2011
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953517954 (931.51 GiB 1000.20 GB)
Array Size : 5860552704 (2794.53 GiB 3000.60 GB)
Used Dev Size : 1953517568 (931.51 GiB 1000.20 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 3056502e:51e004d0:4380f027:fe2d9ebc
Update Time : Tue Jun 14 20:44:51 2011
Checksum : e0b65526 - correct
Events : 4808
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 2
Array State : A.A. ('A' == active, '.' == missing)
/dev/sdd1
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e3da6078:d4699e2d:c1da42cc:d58a42bf
Name : myhost:0
Creation Time : Sun Feb 27 09:27:39 2011
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953517954 (931.51 GiB 1000.20 GB)
Array Size : 5860552704 (2794.53 GiB 3000.60 GB)
Used Dev Size : 1953517568 (931.51 GiB 1000.20 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 3b7ea2c8:9fd80575:94fbe3a0:cde69026
Update Time : Tue Jun 14 20:34:16 2011
Checksum : 2f1a716 - correct
Events : 4791
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 1
Array State : AAAA ('A' == active, '.' == missing)
/dev/sde1 (This is the bad drive)
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e3da6078:d4699e2d:c1da42cc:d58a42bf
Name : myhost:0
Creation Time : Sun Feb 27 09:27:39 2011
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953523057 (931.51 GiB 1000.20 GB)
Array Size : 5860552704 (2794.53 GiB 3000.60 GB)
Used Dev Size : 1953517568 (931.51 GiB 1000.20 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : bad3c5fd:3e439065:957ca15a:412339dc
Update Time : Tue Jun 14 20:44:51 2011
Checksum : 98033b24 - correct
Events : 4808
Layout : left-symmetric
Chunk Size : 512K
Device Role : spare
Array State : A.A. ('A' == active, '.' == missing)
The only difference being that /dev/sdd1 thinks that the RAID has all four devices? Where do i go from here, I'm completely stuck and about to loose 50% of my data. Help!?!

[Solved]Adding a hard drive problem?!?

OK folks, I feel stupid asking this question but each time I try to add a hard drive to my arch server, I get the following error at boot up any advice:
attempting to create root device /dev/sda3
/bin/mknod "/dev/root" b 8 3
/init: 1: cannot open /dev/root: No Such Device or address
:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
kinit: Unable to mount root fs on device dev(8,3)
kinit: init not found!
kernel panic - not synching: Attempted to kill init!
The device I'm adding is a 200gb hard drive PATA drive, the current system is on a SATA drive. There are no other drives on the PATA chain. Any advice? I'm thinking maybe grub is calling it?!?!
Last edited by ybotspawn (2008-07-15 23:16:34)

ybotspawn wrote:
OK folks, I feel stupid asking this question but each time I try to add a hard drive to my arch server, I get the following error at boot up any advice:
attempting to create root device /dev/sda3
/bin/mknod "/dev/root" b 8 3
/init: 1: cannot open /dev/root: No Such Device or address
:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
kinit: Unable to mount root fs on device dev(8,3)
kinit: init not found!
kernel panic - not synching: Attempted to kill init!
The device I'm adding is a 200gb hard drive PATA drive, the current system is on a SATA drive. There are no other drives on the PATA chain. Any advice? I'm thinking maybe grub is calling it?!?!
Try labeling your partitions from a live cd, and use /dev/disk/by-label or some other form of persistent device naming. Sounds like typical linux kernel drive controller issues.
http://wiki.archlinux.org/index.php/Per … ice_naming

[SOLVED] Shredding a Hard Drive

I recently used the shred command on a hard drive like so,
shred -vfz /dev/sda
The whole process took several hours so I assumed it went well, but then afterwards when I looked into the drive with cfdisk I noticed that the partitions were still there. Does that make sense? Or does that mean that shred didn't actually work?
Last edited by tony5429 (2010-12-12 01:52:42)

man hdparm
--security-erase PWD
Erase (locked) drive, using password PWD (DANGEROUS). Password is given as an ASCII string and is padded with NULs to reach 32 bytes. Use the special password
NULL to represent an empty password. The applicable drive password is selected with the --user-master switch (default is "user" password). No other options
are permitted on the command line with this one.
--security-erase-enhanced PWD
Enhanced erase (locked) drive, using password PWD (DANGEROUS). Password is given as an ASCII string and is padded with NULs to reach 32 bytes. The applicable
drive password is selected with the --user-master switch (default is "user" password). No other options are permitted on the command line with this one.
You can use the parted magic boot cd for example. It has a GUI for this erasing method and it's pretty fast :-)

How to Solve Problem Restoring Hard Drive on Disk Utility?

Hi everyone, my hard drive recently crashed. I got a new one placed in my computer, and I'm trying to recover data off of the one that crashed and transfer it onto my existing hard drive (which is larger in capacity than the one that crashed). I got this crashed hard drive tested, and the data is still intact; I was told that it will be possible to recovery data off of it. I bought an enclosure to place my crashed hard drive in, and I connected it to my MacBook Pro using a USB cable. Disk Utility then automatically opened. Upon going to the restore window in Disk Utility, I'm unable to drag down the name of the crashed hard drive into the source window, nor my existing hard drive into the destination window. No error message comes up; Disk Utility simply won't let me drag the names of these drives into these respective fields. Does anyone know how I can get Disk Utility to let me drag each respective drive into the source and destination fields? Thanks.

I don't know if Disk Utility is going to be of much help - you may want to try rescuing your data using Data Rescue 3 or some other data recovery application. I've tested Data Rescue 3 and found that I had excellent results.
Good luck,
Clinton

Satellite 17xx Series Hard Drive Replacement

Will someone please advise how to get into the hard drive on one of these machines . Do you have to lift the keyboard if so how. I have taken all the screwa out the bottom of the case and am getting nowhere fast.
George

This is quite well illustrated though it's not for your model.
http://forums.computers.toshiba-europe.com/forums/thread.jspa?threadID=5640&messageID=19319#19319
If you do a search on this (all) forums for HDD or hard disc or a related word you should come up with quite a few references.
Regards,

[SOLVED] (hopefully) USB Hard drive disconnects

I have a 2TB SATA drive which I used in a stationary computer (as a server). The drive is encrypted using LUKS and for a filesystem I use xfs. Unfortunately that computer died, so I figured I'd migrate everything over to a laptop instead. I put the 2TB SATA drive in an USB drive adapter, and it worked as it expected.
Until a few hours after when I suddenly couldn't use the drive any longer. It always happens after I haven't used the drive in a little while.
dmesg shows the following relevant information:
[ 81.300065] usb 1-2: new high speed USB device number 2 using ehci_hcd
[ 81.516917] usbcore: registered new interface driver uas
[ 81.538799] Initializing USB Mass Storage driver...
[ 81.538966] scsi2 : usb-storage 1-2:1.0
[ 81.539424] usbcore: registered new interface driver usb-storage
[ 81.539429] USB Mass Storage support registered.
[ 82.548407] scsi 2:0:0:0: Direct-Access WDC WD20 EARS-00J2GB0 PQ
: 0 ANSI: 2
[ 82.551630] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 82.552000] sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.
81 TiB)
[ 82.554255] sd 2:0:0:0: [sdb] Write Protect is off
[ 82.554262] sd 2:0:0:0: [sdb] Mode Sense: 38 00 00 00
[ 82.554266] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 82.557630] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 82.593632] sdb: unknown partition table
[ 82.597254] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 82.597262] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 104.697278] XFS (dm-1): Mounting Filesystem
[ 105.023577] XFS (dm-1): Ending clean mount
[ 4249.281149] usb 1-2: USB disconnect, device number 2
[ 4440.332930] INFO: task khubd:370 blocked for more than 120 seconds.
[ 4440.332935] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4440.332939] khubd D 00000000 0 370 2 0x00000000
[ 4440.332947] dea97d74 00000046 c1030357 00000000 00000001 00000003 5d6764c7 000003dd
[ 4440.332956] 00000096 ddd02180 dea97d04 c10303a4 00000000 00000096 dea97d18 c1527480
[ 4440.332965] ddc84c38 c1527480 dec06480 de38f8e0 de2a0d20 00000000 00024592 00000000
[ 4440.332974] Call Trace:
[ 4440.332987] [<c1030357>] ? __wake_up_common+0x47/0x70
[ 4440.332993] [<c10303a4>] ? __wake_up_locked+0x24/0x30
[ 4440.332998] [<c10318ab>] ? cpuacct_charge+0x5b/0x70
[ 4440.333006] [<c11bd4b4>] ? rb_insert_color+0xc4/0x100
[ 4440.333014] [<c13487d5>] schedule_timeout+0x265/0x2e0
[ 4440.333022] [<c103f883>] ? check_preempt_wakeup+0x123/0x1b0
[ 4440.333028] [<c1036f72>] ? check_preempt_curr+0x72/0x90
[ 4440.333033] [<c1347527>] wait_for_common+0x97/0x120
[ 4440.333038] [<c10410a0>] ? try_to_wake_up+0x350/0x350
[ 4440.333043] [<c13475c7>] wait_for_completion+0x17/0x20
[ 4440.333048] [<c106390e>] kthread_stop+0x3e/0x130
[ 4440.333058] [<e00e6178>] release_everything+0x28/0xa0 [usb_storage]
[ 4440.333064] [<e00e620f>] usb_stor_disconnect+0x1f/0x30 [usb_storage]
[ 4440.333089] [<e0f9d64c>] usb_unbind_interface+0x3c/0x140 [usbcore]
[ 4440.333096] [<c1264271>] __device_release_driver+0x51/0xb0
[ 4440.333101] [<c12642f4>] device_release_driver+0x24/0x40
[ 4440.333106] [<c1263e6a>] bus_remove_device+0x5a/0x80
[ 4440.333110] [<c1261dc8>] device_del+0x108/0x170
[ 4440.333121] [<e0f9b691>] usb_disable_device+0x91/0x1a0 [usbcore]
[ 4440.333130] [<e0f94d1a>] usb_disconnect+0x9a/0x120 [usbcore]
[ 4440.333141] [<e0f967dc>] hub_thread+0x86c/0xf60 [usbcore]
[ 4440.333146] [<c1347a25>] ? schedule+0x275/0x9c0
[ 4440.333151] [<c1040efc>] ? try_to_wake_up+0x1ac/0x350
[ 4440.333157] [<c1063fa0>] ? abort_exclusive_wait+0x80/0x80
[ 4440.333161] [<c1031b4e>] ? complete+0x4e/0x60
[ 4440.333172] [<e0f95f70>] ? usb_remote_wakeup+0x40/0x40 [usbcore]
[ 4440.333176] [<c10638bd>] kthread+0x6d/0x80
[ 4440.333181] [<c1063850>] ? kthread_worker_fn+0x160/0x160
[ 4440.333187] [<c134b8be>] kernel_thread_helper+0x6/0x10
At first I figured the drive was suspending, so I've tried to play with the settings in /sys/bus/usb/devices/.../power/. To my knownledge the default settings are set to never suspend, and the dmesg doesn't say anything about suspending any drives (should it?), so I doubt this is the case. And also, I can still hear that the drive is on.
I have tried changing the USB cable but I got the same error.
So I figure, it's either a hardware problem (the USB drive adapter is bad) or it's the kernel -- I've read through some mailing lists that older kernels had some problems with USB devices disconnecting.
What I would like to try is to disable ehci_hcd and try to use a different module, though I need a little help with what module and how I would go about doing this. (I see in the lspci a reference to uhci, maybe try that?).
Anyone has any other ideas I can try that would also be greatly appreciated.
Thanks in advance.
lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
02:01.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller
02:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
02:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller Mobile (rev 03)
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 04fc:0c25 Sunplus Technology Co., Ltd SATALink SPIF225A
Last edited by Canute (2011-07-29 13:36:55)

I think I may have fixed it, or rather; it has worked the last 8 hours which is twice as long as the longest it did before.
Through ubuntu's bug tracker I found out that there appears to be a bug in the kernel (#32432). From what I read on the bugzilla, that bug appears to be only for 2.6.27-2.6.38 (is it??) and I was using 2.6.39 so I was really unsure if that bug applied to my kernel.
Nevertheless I built my own kernel with the help of abs. I used linux version 2.6.38, the standard arch linux patch for 2.6.38 and the patch located here.

Upgrade Options for Internal Hard Drive on dv2000t Laptop (Installation Problems)

I need to replace a failed hard drive in my 2006 dv2000t laptop. The drive I'm replacing was already a replacement drive from the original 80GB drive that shipped with laptop. That first replacement 3 years ago (2008) was a 200GB drive, that worked well for about 3 years. But it just crashed (apparently). I was getting some "S.M.A.R.T" imminent drive failure warnings a week prior, and then it finally would no longer boot-up. Subsequent tests on the extracted drive show it as having many failed sectors.
I had no problem ordering a replacement drive the first time in 2008, restoring an Acronis backup image of original drive, installing it, etc. All went smoothly in 2008. So I assumed all would go smoothly again for yet another replacement and upgrade.
In 2008 the drive I ordered was a W.D. (Western Digital, sticking with the same brand as original) 2.5-in 5400rpm SATA drive (200GB). That was a SATA (I) drive (1.5 Gbit/s interface).
The first drive I recently ordered (Mar 2011) was a W.D 2.5-in 7200rpm 500GB SATA II (3.0 Gbits/s interface) drive (from W.D.'s "Scorpio Black" line.) Got the drive, burned the disc image to it, and popped it into the laptop. Unfortunately, upon startup, and after BIOS screen, all I get is a black screen with a fast flashing white cursor at the top of the screen. Drive apparently is not being recognized by the computer? Then I did some reading in a few on-line forums and found some references about this laptop not doing well with drive capacities over 320GB, nor with 7200rpm drives (because they run hotter than 5400 drives). And finally, references to the SATA interface speed. I ordered a 2nd drive, this one from W.D's "Scorpio Blue" line, this time a 5400rpm 320GB drive (but still SATA II). Same story, still won't work. So I decided that maybe the issue was the SATA speed. So I found someone who still had an older SATA (1.5 GBit/s) W.D. drive in stock . It's a W.D. SATA 250GB (no longer made). It should arrive in a couple days -- and I'm hoping this one works!
I would like to get some kind of confirmation about the blinking white cursor on the black screen on start-up. Is that typicalif the system not finding a bootable hard drive? Also, is this SATA vs. SATA-II issue a likely cause of my problem? I'm pretty sure there's nothing wrong with the new drives themselves, and the restored images on them , as the drives will mount and are accessible when I plug them in as external drives on my other computer.
This question was solved.
View Solution.

I have been able to solve my own hard drive installation problems. It turns out that there were no issues with any of the new replacement drive(s) I ordered (thinking I had ordered drives with the wrong specs). The solution to the problem was a simple one. The restored drives were not booting because there was no MBR (Master Boot Record) on the drives after disc image restoration.
I am using Acronis True Image Home 2011 as my disc imaging (backup) software. And I just didn't understand how to properly restore backed up images to a new hard drive. I had done everything correctly except that I had not checked the box to "restore MBR" -- at the time not understanding what that was or its significance. Once I checked that box, and reimaged the new drive, it worked fine.

Trying to Bootcamp, Hard Drive Won't Partition

Hello there,
I am trying to use the bootcamp assistant utility to install windows 7 on a Late 2009 iMac. I got the Microsoft support software downloaded to an external Flash Drive using the Bootcamp utility and have a full Windows 7 Home Premium install disc that I have been trying to use, brand new bought yesterday. The problem is that I can't seem to get past the point in the Bootcamp utility where it makes the partitions for me. I receive this message:
"you disk cannot be partitioned. an error occurred while partitioning the disk."
I tried using the disk utility (as suggested online) to look at the hard drive and received this message due to an "invalid directory count":
"this disk needs to be repaired using the Recovery HD. Restart your computer, holing down the command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk utility."
I've done that but for some reason the Disk Utility there says that everything is okay after being checked and verified. I even chose the repair option to no avail.
I then went back online and was routed to trying to reboot my iMac using the Single-User Mode (command S at reboot). I used the command line:
"/sbin/fsck -fy" (no quotes) [enter]
the system ran the command; it checks and repairs inconsistencies in file systems that may prevent you from partitioning the drive. the result was
"**the volume macintosh HD could not be repaired.****the volume was modified.****"
i can post a pic of the set of command lines and results if needed, but the hard drive has never been modified. I need help figuring out how to solve this partitioning/hard drive issue.
Thanks

well I believe it always starts in safe mode; i'm not sure but it always starts up with the progress bar loading.
my situation has changed, I tried repeating my steps as aforementioned and have gotten the partitioning process to work but now upon startup the screen is black and says there is no bootable device, I can access my apple side of the machine restarting and using the "option" key and see that it is the only bootable drive. I think the reason for this is because I'm trying to boot Windows 7 using an external superdrive as the disk drive inside the iMac itself is unable to work. I don't know for sure if this is an appropriate solution, but I was wondering if there is a way to get the iMac to recognize the external usb superdrive as its internal optical drive.

Software based hard drive tests?

Is there a software based hard drive tester out there? I have no idea how to test my now 7 year old hard drive on my MDD,just wondering if there are software based solutions as well as hardware,and where to get them,thanks!

Excellent,thank you,just one more question,can the power supply be tested the same way,with software?Or am I stuck using a power supply tester,which I dont currently have(a link to a decent one would be nice,if I cant do this with software,that is).Again thanks for this,as I totally forgot which ones were the best :)Oh,and BTW,japamac,I just joined the Quicksilver club(if one exists )and found your blog an excellent resource for deciding on which one to get,as well as which upgrade parts to use.Recieving one this week,with an Radion 9800Pro card.Alraedy have a Firmtec card and am using a 1TB Hitachi jupiter series hard drive.The Quicksilver is a DP 800,and I'm running Leopard.I for one just want to take this time to thank you for all the help you have been to me and everyone who loves their Power PC G4's!!

Solved - D Series Hard Drive Tray interchang​e

Similar Messages

Maybe you are looking for

Solved - D Series Hard Drive Tray interchange