I have been running debian sid for years on a now old laptop without any issue (internal SSD for OS, external for data). The only hard drive issue I got over the years is when I got a M.2 SSD drive from Kingston (a freebie from my workplace). After installation, formatting, etc, everything seemed fine. But after weeks of use, I started to have SSD failures. Once, I opened the laptop cover and checked the thing: the SSD was actually sitting above the wifi chip and the thing was very sweaty and warm. So I concluded that after weeks of being subjected to heat from the wifi chip, something started to fail. I removed the SSD and later tried to check if I could use it in my sonās PC (Win 11). I got a s/w tool to check for any issue with it and yes, some sectors could not be checked and the conclusion was that this Kingston SSD was defective. I had fortunately no important data on it so it went straight to the drive graveyard.
As to the laptop and external SSD, after years of operations, everything is still smooth. Note that this laptop used to run Windows (another freebie from work). When I installed debian originally, I erased the whole thing and started from scratch. I really dislike dual booting.
Thanks man! Well Iāve been in the IT āindustryā since the the early 90sā¦you know, back when a 20MB drive was $400ā¦and never seem to fail! Well Iām sure youāre right. I likely have a bad one but wow the amount of BS, time and stress this thing has caused me is off the charts. This soft of weird random stuff has been happening for many years and itās what makes me want to go with expensive enterprise drivesā¦but yes, even these can and will eventually fail. I had ordered two Samsung EVO 870s, one of the OS and one for the MUSIC drive. I really struggled with spending the money as the HDD I have now have been running well but there is a noticeable lag in comparison between a SSD and HDD. They were suppose to be in yesterday but since Amazon has been doing itās own deliveries the delivery forecast has been far less accurate then it was when UPS/FedEx was doing the deliverersā¦so who knows when it will show up
Thanks for the FSTAB info as I need to change my to reflect the UUID and not the device path.
Yes Keith! I have had some of those Seagate drivesā¦but I have had far more issues with brand new Western Digital HDDsā¦FAR more. In fact I havenāt purchased a WD drive in like 20 years because of that bad run. Like out of 20 of them 12 of them were bad. For my stuff I have found that the Enterprise/server driver were better but nothing seem to outlast the early 90s drivesā¦which by todayās standards are useless IDE, drives that donāt have enough of storage for a folder full of photos!
Thanks bud. Iām working on a big electrical side job and this is why itās been taking me so long to get this problem solved and get back to you guy. No freakinā time. I have a few things regarding the Pipewire/XR-18 that I wanted to ask you. A problem that I fixed with an application I created a few months ago that Iām not sure why Iām having it but noody else seems to have. I thought I would share it with you since we both use the XR-18.
THanks for your input as alway.
You are very luckyā¦or maybe something else is going on thereā¦positive vibes?? Not sure but can I rent out some of that from you!?
Personally my 35 years of experience tells me never to use a laptop for such an important PC. I just wouldnāt do it. (I"M not saying for anyone else but me). Laptop computer are highly proprietary and donāt stick to the ATX, mATX, ITX, BTXā¦or any other standard. They donāt have the flexibility in regards to physical options such as removable caddie drive bays, up-gradable/replaceable CPUs, expansion cards (say to add another set of SATA port) and so much more. Like for the Behringer XR-18 I have two network cards. This keeps my XR-18 Ethernet control system off my network and when I need to have the studio computer go online I just enabled the second NIC card. So for me laptops are out for a permanent studioā¦great for a portable setup but thatās it for me.
The caddie drive bays are used so the MUSIC project drive is hot swappable removable and I try and purchase the smaller options of these drives. I donāt want a 2 to 4 TB drive for anything. Wayyy too much data on a single source. Even if itās being backed up. .The backup and restore times are long and itās a big failure point for lots of irreplaceable data. The other thing is that none of my backups are compressed. Compression is great to save some space (not much actually) but I do it so I can pick and choose a single backup file to replace a bad one. Compression the backup data means a complete decompression before finding the file needed. Iāve actually have had issues in the decompression stage and that alone has cuased my backed up data to inaccessible. So I tend to go with 250GB to 500Gb drives for the music drives and swap them out (storing the full ones) new drives. This keeps the drive use lower on a specific drive too.
This may interest you, bearing in mind these are mostly data-centre drive models.
Cheers,
Keith
Hey Thanks Keith! Yeah this is good stuff.
Thank you!
C
Chris got one of two of my SSD drives so far. The MUSIC Drive (the one that the DAW pulls the data from) has just been installed, formatted to NTFS (so I can still āconvertā the last Cubase project of to Ardour) an transferred/restored the backed up data from the old drive to this new one. I edited Fstab file but this time with the UUID rather than the device path. Worked like a charm!
This make me feel much better using the UUID of the actual drive rather than some discovered device path that can change based on the order it finds the drives or if one drive craps out (like Iāve had) and it messing everything else up.
Thanks for that information bud!
C
Ok guys,
Iām doing a fresh install again. The breakdown so far is I finally got in my new Samsung SSDs. Everything is working well with these new drives.
I installed a fresh install of Ubuntu Studio 26.04 but I would rather have the MATE DM instead of the KDE. So I install the MATE DM and then everything goes to hell. If you recall I had mentioned before that I have ALWAYS had issues upon boot with MATE 24.04LTS on every PC Iāve ever installed it on. Like six personal computers. On every boot I got an error but I never discovered what the error was caused by because the information was near zero that I was given. THis is why I stuck to use 22.04 LTS all this time.
For the studio setup I also was going to use MATE 24.04 with the Ubuntu Studio packaging. But I also was having an issue with the SSD I had so that was for sure compounding the issues lending me to believe I had an issue with the OSā¦well I guess I was but most of the issues was due to the SSD. Now that the SSD have been replaced that issue is over-with.
So I finally get some time to work with the machine, setting up fstab for the drives and begin to get things in working order.
I thought "well since I have a fresh install with a problem free SSD I would simply add my favorite DM of MATE but this time 26.06. The problems started on the first boot. This time however the list of errors was a mile long. One thing after another. At least 60 errors of packages. I was so discussed and donāt really care what the problem isā¦I just donāt want to start things off like this. Iām now wiping this drive again (because I donāt want to have any remnants of MATE) and reinstalling the OS. Clearly there is something going on with MATE from 24.04 to 26.04LTS. I read the other day that it like like MATE might go away due to the lack of active developers.
Iām going to try one last option before I just use Ubuntu Studio with KDE and thatās Ubuntu Cinnamon and add the Ubuntu Studio audio package. Iām not sure whatās going on here but this should be simple and straight forward and itās nothing but a time consuming, no confidence downer when it comes to setting up a pro audio system. Changing out a DM from one to another shouldnāt make or break the system (or my patients!)
Iāll try using Ubuntu Cinnamon with the Ubuntu Studio audio packaging doesnāt work Iāll just stick with Ubuntu Studio but Iām pretty discussed. Just to be safe Iām doing a hardware check/diagnostics on the studio machine first. Currently RAM is being checked but Iām pretty sure itās not a hardware issue. Just thought I would put this out there to you guys in case someone has a thought about all of this.