[opensuse-factory] kernel-default-3.6.10-15.1.i586 : cannot see HDD SDA
Hello List Tumbleweed : kernel-default-3.6.10-15.1.i586 __________ my system is on /dev/sdb which is 1 TB SATA HDD - i have a /dev/sda for backups, which is 360 GB PATA HDD .............. kernel-default-3.6.10-15.1.i586 does not allow me to mount /dev/sda kernel 3.4.6-2.10-desktop DOES allow mounting of /dev/sda & sees /dev/sda OK ................. - with kernel-default-3.6.10-15.1.i586 i get : command : _______ # mount /dev/sda4 /mnt mount: special device /dev/sda4 does not exist .................... [ because do not feel sufficiently 'advanced' to wrestle with bugzilla reports, since kernel 3.4.6-2.10 i have been hoping this trouble would be solved and 'go away', but, no such luck ] best regards Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-12-16 09:45 (GMT+0200) ellanios82 composed:
Tumbleweed : kernel-default-3.6.10-15.1.i586
my system is on /dev/sdb which is 1 TB SATA HDD
- i have a /dev/sda for backups, which is 360 GB PATA HDD
kernel-default-3.6.10-15.1.i586 does not allow me to mount /dev/sda
kernel 3.4.6-2.10-desktop DOES allow mounting of /dev/sda & sees /dev/sda OK
- with kernel-default-3.6.10-15.1.i586 i get :
command :
# mount /dev/sda4 /mnt mount: special device /dev/sda4 does not exist
[ because do not feel sufficiently 'advanced' to wrestle with bugzilla reports, since kernel 3.4.6-2.10 i have been hoping this trouble would be solved and 'go away', but, no such luck ]
Are you sure the newer kernel didn't change device names? Booted to newer kernel, what is output from: 'fdisk -l'? 'lspci | grep IDE'? lsscsi? llsusb? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/16/12 14:54, Felix Miata wrote:
On 2012-12-16 09:45 (GMT+0200) ellanios82 composed:
Tumbleweed : kernel-default-3.6.10-15.1.i586
my system is on /dev/sdb which is 1 TB SATA HDD
- i have a /dev/sda for backups, which is 360 GB PATA HDD
kernel-default-3.6.10-15.1.i586 does not allow me to mount /dev/sda
kernel 3.4.6-2.10-desktop DOES allow mounting of /dev/sda & sees /dev/sda OK
- with kernel-default-3.6.10-15.1.i586 i get :
command :
# mount /dev/sda4 /mnt mount: special device /dev/sda4 does not exist
[ because do not feel sufficiently 'advanced' to wrestle with bugzilla reports, since kernel 3.4.6-2.10 i have been hoping this trouble would be solved and 'go away', but, no such luck ]
Are you sure the newer kernel didn't change device names? Booted to newer kernel, what is output from:
'fdisk -l'? 'lspci | grep IDE'? lsscsi? llsusb? ................ # lsusb Bus 001 Device 002: ID 152e:2507 LG (HLDS) PL-2507 IDE Controller Bus 004 Device 002: ID 04b4:0033 Cypress Semiconductor Corp. Mouse 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 ...............
fdisk -l Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000bf499 Device Boot Start End Blocks Id System /dev/sda1 * 63 146802032 73400985 83 Linux /dev/sda2 146802033 461370735 157284351+ 83 Linux /dev/sda3 461370736 471861180 5245222+ 82 Linux swap / Solaris /dev/sda4 * 471861181 625137344 76638082 83 Linux Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000265f2 Device Boot Start End Blocks Id System /dev/sdb1 * 63 585938744 292969341 83 Linux /dev/sdb2 585938745 1171877489 292969372+ 83 Linux /dev/sdb3 1171877490 1181645009 4883760 82 Linux swap / Solaris /dev/sdb4 * 1181645010 1767583754 292969372+ 83 Linux .............................. # lspci | grep IDE 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA Controller [IDE mode] (rev 01) .................... # lsscsi [0:0:1:0] disk ATA ST3320620A 3.AA /dev/sda [2:0:1:0] disk ATA WDC WD10EAVS-00M 01.0 /dev/sdb [3:0:1:0] cd/dvd Optiarc DVD RW AD-5260S 1.00 /dev/sr0 [4:0:0:0] cd/dvd HL-DT-ST DVD-RAM GSA-E60N 1.00 /dev/sr1 ..................... # uname -a Linux AIG 3.6.10-15-default #1 SMP Mon Dec 10 22:29:57 UTC 2012 (fd6ec90) i686 i686 i386 GNU/Linux ............................ .............. # mount /dev/sda1 /mnt mount: special device /dev/sda1 does not exist .............. ............... thank you so much best regards Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Dec 16, 2012 at 5:50 PM, ellanios82
fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000bf499
Device Boot Start End Blocks Id System /dev/sda1 * 63 146802032 73400985 83 Linux [...] # mount /dev/sda1 /mnt mount: special device /dev/sda1 does not exist
And "ls -l /dev/sda*"? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-12-16 15:50 (GMT+0200) ellanios82 composed:
On 12/16/12 14:54, Felix Miata wrote:
On 2012-12-16 09:45 (GMT+0200) ellanios82 composed:
Tumbleweed : kernel-default-3.6.10-15.1.i586
my system is on /dev/sdb which is 1 TB SATA HDD
- i have a /dev/sda for backups, which is 360 GB PATA HDD
kernel-default-3.6.10-15.1.i586 does not allow me to mount /dev/sda
kernel 3.4.6-2.10-desktop DOES allow mounting of /dev/sda & sees /dev/sda OK
- with kernel-default-3.6.10-15.1.i586 i get :
command :
# mount /dev/sda4 /mnt mount: special device /dev/sda4 does not exist
[ because do not feel sufficiently 'advanced' to wrestle with bugzilla reports, since kernel 3.4.6-2.10 i have been hoping this trouble would be solved and 'go away', but, no such luck ]
Are you sure the newer kernel didn't change device names? Booted to newer kernel, what is output from:
'fdisk -l'? 'lspci | grep IDE'? lsscsi? llsusb?
# lsusb Bus 001 Device 002: ID 152e:2507 LG (HLDS) PL-2507 IDE Controller
Is this the controller sda is connected to? None of my Intel ICH7 systems have this.
Bus 004 Device 002: ID 04b4:0033 Cypress Semiconductor Corp. Mouse 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
fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes Disk identifier: 0x000bf499
Device Boot Start End Blocks Id System /dev/sda1 * 63 146802032 73400985 83 Linux /dev/sda2 146802033 461370735 157284351+ 83 Linux /dev/sda3 461370736 471861180 5245222+ 82 Linux swap / Solaris /dev/sda4 * 471861181 625137344 76638082 83 Linux
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes Disk identifier: 0x000265f2
Device Boot Start End Blocks Id System /dev/sdb1 * 63 585938744 292969341 83 Linux /dev/sdb2 585938745 1171877489 292969372+ 83 Linux /dev/sdb3 1171877490 1181645009 4883760 82 Linux swap / Solaris /dev/sdb4 * 1181645010 1767583754 292969372+ 83 Linux
# lspci | grep IDE 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA Controller [IDE mode] (rev 01)
# lsscsi [0:0:1:0] disk ATA ST3320620A 3.AA /dev/sda [2:0:1:0] disk ATA WDC WD10EAVS-00M 01.0 /dev/sdb [3:0:1:0] cd/dvd Optiarc DVD RW AD-5260S 1.00 /dev/sr0 [4:0:0:0] cd/dvd HL-DT-ST DVD-RAM GSA-E60N 1.00 /dev/sr1
# uname -a Linux AIG 3.6.10-15-default #1 SMP Mon Dec 10 22:29:57 UTC 2012 (fd6ec90) i686 i686 i386 GNU/Linux
# mount /dev/sda1 /mnt mount: special device /dev/sda1 does not exist
This may be better switched to the opensuse-kernel list. First, see what happens if you add on kernel cmdline (but don't change menu.lst/grub.cfg, just do it interactively, one per boot): modprobe.blacklist=hpsa modprobe.blacklist=cciss -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/16/2012 01:54 PM, Felix Miata wrote:
# mount /dev/sda4 /mnt mount: special device /dev/sda4 does not exist
[ because do not feel sufficiently 'advanced' to wrestle with bugzilla reports, since kernel 3.4.6-2.10 i have been hoping this trouble would be solved and 'go away', but, no such luck ]
Are you sure the newer kernel didn't change device names? Booted to newer kernel, what is output from:
Guys, the error is that the kernel cannot read partition table on his system (I got this from him some time ago): [ 1.844645] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6^M [ 1.844784] ata1.01: BMDMA stat 0x44^M [ 1.844858] ata1.01: failed command: READ DMA^M [ 1.844942] ata1.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 dma 4096 in^M [ 1.844942] res 51/84:00:00:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)^M [ 1.845230] ata1.01: status: { DRDY ERR }^M [ 1.845305] ata1.01: error: { ICRC ABRT }^M [ 1.845403] ata1: soft resetting link^M [ 2.128603] ata1.01: configured for UDMA/33^M [ 2.128610] sd 0:0:1:0: [sda] ^M [ 2.128612] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE^M [ 2.128614] sd 0:0:1:0: [sda] ^M [ 0.907216] ACPI: Invalid Power Resource to register!^M [ 2.128616] Sense Key : Aborted Command [current] [descriptor]^M [ 2.128619] Descriptor sense data with sense descriptors (in hex):^M [ 2.128621] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 ^M [ 2.128631] 00 00 00 00 ^M [ 2.128635] sd 0:0:1:0: [sda] ^M [ 2.128638] Add. Sense: Scsi parity error^M [ 2.128641] sd 0:0:1:0: [sda] CDB: ^M [ 2.128642] Read(10): 28 00 00 00 00 00 00 00 08 00^M [ 2.128651] end_request: I/O error, dev sda, sector 0^M [ 2.128763] Buffer I/O error on device sda, logical block 0^M [ 2.128874] ata1: EH complete^M [ 3.068332] ata1.01: limiting speed to UDMA/25:PIO4^M [ 3.068335] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6^M [ 3.068471] ata1.01: BMDMA stat 0x44^M [ 3.068546] ata1.01: failed command: READ DMA^M [ 3.068629] ata1.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 dma 4096 in^M [ 3.068629] res 51/84:00:00:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)^M [ 3.068904] ata1.01: status: { DRDY ERR }^M [ 3.068979] ata1.01: error: { ICRC ABRT }^M [ 3.069083] ata1: soft resetting link^M [ 3.352292] ata1.01: configured for UDMA/25^M [ 3.352298] sd 0:0:1:0: [sda] ^M [ 3.352300] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE^M [ 3.352302] sd 0:0:1:0: [sda] ^M [ 3.352303] Sense Key : Aborted Command [current] [descriptor]^M [ 3.352306] Descriptor sense data with sense descriptors (in hex):^M [ 3.352308] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 ^M [ 3.352317] 00 00 00 00 ^M [ 3.352322] sd 0:0:1:0: [sda] ^M [ 3.352324] Add. Sense: Scsi parity error^M [ 3.352327] sd 0:0:1:0: [sda] CDB: ^M [ 3.352328] Read(10): 28 00 00 00 00 00 00 00 08 00^M [ 3.352336] end_request: I/O error, dev sda, sector 0^M [ 3.352448] Buffer I/O error on device sda, logical block 0^M [ 3.352555] ata1: EH complete^M [ 3.400372] ldm_validate_partition_table(): Disk read failed.^M [ 3.400764] sda: unable to read partition table^M - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQ0EtjAAoJEL0lsQQGtHBJTQIQAJIiMpw+vB+AyoTjooKo1ZQw 22jCCQnYdEBqX/qwSyv/7r04hHpLvIbQkSx6tM4yZDNkgGHfUHhQP70aOOclyGc4 Ugrcx7m7Sio/nKTF8lG92jJ897QNhBCBPpnhAflJmawghn5cA1mWEui1r96GcXo/ tKzYVDvH9MWAKuCpEk2y9fe43MRidvCnwCNzbs3wzu+rscox188ZN3AKt6TDPo8i T1lISY/IRRSUnKZ/u5/Z4GcxnpUZIw7cc2XkBGNBuRPObrU9/WavrXUeEF4/6c+L PKFnx90xopSPhTGNhd6DhE/DuIRRnHu7Q94PYAfHcb5hAVuDM+gmgCFnJ23VjrTR 99dkQzIxKXng0bUf3W2Toi9zAutn5WwETqRzkvBy3bOMpOmUykE81BOxTpvkcDV1 tPWJGTgz3m8tSV20OeBacfuRUdYrMTIg8HKxYDgsnvOfQTVXOqgUhVkh8exZRHnS LMpIri3GFT/0B3Avh6N2dq0Jb47dL2Nyz2U6BYnT0a0au58Rsm1adGoG5baHslrS SfyLjqgXHlBjJUPAH4stXKJJ46SSmrzHfPqgo4A6RlzFx2MtvpNlrprFh6y2nVQ8 Ob0rp/28a63yUKt+taCJrpPK9CgHV1aWwqJU7ZIUplj0xDKu6gBeGTl+nMDem0JT NPvrhhk4IW7eySxcUs+C =FOKP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-12-18 05:54 (GMT-0500) Jiri Slaby composed:
On 12/16/2012 01:54 PM, Felix Miata wrote:
Are you sure the newer kernel didn't change device names? Booted to newer kernel, what is output from:
Guys, the error is that the kernel cannot read partition table on his system
What about: On 2012-12-16 09:45 (GMT+0200) ellanios82 composed:
- i have a /dev/sda for backups, which is 360 GB PATA HDD kernel-default-3.6.10-15.1.i586 does not allow me to mount /dev/sda kernel 3.4.6-2.10-desktop DOES allow mounting of /dev/sda & sees /dev/sda OK
Why does 12.2 kernel read it, but not newer kernel? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/18/12 15:56, Felix Miata wrote:
- i have a /dev/sda for backups, which is 360 GB PATA HDD kernel-default-3.6.10-15.1.i586 does not allow me to mount /dev/sda kernel 3.4.6-2.10-desktop DOES allow mounting of /dev/sda & sees /dev/sda OK
Why does 12.2 kernel read it, but not newer kernel? ..................
- May one not hope that this problem may be solved during the kernel-default-3.6.series ?? or, must ones hopes await the kernel-default-3.7.series ?? thanks best regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-12-18 16:04 (GMT+0200) ellanios82 composed:
Felix Miata wrote:
Why does 12.2 kernel read it, but not newer kernel?
- May one not hope that this problem may be solved during the kernel-default-3.6.series ??
or,
must ones hopes await the kernel-default-3.7.series ??
I already explained you don't need to wait to find out if 3.7 would help: http://lists.opensuse.org/opensuse-kernel/2012-12/msg00078.html -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
or,
must ones hopes await the kernel-default-3.7.series ??
I already explained you don't need to wait to find out if 3.7 would help: http://lists.opensuse.org/opensuse-kernel/2012-12/msg00078.html --
On 12/18/12 16:39, Felix Miata wrote: thank you . . . unhappily no good with kernel 3.7.0-3-default - still faced with message : # mount /dev/sda4 /mnt mount: special device /dev/sda4 does not exist .................. although fdisk -l does see : # fdisk -l Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000bf499 Device Boot Start End Blocks Id System /dev/sda1 * 63 146802032 73400985 83 Linux /dev/sda2 146802033 461370735 157284351+ 83 Linux /dev/sda3 461370736 471861180 5245222+ 82 Linux swap / Solaris /dev/sda4 * 471861181 625137344 76638082 83 Linux .............. kernel 3.7.0-3-default does not fix it thank you best regards Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 18 Dec 2012 17:06:42 +0200
ellanios82
Device Boot Start End Blocks Id System /dev/sda1 * 63 146802032 73400985 83 Linux /dev/sda2 146802033 461370735 157284351+ 83 Linux /dev/sda3 461370736 471861180 5245222+ 82 Linux swap /dev/sda4 * 471861181 625137344 76638082 83 Linux
Two devices marked as bootable? -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-12-18 18:35 (GMT-0600) Rajko composed:
On Tue, 18 Dec 2012 17:06:42 +0200 ellanios82 wrote:
Device Boot Start End Blocks Id System /dev/sda1 * 63 146802032 73400985 83 Linux /dev/sda2 146802033 461370735 157284351+ 83 Linux /dev/sda3 461370736 471861180 5245222+ 82 Linux swap /dev/sda4 * 471861181 625137344 76638082 83 Linux
Two devices marked as bootable?
Linux native partitioning tools often cause it. "Bootable" is irrelevant on Linux-only systems with Grub on MBR. DOS, OS/2 and WinDOS versions find more than one "bootable" primary per HD an obstacle to startup. Legacy MBR boot code doesn't handle more than one well either, but may not care as long as the first marked has the partition boot code that matters to the primary or sole boot manager/loader. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2012-12-18 a las 17:06 +0200, ellanios82 escribió:
thank you . . . unhappily no good with kernel 3.7.0-3-default
- still faced with message :
# mount /dev/sda4 /mnt mount: special device /dev/sda4 does not exist
..................
although fdisk -l does see :
# fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000bf499
Device Boot Start End Blocks Id System /dev/sda1 * 63 146802032 73400985 83 Linux /dev/sda2 146802033 461370735 157284351+ 83 Linux /dev/sda3 461370736 471861180 5245222+ 82 Linux swap / Solaris /dev/sda4 * 471861181 625137344 76638082 83 Linux
.............. kernel 3.7.0-3-default does not fix it
Does "file -s /dev/sda4" see it? - -- Cheers Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iF4EAREIAAYFAlDSFDYACgkQja8UbcUWM1zEfgD+ImtDbAwKeLza9WdgCAKxq5/j DoZuhKnzzyx+9KcfCaIA/1K/TjLa3kre/GtVulw3dm4RGoG3yjYfXBQcFR3tipkv =hcTy -----END PGP SIGNATURE-----
On 12/19/12 21:23, Carlos E. R. wrote:
Does "file -s /dev/sda4" see it?
................. - thank you Carlos booting kernel 3.7.0-3-default : the result of command # file -s /dev/sda4 is :- /dev/sda4: ERROR: cannot open `/dev/sda4' (No such file or directory) ............................. - my idea was that Linux was proud to be kind to older hardware . . . that After kernel 3.4 it is not possible to boot from a SATA HD while having an internal 40 wire ribbon-cable {i think 40 } PATA HD for back-up is no-longer possible, is, for me, a serious concern. Such a basic ability to mount a 40-wire PATA 2nd drive would seem important enough to be worth fixing fast. .............. best regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-12-20 11:03 (GMT+0200) ellanios82 composed:
/dev/sda4: ERROR: cannot open `/dev/sda4' (No such file or directory)
- my idea was that Linux was proud to be kind to older hardware . . . that After kernel 3.4 it is not possible to boot from a SATA HD while having an internal 40 wire ribbon-cable {i think 40 } PATA HD for back-up is no-longer possible, is, for me, a serious concern.
Such a basic ability to mount a 40-wire PATA 2nd drive would seem important enough to be worth fixing fast.
Finally you told us the cause. Any PATA device a 40 wire cable fits can have an 80 wire replace it, and if it's a HD made in the past 10+ years, should, as the 80 wire cable will not only be your solution, but will allow your PATA device to run at the full speed it is capable of. To continue to use 40 wire will handicap speed, and require a special cmdline parameter to force the maximum speed attempted by the driver down to a fraction of the device's maximum to prevent problems like yours. The UDMA5 spec requires 80 wire. You're lucky if your 3.4 kernel hasn't caused data corruption on your PATA HD while using a 40 wire cable. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/20/12 11:46, Felix Miata wrote:
The UDMA5 spec requires 80 wire. You're lucky if your 3.4 kernel hasn't caused data corruption on your PATA HD while using a 40 wire cable.
- thank you . . . my knowledge is limited :( - the Ribbon Cable that connects the Seagate hard disk, must now be replaced ?? - do i need to replace the 40-wire ribbon cable with a new 80-wire ribbon cable #hwinfo shows ribbon-connect hard-disk as : Device Files: /dev/sda, /dev/disk/by-id/ata-ST3320620A_9QF7G56W, /dev/disk/by-id/scsi-SATA_ST3320620A_9QF7G56W, /dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:1:0 .................. thank you -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-12-20 12:32 (GMT+0200) ellanios82 composed:
Felix Miata wrote:
The UDMA5 spec requires 80 wire. You're lucky if your 3.4 kernel hasn't caused data corruption on your PATA HD while using a 40 wire cable.
- thank you . . . my knowledge is limited :(
- the Ribbon Cable that connects the Seagate hard disk, must now be replaced ??
If indeed it is 40 wire, then you must either switch to 80 wire, or add a cmdline parameter to reduce the speed the driver attempts to use.
- do i need to replace the 40-wire ribbon cable with a new 80-wire ribbon cable
If indeed it is 40 wire, you need to switch it to 80 wire. It doesn't matter if "new" or not, they don't wear out. By now used 80 wire cables should be abundant. 40 wire cables look like http://upload.wikimedia.org/wikipedia/commons/thumb/a/a4/Nappe.svg/550px-Nap... and like MFM/RLL, floppy and 50 pin SCSI cables, with 40 individual wires readily counted by people with normal eyes. Usually their connectors are black, at least on the older ones. Moderate bends in them usually are not remembered. 80 wire cables have a smaller wire size that is difficult to count by average eyes. They also have blue and gray connectors instead of black. Bends are usually remembered unless very mild. Note that there are two types of each, regular, and cable select. Each HD must be jumpered according to which type is used. Cable select cables have one wire that is null, and often can be distinguished by a hole in it near one end. It may or may not have the words CS or cable select stenciled on it.
#hwinfo shows ribbon-connect hard-disk as :
Device Files: /dev/sda, /dev/disk/by-id/ata-ST3320620A_9QF7G56W, /dev/disk/by-id/scsi-SATA_ST3320620A_9QF7G56W, /dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:1:0
That would be much too new for optimal use with a 40 wire cable. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/20/2012 06:20 PM, Felix Miata wrote:
If indeed it is 40 wire, you need to switch it to 80 wire. It doesn't matter if "new" or not, they don't wear out. By now used 80 wire cables should be abundant.
40 wire cables look like http://upload.wikimedia.org/wikipedia/commons/thumb/a/a4/Nappe.svg/550px-Nap... and like MFM/RLL, floppy and 50 pin SCSI cables, with 40 individual wires readily counted by people with normal eyes. Usually their connectors are black, at least on the older ones. Moderate bends in them usually are not remembered.
80 wire cables have a smaller wire size that is difficult to count by average eyes. They also have blue and gray connectors instead of black. Bends are usually remembered unless very mild.
Note that there are two types of each, regular, and cable select. Each HD must be jumpered according to which type is used. Cable select cables have one wire that is null, and often can be distinguished by a hole in it near one end. It may or may not have the words CS or cable select stenciled on it.
#hwinfo shows ribbon-connect hard-disk as :
Device Files: /dev/sda, /dev/disk/by-id/ata-ST3320620A_9QF7G56W, /dev/disk/by-id/scsi-SATA_ST3320620A_9QF7G56W, /dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:1:0
That would be much too new for optimal use with a 40 wire cable. --
- thank you so much { this will keep me busy for some time!!} best regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Dec 20, 2012 at 1:38 PM, ellanios82
On 12/20/2012 06:20 PM, Felix Miata wrote:
If indeed it is 40 wire, you need to switch it to 80 wire. It doesn't matter if "new" or not, they don't wear out. By now used 80 wire cables should be abundant.
40 wire cables look like http://upload.wikimedia.org/wikipedia/commons/thumb/a/a4/Nappe.svg/550px-Nap... and like MFM/RLL, floppy and 50 pin SCSI cables, with 40 individual wires readily counted by people with normal eyes. Usually their connectors are black, at least on the older ones. Moderate bends in them usually are not remembered.
80 wire cables have a smaller wire size that is difficult to count by average eyes. They also have blue and gray connectors instead of black. Bends are usually remembered unless very mild.
Note that there are two types of each, regular, and cable select. Each HD must be jumpered according to which type is used. Cable select cables have one wire that is null, and often can be distinguished by a hole in it near one end. It may or may not have the words CS or cable select stenciled on it.
#hwinfo shows ribbon-connect hard-disk as :
Device Files: /dev/sda, /dev/disk/by-id/ata-ST3320620A_9QF7G56W, /dev/disk/by-id/scsi-SATA_ST3320620A_9QF7G56W, /dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:1:0
That would be much too new for optimal use with a 40 wire cable. --
__________
- thank you so much { this will keep me busy for some time!!}
best regards
If you have any PC hardware enthusiasts as friends or a friendly repair shop around, they will probably give you a cable for free and you can swap it out easily enough. (It used to be that when you bought a new/replacement PATA drive it came with a 80-pin cable.) I probably have 50 new ones at my office, but shipping is too expensive bother sending you one. fyi: I connect disks to PCs temporarily all the time. Back when that meant connecting/disconnecting the 80-pin cable repeatedly, I would replace them on my lab machines every year or so. They do wear out after enough physical manipulation. Now it's sata cables I have to replace every now and then. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 20/12/12 20:46, Felix Miata wrote:
On 2012-12-20 11:03 (GMT+0200) ellanios82 composed:
/dev/sda4: ERROR: cannot open `/dev/sda4' (No such file or directory)
- my idea was that Linux was proud to be kind to older hardware . . . that After kernel 3.4 it is not possible to boot from a SATA HD while having an internal 40 wire ribbon-cable {i think 40 } PATA HD for back-up is no-longer possible, is, for me, a serious concern.
Such a basic ability to mount a 40-wire PATA 2nd drive would seem important enough to be worth fixing fast.
Finally you told us the cause. Any PATA device a 40 wire cable fits can have an 80 wire replace it, and if it's a HD made in the past 10+ years, should, as the 80 wire cable will not only be your solution, but will allow your PATA device to run at the full speed it is capable of. To continue to use 40 wire will handicap speed, and require a special cmdline parameter to force the maximum speed attempted by the driver down to a fraction of the device's maximum to prevent problems like yours. The UDMA5 spec requires 80 wire. You're lucky if your 3.4 kernel hasn't caused data corruption on your PATA HD while using a 40 wire cable.
For chrissake! What does the size of the cable - 40-wire or 80-wire - have anything to do with the man's problem? In his first post the man wrote: QUOTE kernel-default-3.6.10-15.1.i586 does not allow me to mount /dev/sda kernel 3.4.6-2.10-desktop DOES allow mounting of /dev/sda & sees /dev/sda OK UNQUOTE Note what the second sentence states: "kernel 3.4.6-2.10 DOES allow mounting...". Kernel 3.4.6-2.10 was released on 8 September THIS year - ie, 2012. Nothing to do with having a hard disc drive 10+ years old! Yes, a 40-wire cable will NOT give him the full UDMA for his HDD in question -- but this is NOT about which he is asking the question. And "You're lucky if your 3.4 kernel hasn't caused data corruption on your PATA HD while using a 40 wire cable." is nothing but a furphy. Why should using a 40-wire cable cause corruption? Not the maximum UDMA, but data corruption? (BTW, this kernel problem about configuring for 40-wire cable goes back to at least 2007, and earlier, and it is still doing it - even with SATA-3 setups.) BC -- Using openSUSE 12.2 x86_64 KDE 4.9.4 & kernel 3.6.10-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-12-21 17:29 (GMT+1100) Basil Chupin composed:
What does the size of the cable - 40-wire or 80-wire - have anything to do with the man's problem?
I guess you missed the significance of http://lists.opensuse.org/opensuse-factory/2012-12/msg00411.html It holds the clue that explains why devices /dev/sda* do not get created automatically when running the newer kernel. Kernel response to non-compliance with ATA cabling spec apparently changed after 12.2's 3.4.6 kernel. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/21/2012 2:49 AM, Felix Miata wrote:
On 2012-12-21 17:29 (GMT+1100) Basil Chupin composed:
What does the size of the cable - 40-wire or 80-wire - have anything to do with the man's problem?
I guess you missed the significance of http://lists.opensuse.org/opensuse-factory/2012-12/msg00411.html
It holds the clue that explains why devices /dev/sda* do not get created automatically when running the newer kernel. Kernel response to non-compliance with ATA cabling spec apparently changed after 12.2's 3.4.6 kernel.
Hahaha :) You mean "For chrissake!" it does in fact have exactly everything in the world to do with the man's problem? -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/22/2012 01:30 AM, Brian K. White wrote:
it does in fact have exactly everything in the world to do with the man's problem?
- Thus : [if i understand correctly] Replace 40 wire Ribbon Cable, with 80 wire Ribbon Cable to connect PATA HD . . . and . . . Problem solved !! ................................. best regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* ellanios82
On 12/22/2012 01:30 AM, Brian K. White wrote:
it does in fact have exactly everything in the world to do with the man's problem?
- Thus : [if i understand correctly]
Replace 40 wire Ribbon Cable, with 80 wire Ribbon Cable to connect PATA HD . . . and . . . Problem solved !!
.................................
Is that a question/comment/or is problem *actually* solved? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/22/2012 05:11 PM, Patrick Shanahan wrote:
* ellanios82
[12-22-12 05:29]: On 12/22/2012 01:30 AM, Brian K. White wrote:
it does in fact have exactly everything in the world to do with the man's problem?
- Thus : [if i understand correctly]
Replace 40 wire Ribbon Cable, with 80 wire Ribbon Cable to connect PATA HD . . . and . . . Problem solved !!
................................. Is that a question/comment/or is problem *actually* solved? ........................
- an expression of 'hope' : not yet managed to buy 80 wire ribbon cable. best regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-12-22 12:26 (GMT+0200) ellanios82 composed:
On 12/22/2012 01:30 AM, Brian K. White wrote:
it does in fact have exactly everything in the world to do with the man's problem?
- Thus : [if i understand correctly]
From http://lists.opensuse.org/opensuse-factory/2012-12/msg00430.html I thought it was already clear to you that you need to
Replace 40 wire Ribbon Cable, with 80 wire Ribbon Cable to connect PATA HD
and if that wasn't clear enough, http://lists.opensuse.org/opensuse-factory/2012-12/msg00459.html and its sub-thread certainly should have made it so.
. . . and . . . Problem solved !!
This implies no further need to continue thread, that it has already been fixed by cable replacement. You should cease to post this thread until after an 80 wire cable has already been tried. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/22/2012 06:23 PM, Felix Miata wrote:
Replace 40 wire Ribbon Cable, with 80 wire Ribbon Cable to connect PATA HD
- Thanks to Felix Miata, problem solved : today obtained 80 wire Ribbon Cable to connect PATA HD - now again able to mount and unmount 2nd disk /dev/sda ................... Synopsis : after Kernel 3.4.6-2.10-desktop 40 wire Ribbon Cable is NOT supported ________ - solution : replace with 80 wire Ribbon Cable [plugs remain the same] ................. best regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 21/12/12 18:49, Felix Miata wrote:
On 2012-12-21 17:29 (GMT+1100) Basil Chupin composed:
What does the size of the cable - 40-wire or 80-wire - have anything to do with the man's problem?
I guess you missed the significance of http://lists.opensuse.org/opensuse-factory/2012-12/msg00411.html
It holds the clue that explains why devices /dev/sda* do not get created automatically when running the newer kernel. Kernel response to non-compliance with ATA cabling spec apparently changed after 12.2's 3.4.6 kernel.
So, I had better now go and find an 80-wire cable replacement for my SATA 3 cable now connecting my HDD and which the kernel (3.6.10) has decided is connected with a 40-wire cable and therefore has configured it to operate at UDMA 33 and not its native 133 UDMA. Makes sense I suppose.... BC -- Using openSUSE 12.2 x86_64 KDE 4.10.0 & kernel 3.6.10-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (10)
-
Andrey Borzenkov
-
Basil Chupin
-
Brian K. White
-
Carlos E. R.
-
ellanios82
-
Felix Miata
-
Greg Freemyer
-
Jiri Slaby
-
Patrick Shanahan
-
Rajko