[nflug] Help needed Initializing a new notebook disk drive
Cyber Source
peter at thecybersource.com
Wed Dec 31 16:38:09 EST 2008
whats in your fstab file? what are the chances that your dvd/cd is
actually sdc and it's not seeing the new drive at all?
Joe wrote:
> Here's the output for dmesg and fdisk. dmesg shows how it handles my
> internal drive (sda) and my FreeAgent USB drive (sdb2) (bought it before
> the article about Seagate dropping support for Linux). The last two
> lines show it sees sdc, but fdisk isn't having any.
>
> Do you know if a 1.5 MB/sec controller can handle a 3MB/sec drive?
>
> Thanks for looking into this further.
>
> Joe
>
> bigbird at sananda:~$ sudo fdisk /dev/sdc
>
> Unable to read /dev/sdc
> bigbird at sananda:~$
> bigbird at sananda:~$ dmesg | grep sd
> [ 31.978128] Driver 'sd' needs updating - please use bus_type methods
> [ 31.981229] sd 1:0:0:0: [sda] 234441648 512-byte hardware sectors
> (120034 MB)
> [ 31.981257] sd 1:0:0:0: [sda] Write Protect is off
> [ 31.981263] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 31.981300] sd 1:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 31.981400] sd 1:0:0:0: [sda] 234441648 512-byte hardware sectors
> (120034 MB)
> [ 31.981424] sd 1:0:0:0: [sda] Write Protect is off
> [ 31.981429] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 31.981467] sd 1:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 31.981474] sda: sda1 sda2 sda3 < sda5 > sda4
> [ 32.027345] sd 1:0:0:0: [sda] Attached SCSI disk
> [ 32.036425] sd 1:0:0:0: Attached scsi generic sg0 type 0
> [ 34.959860] sd 0:0:0:0: [sdb] 488397168 512-byte hardware sectors
> (250059 MB)
> [ 34.961470] sd 0:0:0:0: [sdb] Write Protect is off
> [ 34.961479] sd 0:0:0:0: [sdb] Mode Sense: 1c 00 00 00
> [ 34.961485] sd 0:0:0:0: [sdb] Assuming drive cache: write through
> [ 34.963859] sd 0:0:0:0: [sdb] 488397168 512-byte hardware sectors
> (250059 MB)
> [ 34.965465] sd 0:0:0:0: [sdb] Write Protect is off
> [ 34.965474] sd 0:0:0:0: [sdb] Mode Sense: 1c 00 00 00
> [ 34.965479] sd 0:0:0:0: [sdb] Assuming drive cache: write through
> [ 34.965491] sdb: sdb1 sdb2
> [ 34.991407] sd 0:0:0:0: [sdb] Attached SCSI disk
> [ 34.991485] sd 0:0:0:0: Attached scsi generic sg2 type 0
> [ 53.533600] sdhci: Secure Digital Host Controller Interface driver
> [ 53.533608] sdhci: Copyright(c) Pierre Ossman
> [ 57.853803] sdhci: SDHCI controller found at 0000:08:06.3 [104c:803c]
> (rev 0)
> [ 58.885622] Adding 1767076k swap on /dev/sda5. Priority:-1 extents:1
> across:1767076k
> [ 59.407078] EXT3 FS on sda4, internal journal
> [ 60.965326] EXT3 FS on sda2, internal journal
> [ 65.379312] audit(1230746295.196:2): type=1503
> operation="inode_permission" requested_mask="a::" denied_mask="a::"
> name="/dev/tty" pid=5709 profile="/usr/sbin/cupsd" namespace="default"
> [ 159.538730] EXT3 FS on sdb2, internal journal
> [ 3994.249820] sd 7:0:0:0: [sdc] Attached SCSI disk
> [ 3994.249909] sd 7:0:0:0: Attached scsi generic sg3 type 0
> bigbird at sananda:~$
>
> Cyber Source wrote:
>
>> what does "dmesg|grep sd" return?
>>
>> Joe wrote:
>>
>>> Thanks for the quick reply.
>>>
>>> I did it and the drive shows up as /dev/sdc now (my other usb drive is
>>> plugged in and is /dev/sdb).
>>> *But* fdisk doesn't seem to see the new drive (see below).
>>>
>>> What now?
>>>
>>> Joe
>>>
>>> bigbird at sananda:~/pq$ ls /dev/sd*
>>> /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/sda5
>>> /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdc
>>> bigbird at sananda:~/pq$ fdisk -l
>>> bigbird at sananda:~/pq$ sudo !!
>>> sudo fdisk -l
>>> [sudo] password for bigbird:
>>>
>>> Disk /dev/sda: 120.0 GB, 120034123776 bytes
>>> 255 heads, 63 sectors/track, 14593 cylinders
>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>> Disk identifier: 0x1ea71ea6
>>>
>>> Device Boot Start End Blocks Id System
>>> /dev/sda1 * 1 5099 40957686 7 HPFS/NTFS
>>> /dev/sda2 5100 8986 31222327+ 83 Linux
>>> /dev/sda3 14000 14219 1767150 5 Extended
>>> /dev/sda4 8987 13999 40266922+ 83 Linux
>>> /dev/sda5 14000 14219 1767087 82 Linux swap /
>>> Solaris
>>>
>>> Partition table entries are not in disk order
>>>
>>> Disk /dev/sdb: 250.0 GB, 250059350016 bytes
>>> 255 heads, 63 sectors/track, 30401 cylinders
>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>> Disk identifier: 0x000979ea
>>>
>>> Device Boot Start End Blocks Id System
>>> /dev/sdb1 1 6384 51279448+ 7 HPFS/NTFS
>>> /dev/sdb2 6385 30401 192916552+ 83 Linux
>>> bigbird at sananda:~/pq$
>>>
>>>
>>> Cyber Source wrote:
>>>
>>>
>>>> The gparted cd probably does not have the usb storage module loaded.
>>>> Boot the laptop with kbuntu, then plug it in. as root, type "fdisk
>>>> -l", if it sees the drive, there's nothing wrong.
>>>>
>>>> Joe wrote:
>>>>
>>>>
>>>>> I just got a new drive for my notebook. The old drive still works,
>>>>> but
>>>>> has some bad spots on it (that are out of the way for now).
>>>>>
>>>>> The notebook is an HP dv5020us Centrino Duo. It is dual boot kubuntu
>>>>> hardy and Win XP.
>>>>>
>>>>> The new HD is Hitachi HTS543232L9A300 5400rpm SATA 320GB 3GB/s drive.
>>>>> I thought I ordered a 1.5 GB/s drive, but that's not what the label on
>>>>> the drive says.
>>>>> My old (current) drive (/dev/sda) is a 120GB 1.5GB/s drive
>>>>> (ST9120821AS)
>>>>> ATA-5 4200rpm and my controller is probably a 1.5GB/s controller.
>>>>>
>>>>> Is that enough to make the new drive incompatible with my system?
>>>>>
>>>>> I hooked up the drive to my notebook using a Vantec SATA/IDE to USB
>>>>> 2.0
>>>>> adapter.
>>>>>
>>>>> When I plug it into the usb port, nothing seems to happen, but when I
>>>>> look, I see that /dev/sdb appears when the drive is plugged in. the
>>>>> drive is very quiet, but I can hear it spinning when I put it next
>>>>> to my
>>>>> ear.
>>>>>
>>>>> I rebooted the notebook from my gparted live CD.
>>>>> I expected gparted to be able to see and setup the new drive, but it
>>>>> does not see it at all.
>>>>>
>>>>> I thought about swapping the new and old drive in the notebook and
>>>>> then
>>>>> booting from gparted again, but since gparted can see and work with my
>>>>> other usb drive (currently unplugged), I'm not sure if that will help.
>>>>>
>>>>> What do I do next?
>>>>>
>>>>> I have a blinking rebate to send in right away, so I need to determine
>>>>> if the drive will work asap.
>>>>> _______________________________________________
>>>>> nflug mailing list
>>>>> nflug at nflug.org
>>>>> http://www.nflug.org/mailman/listinfo/nflug
>>>>>
>>>>>
>>>> _______________________________________________
>>>> nflug mailing list
>>>> nflug at nflug.org
>>>> http://www.nflug.org/mailman/listinfo/nflug
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> nflug mailing list
>>> nflug at nflug.org
>>> http://www.nflug.org/mailman/listinfo/nflug
>>>
>>>
>> _______________________________________________
>> nflug mailing list
>> nflug at nflug.org
>> http://www.nflug.org/mailman/listinfo/nflug
>>
>>
>
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug
>
More information about the nflug
mailing list