[opensuse-factory] /dev/sda1 is not a valid block device : not able mount any SDA partition
Hello SuSErs
- i have just tumbleweed installed new Kernel 3.6.0-3-desktop
{ until now, no problems mounting partitions of /dev/sda drive }
......................
my system boots SATA drive HDB
my backup ATA disk was until now. seen by my system as HDA
.......................
command fdisk -l results in output : ____________
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
........................................
my /etc/fstab looks as it was. and has entries :
/dev/sda1 /mnt_cron auto noauto, user 0 0 /dev/sda2 /mnt_cron auto noauto, user 0 0 /dev/sda4 /mnt_cron auto noauto, user 0 0
..................
the Device entries are :
ls -la /dev/sda* brw-rw---- 1 root disk 8, 0 Oct 5 11:59 /dev/sda brw-rw---- 1 root disk 8, 1 Oct 5 12:08 /dev/sda1 brw-rw---- 1 root disk 8, 2 Oct 5 12:08 /dev/sda2 brw-rw---- 1 root disk 8, 3 Oct 5 12:08 /dev/sda3 brw-rw---- 1 root disk 8, 4 Oct 5 12:07 /dev/sda4
.........................................................
all the SDA partitions say "is not a valid block device".
.....................................
Any ideas please how to solve the problem ?
thanks
best regards
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/05/2012 12:38 PM, ellanios82 wrote:
Hello SuSErs
- i have just tumbleweed installed new Kernel 3.6.0-3-desktop
{ until now, no problems mounting partitions of /dev/sda drive }
......................
my system boots SATA drive HDB
my backup ATA disk was until now. seen by my system as HDA
.......................
command fdisk -l results in output : ____________
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
........................................
my /etc/fstab looks as it was. and has entries :
/dev/sda1 /mnt_cron auto noauto, user 0 0 /dev/sda2 /mnt_cron auto noauto, user 0 0 /dev/sda4 /mnt_cron auto noauto, user 0 0
..................
the Device entries are :
ls -la /dev/sda* brw-rw---- 1 root disk 8, 0 Oct 5 11:59 /dev/sda brw-rw---- 1 root disk 8, 1 Oct 5 12:08 /dev/sda1 brw-rw---- 1 root disk 8, 2 Oct 5 12:08 /dev/sda2 brw-rw---- 1 root disk 8, 3 Oct 5 12:08 /dev/sda3 brw-rw---- 1 root disk 8, 4 Oct 5 12:07 /dev/sda4
.........................................................
all the SDA partitions say "is not a valid block device".
.....................................
Any ideas please how to solve the problem ?
Hmm, you should avoid using /dev/sdXX in /etc/fstab. The order of disks initialization was never guaranteed. Use some of /dev/disk/by-*.
But that should not be the issue as you have the first partition on all disks. So what is exactly in the output of dmesg when you do that inside the failed boot's rescue console from the initrd?
- -- js suse labs
On 10/05/2012 01:54 PM, Jiri Slaby wrote:
So what is exactly in the output of dmesg when you do that inside the failed boot's rescue console from the initrd?
Dear JS - thank you
my system boots OK from sata disk SDB
my system cannot use SDA ata disk for backup
please excuse me as i am not experienced enough to understand what dmesg you ask me to provide, thus . . . attached is dmesg.txt
................
best regards
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/05/2012 01:16 PM, ellanios82 wrote:
On 10/05/2012 01:54 PM, Jiri Slaby wrote:
So what is exactly in the output of dmesg when you do that inside the failed boot's rescue console from the initrd?
Dear JS - thank you
my system boots OK from sata disk SDB
my system cannot use SDA ata disk for backup
Do you mean pata? As sata is ata too... Do you still have the working kernel? Can you compare listings of lsinitrd /boot/initrd-XXX where XXX are the two kernels (working, non-working).
please excuse me as i am not experienced enough to understand what dmesg you ask me to provide,
Try to boot with sdb and when it comes to the rescue console, issue dmesg. It will output kernel messages on the standard output. Just grab a photo of that or something...
regards, - -- js suse labs
On 10/05/2012 01:16 PM, ellanios82 wrote:
[ 0.613814] ata_piix 0000:00:1f.1: version 2.13 [ 0.613854] ata_piix 0000:00:1f.1: setting latency timer to 64 [ 0.614149] scsi0 : ata_piix [ 0.614890] scsi1 : ata_piix [ 0.615418] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14 [ 0.615420] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15 [ 0.615442] ata_piix 0000:00:1f.2: MAP [ [ 0.615443] P0 P2 P1 P3 ] [ 0.615473] ata_piix 0000:00:1f.2: setting latency timer to 64 [ 0.615722] scsi2 : ata_piix [ 0.616419] scsi3 : ata_piix [ 0.617042] ata3: SATA max UDMA/133 cmd 0xd080 ctl 0xd000 bmdma 0xc800 irq 19 [ 0.617044] ata4: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc808 irq 19 [ 0.790088] ata3.01: ATA-8: WDC WD10EAVS-00M4B0, 01.00A01, max UDMA/133 [ 0.790092] ata3.01: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 0.792176] ata4.01: ATAPI: Optiarc DVD RW AD-5260S, 1.00, max UDMA/100 [ 0.796515] ata3.01: configured for UDMA/133 [ 0.798177] ata4.01: configured for UDMA/100 [ 0.830009] ata1.01: ATA-7: ST3320620A, 3.AAF, max UDMA/100 [ 0.830012] ata1.01: 625142448 sectors, multi 16: LBA48 [ 0.830016] ata1.01: limited to UDMA/33 due to 40-wire cable [ 0.862014] usb 1-1: new high-speed USB device number 2 using ehci_hcd [ 0.904921] ata1.01: configured for UDMA/33 [ 0.905053] scsi 0:0:1:0: Direct-Access ATA ST3320620A 3.AA PQ: 0 ANSI: 5 [ 0.905244] sd 0:0:1:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB) [ 0.905279] sd 0:0:1:0: [sda] Write Protect is off [ 0.905281] sd 0:0:1:0: [sda] Mode Sense: 00 3a 00 00 [ 0.905296] sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 0.905422] scsi 2:0:1:0: Direct-Access ATA WDC WD10EAVS-00M 01.0 PQ: 0 ANSI: 5 [ 0.905589] sd 2:0:1:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 0.905626] sd 2:0:1:0: [sdb] Write Protect is off [ 0.905629] sd 2:0:1:0: [sdb] Mode Sense: 00 3a 00 00 [ 0.905645] sd 2:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 0.905332] ACPI: Invalid Power Resource to register! [ 0.905688] ACPI: Invalid Power Resource to register!<5>[ 0.906959] scsi 3:0:1:0: CD-ROM Optiarc DVD RW AD-5260S 1.00 PQ: 0 ANSI: 5 [ 0.934708] sdb: sdb1 sdb2 sdb3 sdb4 [ 0.935041] sd 2:0:1:0: [sdb] Attached SCSI disk [ 0.996362] usb 1-1: New USB device found, idVendor=152e, idProduct=2507 [ 0.996365] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 0.996368] usb 1-1: Product: Super Multi Rewriter [ 0.996371] usb 1-1: Manufacturer: HLDS Inc. [ 0.996373] usb 1-1: SerialNumber: P01071013185543 [ 1.410022] usb 4-1: new low-speed USB device number 2 using uhci_hcd [ 1.416014] tsc: Refined TSC clocksource calibration: 2666.363 MHz [ 1.416018] Switching to clocksource tsc [ 1.551813] usb 4-1: New USB device found, idVendor=04b4, idProduct=0033 [ 1.551816] usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.569285] input: HID 04b4:0033 as /devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/input/input1 [ 1.569359] hid-generic 0003:04B4:0033.0001: input,hidraw0: USB HID v1.00 Mouse [HID 04b4:0033] on usb-0000:00:1d.2-1/input0 [ 1.844645] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [ 1.844784] ata1.01: BMDMA stat 0x44 [ 1.844858] ata1.01: failed command: READ DMA [ 1.844942] ata1.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 dma 4096 in [ 1.844942] res 51/84:00:00:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error) [ 1.845230] ata1.01: status: { DRDY ERR } [ 1.845305] ata1.01: error: { ICRC ABRT } [ 1.845403] ata1: soft resetting link [ 2.128603] ata1.01: configured for UDMA/33 [ 2.128610] sd 0:0:1:0: [sda] [ 2.128612] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 2.128614] sd 0:0:1:0: [sda] [ 0.907216] ACPI: Invalid Power Resource to register! [ 2.128616] Sense Key : Aborted Command [current] [descriptor] [ 2.128619] Descriptor sense data with sense descriptors (in hex): [ 2.128621] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 2.128631] 00 00 00 00 [ 2.128635] sd 0:0:1:0: [sda] [ 2.128638] Add. Sense: Scsi parity error [ 2.128641] sd 0:0:1:0: [sda] CDB: [ 2.128642] Read(10): 28 00 00 00 00 00 00 00 08 00 [ 2.128651] end_request: I/O error, dev sda, sector 0 [ 2.128763] Buffer I/O error on device sda, logical block 0 [ 2.128874] ata1: EH complete [ 3.068332] ata1.01: limiting speed to UDMA/25:PIO4 [ 3.068335] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [ 3.068471] ata1.01: BMDMA stat 0x44 [ 3.068546] ata1.01: failed command: READ DMA [ 3.068629] ata1.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 dma 4096 in [ 3.068629] res 51/84:00:00:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error) [ 3.068904] ata1.01: status: { DRDY ERR } [ 3.068979] ata1.01: error: { ICRC ABRT } [ 3.069083] ata1: soft resetting link [ 3.352292] ata1.01: configured for UDMA/25 [ 3.352298] sd 0:0:1:0: [sda] [ 3.352300] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 3.352302] sd 0:0:1:0: [sda] [ 3.352303] Sense Key : Aborted Command [current] [descriptor] [ 3.352306] Descriptor sense data with sense descriptors (in hex): [ 3.352308] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 3.352317] 00 00 00 00 [ 3.352322] sd 0:0:1:0: [sda] [ 3.352324] Add. Sense: Scsi parity error [ 3.352327] sd 0:0:1:0: [sda] CDB: [ 3.352328] Read(10): 28 00 00 00 00 00 00 00 08 00 [ 3.352336] end_request: I/O error, dev sda, sector 0 [ 3.352448] Buffer I/O error on device sda, logical block 0 [ 3.352555] ata1: EH complete [ 3.400372] ldm_validate_partition_table(): Disk read failed. [ 3.400764] sda: unable to read partition table [ 3.400969] sd 0:0:1:0: [sda] Attached SCSI disk
Ah, I see the error there. Does it happen with kernel-vanilla?
On 10/05/2012 02:45 PM, Jiri Slaby wrote:
On 10/05/2012 01:16 PM, ellanios82 wrote:
[ 0.613814] ata_piix 0000:00:1f.1: version 2.13 [ 0.613854] ata_piix 0000:00:1f.1: setting latency timer to 64 [ 0.614149] scsi0 : ata_piix [ 0.614890] scsi1 : ata_piix [ 0.615418] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14 [ 0.615420] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15 [ 0.615442] ata_piix 0000:00:1f.2: MAP [ [ 0.615443] P0 P2 P1 P3 ] [ 0.615473] ata_piix 0000:00:1f.2: setting latency timer to 64 [ 0.615722] scsi2 : ata_piix [ 0.616419] scsi3 : ata_piix [ 0.617042] ata3: SATA max UDMA/133 cmd 0xd080 ctl 0xd000 bmdma 0xc800 irq 19 [ 0.617044] ata4: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc808 irq 19 [ 0.790088] ata3.01: ATA-8: WDC WD10EAVS-00M4B0, 01.00A01, max UDMA/133 [ 0.790092] ata3.01: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 0.792176] ata4.01: ATAPI: Optiarc DVD RW AD-5260S, 1.00, max UDMA/100 [ 0.796515] ata3.01: configured for UDMA/133 [ 0.798177] ata4.01: configured for UDMA/100 [ 0.830009] ata1.01: ATA-7: ST3320620A, 3.AAF, max UDMA/100 [ 0.830012] ata1.01: 625142448 sectors, multi 16: LBA48 [ 0.830016] ata1.01: limited to UDMA/33 due to 40-wire cable [ 0.862014] usb 1-1: new high-speed USB device number 2 using ehci_hcd [ 0.904921] ata1.01: configured for UDMA/33 [ 0.905053] scsi 0:0:1:0: Direct-Access ATA ST3320620A 3.AA PQ: 0 ANSI: 5 [ 0.905244] sd 0:0:1:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB) [ 0.905279] sd 0:0:1:0: [sda] Write Protect is off [ 0.905281] sd 0:0:1:0: [sda] Mode Sense: 00 3a 00 00 [ 0.905296] sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 0.905422] scsi 2:0:1:0: Direct-Access ATA WDC WD10EAVS-00M 01.0 PQ: 0 ANSI: 5 [ 0.905589] sd 2:0:1:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 0.905626] sd 2:0:1:0: [sdb] Write Protect is off [ 0.905629] sd 2:0:1:0: [sdb] Mode Sense: 00 3a 00 00 [ 0.905645] sd 2:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 0.905332] ACPI: Invalid Power Resource to register! [ 0.905688] ACPI: Invalid Power Resource to register!<5>[ 0.906959] scsi 3:0:1:0: CD-ROM Optiarc DVD RW AD-5260S 1.00 PQ: 0 ANSI: 5 [ 0.934708] sdb: sdb1 sdb2 sdb3 sdb4 [ 0.935041] sd 2:0:1:0: [sdb] Attached SCSI disk [ 0.996362] usb 1-1: New USB device found, idVendor=152e, idProduct=2507 [ 0.996365] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 0.996368] usb 1-1: Product: Super Multi Rewriter [ 0.996371] usb 1-1: Manufacturer: HLDS Inc. [ 0.996373] usb 1-1: SerialNumber: P01071013185543 [ 1.410022] usb 4-1: new low-speed USB device number 2 using uhci_hcd [ 1.416014] tsc: Refined TSC clocksource calibration: 2666.363 MHz [ 1.416018] Switching to clocksource tsc [ 1.551813] usb 4-1: New USB device found, idVendor=04b4, idProduct=0033 [ 1.551816] usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.569285] input: HID 04b4:0033 as /devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/input/input1 [ 1.569359] hid-generic 0003:04B4:0033.0001: input,hidraw0: USB HID v1.00 Mouse [HID 04b4:0033] on usb-0000:00:1d.2-1/input0 [ 1.844645] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [ 1.844784] ata1.01: BMDMA stat 0x44 [ 1.844858] ata1.01: failed command: READ DMA [ 1.844942] ata1.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 dma 4096 in [ 1.844942] res 51/84:00:00:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error) [ 1.845230] ata1.01: status: { DRDY ERR } [ 1.845305] ata1.01: error: { ICRC ABRT } [ 1.845403] ata1: soft resetting link [ 2.128603] ata1.01: configured for UDMA/33 [ 2.128610] sd 0:0:1:0: [sda] [ 2.128612] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 2.128614] sd 0:0:1:0: [sda] [ 0.907216] ACPI: Invalid Power Resource to register! [ 2.128616] Sense Key : Aborted Command [current] [descriptor] [ 2.128619] Descriptor sense data with sense descriptors (in hex): [ 2.128621] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 2.128631] 00 00 00 00 [ 2.128635] sd 0:0:1:0: [sda] [ 2.128638] Add. Sense: Scsi parity error [ 2.128641] sd 0:0:1:0: [sda] CDB: [ 2.128642] Read(10): 28 00 00 00 00 00 00 00 08 00 [ 2.128651] end_request: I/O error, dev sda, sector 0 [ 2.128763] Buffer I/O error on device sda, logical block 0 [ 2.128874] ata1: EH complete [ 3.068332] ata1.01: limiting speed to UDMA/25:PIO4 [ 3.068335] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [ 3.068471] ata1.01: BMDMA stat 0x44 [ 3.068546] ata1.01: failed command: READ DMA [ 3.068629] ata1.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 dma 4096 in [ 3.068629] res 51/84:00:00:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error) [ 3.068904] ata1.01: status: { DRDY ERR } [ 3.068979] ata1.01: error: { ICRC ABRT } [ 3.069083] ata1: soft resetting link [ 3.352292] ata1.01: configured for UDMA/25 [ 3.352298] sd 0:0:1:0: [sda] [ 3.352300] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 3.352302] sd 0:0:1:0: [sda] [ 3.352303] Sense Key : Aborted Command [current] [descriptor] [ 3.352306] Descriptor sense data with sense descriptors (in hex): [ 3.352308] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 3.352317] 00 00 00 00 [ 3.352322] sd 0:0:1:0: [sda] [ 3.352324] Add. Sense: Scsi parity error [ 3.352327] sd 0:0:1:0: [sda] CDB: [ 3.352328] Read(10): 28 00 00 00 00 00 00 00 08 00 [ 3.352336] end_request: I/O error, dev sda, sector 0 [ 3.352448] Buffer I/O error on device sda, logical block 0 [ 3.352555] ata1: EH complete [ 3.400372] ldm_validate_partition_table(): Disk read failed. [ 3.400764] sda: unable to read partition table [ 3.400969] sd 0:0:1:0: [sda] Attached SCSI disk
Ah, I see the error there. Does it happen with kernel-vanilla?
_____________________
Hello Jiri
- this is all very advanced for me . . . I do not have :
kernel-vanilla . . . i only have kernel that Tumbleweed installed last night.
...........
thank you
best regards
On 10/05/2012 02:45 PM, Jiri Slaby wrote:
Ah, I see the error there. Does it happen with kernel-vanilla?
_______________
Hello Jiri
i have installed now :
kernel-vanilla using YAST :
3.6.0-3-vanilla #1 SMP
.............
Still cannot mount any partition of /dev/sda :
# mount -t ext4 /dev/sda1 /mnt mount: special device /dev/sda1 does not exist
............
however : _______
# fdisk -l /dev/sda
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
............
thus, because fdisk can see disk SDA all right . . . is this a Kernel Issue ??
..............
thank you
best regards
On 10/05/2012 05:20 PM, ellanios82 wrote:
On 10/05/2012 02:45 PM, Jiri Slaby wrote:
Ah, I see the error there. Does it happen with kernel-vanilla?
Hello Jiri
- am now having extreme difficulty to boot my system :
When i Boot, my System freezes : last message is :
"fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic drive" . . . after which system freezes
......................... - Am booting from disk SDB ______________________
on command :
#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
- thus system sees my sda partitions
BUT
command # ls -la /dev/sd* brw-rw---- 1 root disk 8, 0 Oct 5 22:15 /dev/sda brw-rw---- 1 root disk 8, 16 Oct 5 22:15 /dev/sdb brw-rw---- 1 root disk 8, 17 Oct 5 22:15 /dev/sdb1 brw-rw---- 1 root disk 8, 18 Oct 5 22:15 /dev/sdb2 brw-rw---- 1 root disk 8, 19 Oct 5 22:15 /dev/sdb3 brw-rw---- 1 root disk 8, 20 Oct 5 22:15 /dev/sdb4
- this shows that : presumably booting has DELETED my devices sda1 sda2 sda3 sda4
..................................
Attached is most recent DMESG as .txt file
......................
Any suggestions please how these troubles may be fixed ??
Thank you
best regards
On 10/05/2012 09:40 PM, ellanios82 wrote:
On 10/05/2012 05:20 PM, ellanios82 wrote:
On 10/05/2012 02:45 PM, Jiri Slaby wrote:
Ah, I see the error there. Does it happen with kernel-vanilla?
Hello Jiri
- am now having extreme difficulty to boot my system :
When i Boot, my System freezes : last message is :
"fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic drive" . . . after which system freezes
This is from sda? ^^^^^^^^^^^^
- Am booting from disk SDB
on command :
#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
- thus system sees my sda partitions
BUT
command # ls -la /dev/sd* brw-rw---- 1 root disk 8, 0 Oct 5 22:15 /dev/sda brw-rw---- 1 root disk 8, 16 Oct 5 22:15 /dev/sdb brw-rw---- 1 root disk 8, 17 Oct 5 22:15 /dev/sdb1 brw-rw---- 1 root disk 8, 18 Oct 5 22:15 /dev/sdb2 brw-rw---- 1 root disk 8, 19 Oct 5 22:15 /dev/sdb3 brw-rw---- 1 root disk 8, 20 Oct 5 22:15 /dev/sdb4
- this shows that : presumably booting has DELETED my devices sda1 sda2
sda3 sda4
No, the kernel did not. According to the logs it cannot read from the disk anything initially. If you can read from the disk later by fdisk, try running `partprobe'. Then the kernel should re-read the partition table and it should work.
Any suggestions please how these troubles may be fixed ??
For the time being, just downgrade the kernel back to 12.2, i.e. to 3.4.
regards,
On 10/05/2012 10:57 PM, Jiri Slaby wrote:
Any suggestions please how these troubles may be fixed ??
For the time being, just downgrade the kernel back to 12.2, i.e. to 3.4.
______________
Thank you, Jiri
How to downgrade?? . . . do i need to install PREVIOUS Modules and Libraries , in addition to Kernel 3.4. ??
thank you
best wishes
On 10/05/2012 10:20 PM, ellanios82 wrote:
On 10/05/2012 10:57 PM, Jiri Slaby wrote:
Any suggestions please how these troubles may be fixed ??
For the time being, just downgrade the kernel back to 12.2, i.e. to 3.4.
Thank you, Jiri
How to downgrade?? . . . do i need to install PREVIOUS Modules and Libraries , in addition to Kernel 3.4. ??
No, you can switch kernels without changing tools. In fact you can have two kernels side-by-side. E.g. by doing this: rpm -ivh http://download.opensuse.org/repositories/Kernel:/openSUSE-12.2/standard/x86...
Or you may uncomment "multiversion = provides:multiversion(kernel)" in /etc/zypp/zypp.conf and then choose in yast to install another kernel.
Or if you want only the older kernel, go to yast, sw mgmt, search kernel-desktop and in the "versions" tab choose the appropriate version...
-
ellanios82 -
Jiri Slaby