Can't bind ps3daX device to md array

Bug #165198 reported by sandworm on 2007-11-26
4
Affects Status Importance Assigned to Milestone
Ubuntu PS3 Port
Undecided
Unassigned
linux (Ubuntu)
Undecided
Unassigned
Declined for Gutsy by Brian Murray
linux-source-2.6.22 (Ubuntu)
Undecided
Ben Collins
Declined for Gutsy by Brian Murray

Bug Description

Binary package hint: linux-source-2.6.22

In Feisty on PS3 I has a RAID1 array on /dev/sda6 (internal HDD) and /dev/sdf6 (USB HDD).

Trying to update to Gutsy, I installed linux-cell at first. So it binds /dev/sdd6 (USB HDD) to array, but /dev/ps3da6 (internal HDD) was bound in failure state.

Next, I tried to upgrate mdadm. It rebuilds initrd and system goes unbootable, so I can't copypaste a log example now.

description: updated

How many physical drives do you have in your system? (Counting IDE and SATA)

If you have more than 4, you are probably suffering from Bug 157909.

sandworm (launchpad-sandworm) wrote :

This is Sony Playstation 3, not PC !!!! There are no IDE or raw SATA ports.
It has only one physical SATA drive presented as ps3da (not sdX!) and allow to connect USB storage devices.

And this bug is found in ps3disk module which doesn't exist on PC,

description: updated
Brian Murray (brian-murray) wrote :

This bug was nominated for Gutsy but does currently not qualify for a 7.10 stable release update (SRU) and the nomination is therefore declined.
According the the SRU policy, the fix should already be deployed and tested in the current development version before an update to the stable releases will be considered. With 7.10 now released, that policy applies to this bug. See: https://wiki.ubuntu.com/StableReleaseUpdates .
The bug is not being closed as work will continue on fixing it for the next release, Hardy Heron (8.04). If the state of this bug should change such that it qualifies for the SRU process, please contact the person who originally declined it and ask them to re-evaluate it. To help improve the state of this bug see: https://wiki.ubuntu.com/Bugs/HowToTriage .

sandworm (launchpad-sandworm) wrote :

This is a log fragment showing a bug:

Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.532836] md: bind<ps3da6>
Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.644320] ps3disk bad request: dev ps3da: type=7, flags=98
Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.644333]
Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.644335] sector 0, nr/cnr 0/0
Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.644342] bio 0000000000000000, biotail 0000000000000000, buffer 0000000000000000, data 0000000000000000, len 0
Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.644527] ps3disk bad request: dev ps3da: type=7, flags=98
Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.644537]
Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.644540] sector 0, nr/cnr 0/0
Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.644547] bio 0000000000000000, biotail 0000000000000000, buffer 0000000000000000, data 0000000000000000, len 0
Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.644570] md: super_written gets error=-5, uptodate=0
Nov 29 18:53:25 sandworm-ps3-2 kernel: [ 415.644590] ^IOperation continuing on 1 devices

And it had freezed a machine several times and had crashed the filesyestem to unbootable state twice for a week of testing.

Changed in linux-source-2.6.22:
assignee: nobody → ben-collins
status: New → Confirmed

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Dan Munckton (munckfish) wrote :

@sandworm - is this still a problem with Intrepid?

kernel-janitor (kernel-janitor) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Changed in linux (Ubuntu):
status: Incomplete → Invalid
tags: added: kj-expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers