[atlas] USB drive
- Previous message (by thread): [atlas] [dagstuhl seminar]: global measurements: practice and experience
- Next message (by thread): [atlas] Adding additional probes to existing measurement or exchange them
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Ionescu
mhi at ionescu.de
Fri May 13 12:20:47 CEST 2016
Hi, I need to follow up on this once more... The same probe, which had now been working again for several weeks after it reformatted its drive, I have now found the drive to be read-only. After replacing the drive with a new one, the probe is once again fine. While troubleshooting I have found that the probe does not connect as long as there is no functioning drive present. This makes troubleshooting unnecessarily difficult. I would suggest adding a couple of (SOS?) messages that would run regardless of the presence of a drive, such as: - detected no USB drive on bootup - detected insertion of USB drive - detected removal of USB drive - detected read-only USB drive - Starting fsck on USB drive - Ended fsck on USB drive (possibly indicating success/failure) - Starting to reformat USB drive - Ended reformatting USB drive (possibly indicating success/failure) and possibliy something that would point towards a corrupt FS - if that is easily detectable, for instance by checking the integrity of a known file within the FS. Just my 2ct. Michael On 30.03.2016 13:50, Philip Homburg wrote: > Hi Michael, > [...] > In general, the probe doesn't care what is on the USB stick. So wiping > or formatting the stick is not needed. > > There is at the moment one rare exception. The filesystem can go corrupt > to the point the fsck hangs. > [...] > Philip
- Previous message (by thread): [atlas] [dagstuhl seminar]: global measurements: practice and experience
- Next message (by thread): [atlas] Adding additional probes to existing measurement or exchange them
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]