Hi, Which information exactly do you need? I can provide you any information you may require if you explain me how to gather it (I'm not as good as most of you). Regarding testing. I don't want to use testing in this computer as it has some sensitive data. Regarding non mounting at boot it is rather not a good option. First, I like my disks to be check up periodically, this is fairly well done at boot. Second, This is a file server besides a desktop, so not always kde/gnome... are in use. I really think it is redundant to have to use another tool than fstab to mount disks only for the seek of speeding up the boot process. I really don't see the point of speeding the things up if they make everything else unstable. I honestly think that we are trying to build a house starting from the roof. First stability and then if possible speed. Hector On 6 June 2011 13:13, Tom Gundersen <teg@xxxxxxx> wrote: > On Mon, Jun 6, 2011 at 10:37 AM, Hector Martinez-Seara <hseara@xxxxxxxxx> wrote: >> t 4 days I've been again experiencing problems with my usb >> disks at boot. Right now it is not as bad as before, it fails around >> 75% of the boots which is still unacceptable. The problem was totally >> solved with udev-168-2. But at some point, currently udev-171-1, the >> problem was back. Sorry I can not be more precise as I don't boot the >> system every day. Has been any changes again in this respect? > > We have been speeding up boot with the recent udev releases, so any > race conditions will be more pronounced than before. There might of > course be a bug in udev which is not just a race, but then I would > need more info (like which exact version breaks for you, and maybe > have a try with [testing], as there is lots of news stuff there). > > As I said before: > > "That said, there is a fundamental problem with usb drives, so we > cannot reliably mount them at boot (it probably will work in practice > though). The problem is that there is no way to know when all usb > devices have been enumerated (even if the drivers are loaded), so we > don't know how long to wait before trying to mount them. > > This is the kind of problems solved by systemd (in community), and it > is out of scope for the standard sysvinit initscripts (unless there is > a solution that I am not aware of)." > > Another option, if usb is not actually needed for booting (as in your > case) is to have some software do automounting when the device appears > (KDE/GNOME can do this, I'm sure there are others too, but I'm not too > familiar with it). > > HTH, > > Tom > -- Hector Martínez-Seara Monné mail: hseara@xxxxxxxxx Tel: +34656271145 Tel: +358442709253
