Driver sr needs updating bustype

BTW this is inside qemu-kvm, and could be a qemu issue?! CHAINHASH_SIZE: 8192 memory used by lock dependency info: 4351 k B per task-struct memory footprint: 2688 bytes allocated 5242880 bytes of page_cgroup please try cgroup_disable=memory option if you don't want Checking aperture...

driver sr needs updating bustype-15driver sr needs updating bustype-6driver sr needs updating bustype-63

PQ: 0 ANSI: 5 ata2.00: ATAPI: QEMU DVD-ROM, 0.9.1, max UDMA/100 ata2.00: configured for MWDMA2 scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM 0.9.

PQ: 0 ANSI: 5 Uniform Multi-Platform E-IDE driver udevd version 128 started Driver 'sd' needs updating - please use bus_type methods sd 0:0:0:0: [sda] 8388608 512-byte hardware sectors: (4.29 GB/4.00 Gi B) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:0:0: [sda] 8388608 512-byte hardware sectors: (4.29 GB/4.00 Gi B) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:1:0: [sdb] 8388608 512-byte hardware sectors: (4.29 GB/4.00 Gi B) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00 sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:1:0: [sdb] 8388608 512-byte hardware sectors: (4.29 GB/4.00 Gi B) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00 sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sdb: sdb1 sd 0:0:1:0: [sdb] Attached SCSI disk PM: Starting manual resume from disk kjournald starting.

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange Yes, you can do that, but it can cause an annoying side effect.

Having reserved some slack space it is easy to make a matching partition because you just make the slack space smaller or bigger (and you can always assign the "wasted" space for swap).

Thanks Nikanth Initializing cgroup subsys cpuset Linux version 2.6.29-rc8-9-default ([email protected]) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #88 SMP Mon Mar 23 IST 2009 Command line: root=/dev/disk/by-id/ata-QEMU_HARDDISK_QM00001-part2 resume=/dev/disk/by-id/ata-QEMU_HARDDISK_QM00001-part1 splash=silent vga=0x314 KERNEL supported cpus: Intel Genuine Intel AMD Authentic AMD Centaur Centaur Hauls PAT WC disabled due to known CPU erratum. Using ACPI (MADT) for SMP configuration information SMP: Allowing 16 CPUs, 15 hotplug CPUs nr_irqs_gsi: 24 PM: Registered nosave memory: 000000000009f000 - 00000000000a0000 PM: Registered nosave memory: 00000000000a0000 - 00000000000e8000 PM: Registered nosave memory: 00000000000e8000 - 0000000000100000 Allocating PCI resources starting at 30000000 (gap: 20000000:dffbc000) NR_CPUS:4096 nr_cpumask_bits:16 nr_cpu_ids:16 nr_node_ids:1 PERCPU: Allocating 1908736 bytes of per cpu data kvm-clock: cpu 0, msr cef81, primary cpu clock Built 1 zonelists in Node order, mobility grouping on. Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Mount-cache hash table entries: 256 Initializing cgroup subsys debug Initializing cgroup subsys ns Initializing cgroup subsys cpuacct Initializing cgroup subsys memory Initializing cgroup subsys devices Initializing cgroup subsys freezer CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K CPU 0/0x0 - Node 0 lockdep: fixing up alternatives. Also it would be very nice if CONFIG_FTRACE_STARTUP_TEST can detect this as well. 4654.83 Bogo MIPS (lpj=9309672) Security Framework initialized SELinux: Disabled at boot. Even though it could be a qemu bug, no idea what exactly is failing, so that I could report it to qemu developers. No AGP bridge found Memory: 438260k/524224k available (2862k kernel code, 388k absent, 85576k reserved, 2107k data, 3412k init) Calibrating delay loop (skipped) preset value..Nov 24 dump kernel: [ 49.717165] sd 0:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB) Nov 24 dump kernel: [ 49.717172] sd 0:0:0:0: [sda] Write Protect is off Nov 24 dump kernel: [ 49.717173] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Nov 24 dump kernel: [ 49.717182] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 24 dump kernel: [ 49.717209] sd 0:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB) Nov 24 dump kernel: [ 49.717213] sd 0:0:0:0: [sda] Write Protect is off Nov 24 dump kernel: [ 49.717214] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Nov 24 dump kernel: [ 49.717221] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 24 dump kernel: [ 49.717222] sda: unknown partition table Nov 24 dump kernel: [ 49.724463] sd 0:0:0:0: [sda] Attached SCSI disk Nov 24 dump kernel: [ 49.724504] sd 1:0:0:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) Nov 24 dump kernel: [ 49.724510] sd 1:0:0:0: [sdb] Write Protect is off Nov 24 dump kernel: [ 49.724512] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Nov 24 dump kernel: [ 49.724519] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 24 dump kernel: [ 49.724547] sd 1:0:0:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) Nov 24 dump kernel: [ 49.724551] sd 1:0:0:0: [sdb] Write Protect is off Nov 24 dump kernel: [ 49.724552] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Nov 24 dump kernel: [ 49.724559] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 24 dump kernel: [ 49.724561] sdb: Driver 'sr' needs updating - please use bus_type methods Nov 24 dump kernel: [ 49.734320] unknown partition table Nov 24 dump kernel: [ 50.145507] attempt to access beyond end of device Nov 24 dump kernel: [ 50.145513] sdc: rw=0, want=7018997372, limit=2930277168 Nov 24 dump kernel: [ 50.145515] Buffer I/O error on device sdc3, logical block 4250167552 Nov 24 dump kernel: [ 50.145626] attempt to access beyond end of device Nov 24 dump kernel: [ 50.145627] sdc: rw=0, want=7018997373, limit=2930277168 Nov 24 dump kernel: [ 50.145628] Buffer I/O error on device sdc3, logical block 4250167553 device is used as a RAID member.The next time I boot the machine, it might be a different drive it complains about or none at all.If you for example replace a 2TB disk with another 2TB disk it might not be exactly the same size as the other one.

Tags: , ,