Error audio device is set to a sample rate not supported by soundwire

6 votes and 11 comments so far on Reddit

Create an account to follow your favorite communities and start taking part in conversations.

r/FL_Studio

Posted by4 years ago

Archived

What does this mean? How can i fix it? Please. Help me .

I go to asio panel and in the wdm device list whenever I choose my bluetooth speaker as the output it displays «Warning: The needed sample rate (44100Hz) couldn’t be set or is not suported by the ASIO driver. Please try another sample rate. » but it still applies the change and plays everything in shitty quality and wrong pitch and stuff.

This thread is archived

New comments cannot be posted and votes cannot be cast

level 1

I’ve been having a similar problem using the Scarlett 2i4, only solution I’ve found is to just use FL Studio ASIO instead of the interface’s driver. Kind of defeats the purpose of having an audio interface but oh well.

level 1

Have you tried other sample rates? Maybe 48k?

level 1

You may need to go to the sound settings in control panel (in windows) and make sure that your audio devices are set to use your desired sample rate there. Look under sound -> playback device -> properties -> advanced. My guess is that the WDM device is set to 48k under sound options, which conflicts with the 44k you’re tying to use in FL. There are probably similar troubleshooting steps for a mac.

level 2

Thank you SO much. Changing my sample rate just fixed my problem. I was about to give up until I found your comment.

level 1

Reinstall the ASIO driver? Or try using FL Studio ASIO or vice versa. Does it work when you don’t use ASIO(like using the primary driver or smthn)?

level 2

I go to asio panel and in the wdm device list whenever I choose my bluetooth speaker as the output it displays «Warning: The needed sample rate (44100Hz) couldn’t be set or is not suported by the ASIO driver. Please try another sample rate. » but it still applies the change and plays everything in shitty quality and wrong pitch and stuff.

level 1

guys i got the solution, just turn off the «slim level box …» option and turn on your sound target or whatever you are using (all i just said is you have to do it inside the asio4all panel in fl studio)

About Community

Subreddit Icon

The best FL Studio resource on the internet!



Several Windows users have been reaching us with questions after seeing the “The sample rate for your microphone isn’t supported” error whenever they open the Xbox App and try to create a party. All affected users are reporting that the microphone or the headset works fine with any other application. As it turns out, the issue is not exclusive to a certain Windows version since it’s confirmed to occur on Windows 7, Windows 8.1 and Windows 10.

“The sample rate for your microphone isn’t supported” Error with the Xbox app

What is causing the “sample rate for your microphone isn’t supported” error?

We investigated this particular issue by looking at various user reports and by analyzing several fixes that are commonly recommended by those that managed to resolve the issue successfully. As it turns out, there are several different scenarios with the potential of triggering this issue. Here’s a shortlist with the most common culprits:

  • Common recording device inconsistency – This error can occur due to a common Audio Recording inconsistency that can be caused by two conflicting apps or by a user mistake. In this case, you should deploy the Recording Audio troubleshooter (a built-in utility designed to identify and recommend an appropriate repair strategy).
  • Bad windows update – We haven’t managed to pinpoint the exact update that caused the issue, but during two months, there was a surge of user reports complaining about this issue. Since then, Microsoft has released a hot-fix for the issue that is confirmed to fix the problem. With this in mind, you can resolve the problem by installing every pending update, bringing your Windows version to a newer version than 1803.
  • Dedicated drivers are not compatible with the Windows version – As it turns out, several headsets haven’t yet been optimized for the latest Windows version. So if you use them with the dedicated drivers, chances are you’ll get this error message due to some incompatibility issues. If this scenario is applicable, you will be able to resolve the issue by uninstalling the current driver and reverting towards the generic one.
  • Xbox Live Core service is down – Although this is an unlikely culprit, it’s confirmed that there’s a direct link between this error message and the status of the Xbox Live services. If the core services are down, the party requirements won’t be met and this error will show up. In this case, the only fix is to wait until the services return online.
  • NAT Type is set to Close – Another potential culprit is a NAT Type that is set as closed. The Xbox Companion app might trigger this error because it can’t communicate with the Xbox servers. In this case, you can resolve the issue by repairing the NAT using the Fix it tool included in the Xbox Networking tab.
  • Glitched Xbox App – Another reason that might trigger this error is a glitched Xbox app. Corruption inside the temp folder can fool the Xbox server that the connection is not proper. If this scenario is applicable, you should be able to resolve the issue by resetting the Xbox app altogether, deleting all temporary files.

Method 1: Running the Recording Audio troubleshooter

Before you try more complex repair strategies, you should start this troubleshooting quest by ensuring that your Windows version is not capable of resolving the issue automatically. As it turns out, an incorrect recording configuration can cause the “sample rate for your microphone isn’t supported”.

Under some circumstances, you might be able to fix it simply by running the Recording Audio troubleshooter and letting it recommend a suitable repair strategy. Some users have managed to fix the issue by deploying this troubleshooter and then restarting your computer.

Here’s a quick guide on running the Recording Audio troubleshooter to resolve the “sample rate for your microphone isn’t supported” error:

  1. Open a Run dialog box by pressing Windows key + R. Then, type ‘ms-settings:troubleshoot‘ and press Enter to open up Troubleshooting tab of the Settings app.
    Accessing the Troubleshooting tab
  2. Once you’re inside the Troubleshooting tab, move down to the right-hand menu and click on Recording Audio. Then, click on Run the troubleshooter to start the utility.
    Running the Recording Audio troubleshooter
  3. Wait until the analysis is complete, then click on Apply this fix if a viable repair strategy is recommended.
    Apply this fix
  4. After the fix is enforced, restart your computer and see if the issue is resolved at the next system startup.

If the same issue is still occurring or the Recording Audio troubleshooter didn’t manage to find an issue, move down to the next method below.

Method 2: Update Windows 10 build to the latest

If the first method didn’t allow you to resolve the issue, you should proceed by ensuring that every pending update is installed and you’re using the latest Windows 10 build available for your version. Several affected users that we’re struggling to resolve the same issue have managed to fix it by installing the Feature update version 1803.

This confirms the suspicion that Microsoft has quietly released an unannounced hotfix for the issue. Here’s a quick guide on installing every pending update:

  1. Press Windows key + R to open up a Run dialog box. Next, type “ms-settings:windowsupdate” inside the newly appeared text box and press Enter to open up the Windows Update tab of the Settings app.
    Run dialog: ms-settings:windowsupdate
  2. After you manage to get inside the Windows Update tab, click on Check for Update, then wait for the initial scan to complete.
    Checking for updates on Windows 10
  3. Wait until the initial scan is complete. After the updating utility figures out which updates apply to your computer, follow the on-screen prompts to install them one-by-one.
    Note: In case you’re prompted to restart before you get the chance to install every pending update do so but make sure to return to the same window and continue with the rest of the update installations until your Windows version is up to date.
  4. Once every pending update is installed, restart your computer and see if the issue is resolved once the next startup is complete.

If you’re still seeing the “sample rate for your microphone isn’t supported” error when you open the Xbox app, move down to the next method below.

Method 3: Installing Generic drivers for your Microphone

As it turns out, another common cause that will produce this “sample rate for your microphone isn’t supported” error is an improper microphone driver. Several affected users have managed to resolve this issue by uninstalling the current driver to let Windows install its generic driver.

So far, there have been no reports of this issue occurring while the generic drivers are installed. We have only been able to confirm the effectiveness of this method on Windows 10, but the steps below can be followed on both Windows 7 and Windows 8.1.

Here’s a quick guide on uninstalling the current microphone drivers to allow Windows to install the generic drivers:

  1. Press Windows key + R to open up a Run dialog box. Next, type ” mmsys.cpl” and press Enter to open up the Sound window.
  2. Once you’re inside the Sound window, select the Recording tab and select the Microphone that you’re having issues with. With the recording device selected, click the Properties menu.
  3. After you’re inside the Microphone Properties menu, select the General tab and click on the Properties button under Controller information.
  4. Inside the next setup screen, select the Driver tab from the list horizontal menu and click on Uninstall Device. Then, click on Uninstall again to confirm the uninstallation.
  5. Once the process is complete, restart your computer to allow your operating system to install the generic drivers. You might be prompted to do so automatically
  6. After the next startup sequence is complete, repeat the action that was previously triggering the “sample rate for your microphone isn’t supported” error and see if the issue is now resolved.

Installing the Generic Microphone drivers

If you’re still encountering the same issue, move down to the next method below.

Method 4: Checking your Xbox Live service status

As several users have reported, this particular issue can also occur in instances where one of more critical Xbox Live Core services are down or undergoing maintenance. Although the two doesn’t seem to be related, some users said that the “sample rate for your microphone isn’t supported” error stopped occurring once the Xbox Core services were back online.

You can check if this is the cause of your problem by visiting this page here. If all services have a green check-mark, it means that there is no problem with the core services and you can proceed with the next method below.

Verifying the status of the Xbox live services

If the investigation reveals a problem with the Xbox Live services, wait a couple of hours before checking back if the issue is resolved automatically.

If there are no issues with the Xbox Live services, move down to the next method below.

Method 5: Fixing the NAT type

As it turns out, the inability to create parties can also be related to the fact that your NAT type is Closed. This can produce errors with various multiplayer games and can also interfere with the Xbox App‘s ability to create and maintain parties.

Several affected users that we’re also struggling to resolve this issue finally managed to do so by opening the NAT using the built-in Fix in utility. After doing so and restarting their machine, some said that the “sample rate for your microphone isn’t supported” error was no longer occurring.

Here’s a quick guide on Fixing the NAT type from the Xbox Networking tab:

  1. Press Windows key + R to open up a Run dialog box. Next, type “ms-settings:” and press Enter to open up the Settings app.
    Accessing the Settings app
  2. Once you’re inside the Settings app, scroll down to the bottom o list and click on Gaming.
  3. From the Gaming section, select the Xbox Networking from the vertical menu on the left.
  4. Wait until the NAT analysis is complete. If it reveals that the NAT type is closed, scroll down below and click on Fix it to start the troubleshooter capable of opening it.
    Fixing a Closed NAT Type
  5. Once the process is complete, restart your computer and see if the issue is resolved at the next startup sequence.

Method 6: Resetting the Xbox App

If none of the methods above have allowed you to resolve the issue, chances are you’re dealing with a glitched instance of Xbox Live App or Xbox Companion app. In this case, the fix with the most likelihood of succeeding is to reset the app, forcing it to load all components once again the next time it’s started.

Several affected users have confirmed that the issue was successful for them. If the error is caused by a glitch, there’s a high chance that the sample rate for your microphone isn’t supported” error will be fixed after you do this and restart your computer.

Here’s a quick guide on resetting the Xbox app that is causing the error message:

  1. Press Windows key + R to open up a Run dialog box. Once you’re inside the Run dialog box, type “ms-settings:appsfeatures” and press Enter to open up the Apps & Features screen of the Settings app.
    Accessing the Apps & Features Menu
  2. After you’re inside the Apps & features menu, scroll down through the list of installed UWP applications and locate the Xbox app that is triggering the error message.
  3. Once you see it, click on it once to select it then click on the associated Advanced Options hyperlink.
    Accessing the Advanced Options menu of the Xbox app
  4. Inside the Advanced Options menu, scroll down to the Reset tab and click on Reset to initiate the process.
    Resetting the Xbox app
  5. Click the Reset button at the confirmation prompt to start the process, then wait for it to complete.
  6. Restart your computer and see if the issue is now resolved.

Photo of Kevin Arrows

Kevin Arrows

Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration. Superior record of delivering simultaneous large-scale mission critical projects on time and under budget.

Hello guys, I have installed SoundWire 2.1 64 Bit version on my Arch Linux x86_64 but I have a little problem, when I open the SoundWire Server the program says this: «Audio capture running at 48 kHz», when I open pavucontrol the SoundWire Server is not listed on tab Recording and the program just doesn’t work, don’t play any audio on my phone, but if I’m using the 32 Bit version of Arch Linux when I open the SoundWire Server the program says this: «Audio capture running at 44.1 kHz» and are listed on tab Recording of pavucontrol, and the audio works perfectly. I install both versions of Arch Linux as the same, the only diference is that one is 32 Bit and the other is 64 Bit. So, the problem is with x86_64 version, anyone can help me? Thank you in advance! big_smile

Here is the output when I open SoundWire Server on terminal with Arch Linux x86_64:

[eduardo@chappie ~]$ SoundWireServer 
/usr/bin//win_bitmap.bmp
This server's probable IPv4 address: 192.168.0.102
SoundWire Server v2.1
Initializing server network communication
Portaudio reported default input device sample rate is 48000 (may be incorrect)
Audio stream info: sample rate = 48000, input latency = 0.0213333 sec
Audio input device opened successfully
SoundWireServer: Audio capture running

Last edited by eduardojunio (2015-03-28 03:31:51)

Сказали же уже выше:

на самом деле звуковуха используется как системная и кто-то успел захватить ее раньше (в монопольном режиме)

В этом трабла, при чём тут хр.
Если звуковуха стоит по-умолчанию как системная, она воспроизводит всё что звучит — кино, мп3, вавки, флэш и пр. А они могут быть любой частоты. Ну вот человек включает куб после просмотра очередного выпука прожекторперисхилтон, а он имеет звук 48 килохерц, и звуковая на них так и стоит после просмотра этого весёлого сериала, а куб имеет частоту 44. Куб обязан соединиться со звуковухой при включении — он соединяется и ба!.. Что я вижу мамадарагая — говорит он, — частота-то звуковухи с моим 44-херцовым проектом не совпадает, пиля! Дай-ка я скажу об этом хозяину. Что собсна и делает, после чего пытается переключить звуковуху на 44, но.. поздно, батенька.. :spiteful: Более того, куб заточен под ASIO интерфейс (изобретённый кстати фирмой Steinberg, собсна создавшей кубэйс), и при включении он обязан ещё и в режим ASIO звуковуху перевести с директ-х’овского режима винды, в результате шок получают все — и куб и звуковая и их незадачливый хозяин..:) Поэтому, чтобы не портить себе нервы этой хренью, burken, тебе надо купить вторую звуковуху, или назначить на звук системы (для винды и всех её плееров) встроенную (на мамке которая), а кубэйсу, как точно и красиво сказал Alf_Zetas, — монопольно отдать M-audio. Причём навеки! И чтоб никакая кака даже близко не приближалась к его личной монопольной звуковой карте! :mamba:
Но лучше купить серьёзную карту для куба — и я однозначно могу в этом смысле посоветовать только RME AIO. Она, конечно, дороговатенькая, но лучше ничего нет, причём это конкретно я говорю. А на винду поставить м-аудиву, ибо во-первых и кино с хорошим звуком иногда хочется посмотреть, и в игру поиграть так чтоб волосы дыбом вставали от звука крыльевых пулемётов :) и! — что важно! — иметь возможность, работая в кубэйсе, включить спец-про-прогу типа мелодины стэндэлон, или ресайкли, или самплы, или контакта либо какого-нить другого сэмплера и т.д., имеющих ASIO интерфейс для работы со звуком, и спокойно работать в них обоих параллельно — и в кубе и в этой проге с ASIO (M-audio имеет ASIO а встроенная звуковуха не имеет). Но в любом случае, как бы то ни было, кубэйсу нужно отдать одну из звуковух в единоличное пользование и смириться с этим. Не случайно ведь золотые годы Про Тулса прошли под девизом — «работаю только со своим железом!» :) Ща вот он решил прогнуться под чужие железки ну и где протулс.. :SHABLON_padonak_02: Вот представь, что кубэйс это тот же ПТ и купил ты его в комплекте со звуковой картой. Просто забыл её в магазине почему-то. :) Вперёд! :dance:

  • User avatar
  • tomsavard
  • Posts: 3
  • Offline

I recorded songs on another computer which had the sample rate to my StudioLive at 48kHz. I am now trying to edit them on a different computer using Windows sound drivers. I have set every playback and recording interface that I could find to 48kHz, but I still get this warning.

Songs play fine, so does this warning matter? Is there something else I need to do?

Thanks for your help!

  • User avatar
  • Rangersam
  • Posts: 272
  • Offline

StudioOne will automatically adjust to set your system sample rate, but you really don’t want it to in this case. Personally I would close the project and go to the start page, and check to make sure your interface is set to the sample rate you think it is. Also keep in mind that if at some stage, you have inadvertently saved your project at the different sample rate, say 44.1kHz, that is the sample rate it will try to use.

You may simply need to resave your project set to your desired sample rate (48kHz) and problem solved. I would be using the ‘save as’ feature to make progressive files of your project just in case you have unexpected errors.

You also may have accrued quite a large number of files in the cache folder if you have tried to work at a different sample rate. Although innocuous, you may want to ‘save your project to new folder’ so you can delete all these cache files and free up hard disk. The cache could be several Gbytes by now.


i7 3770,ASUS P8Z68-V-LE RME Multiface x2,RME ADI2,Lucid 2496. Casio PX-3,Yamaha V50,Korg 05,Roland SH-01,Korg Nanopad2,Behringer BCF,BCR2000(studio).
i7 4770, Asus Z87-C, M-Audio delta66,RME ADI2,Vox TonelabLE (spdif input), A&HZED12FX, M-Audio Keystation61ES (home).
Soundworkshop Series30(rackmounted in groups of 8), Dynaudio BM15 speakers.
Win10 64,S1Pro,Soundforge10, CD Arch5,Reason10,Recycle, Waves, Drumcore 3, Korg legacy digital and analogue,
Arturia Vintage Collection, NI Komplete10,Alicia’s Keys,Vintage compressors,Premium tube series.

https://soundcloud.com/andrew-emery

  • User avatar
  • tomsavard
  • Posts: 3
  • Offline

Thank you for the feedback. I see the error on the song page. Here is what I see:
The rate you set 48.0kHz.
The rate the device has: 44.1kHz

I have set all recording and playback rates at 48kHz, but I still get this warning. If I don’t plan to record with this setup, does this warning matter?
Thanks!

  • User avatar
  • Rangersam
  • Posts: 272
  • Offline

tomsavard wroteThank you for the feedback. I see the error on the song page. Here is what I see:
The rate you set 48.0kHz.
The rate the device has: 44.1kHz

I have set all recording and playback rates at 48kHz, but I still get this warning. If I don’t plan to record with this setup, does this warning matter?
Thanks!

Most ASIO sound devices will be able to use 44.1 or 48kHz. Is your audio device able to switch to 48kHz? Maybe that’s your problem.

If you aren’t recording, you won’t create new files at the wrong sample rate, but your project will use the cache to convert all the files to the new rate. Someone else may be able to help you with any complications this may create, because for me, whenever it happens I just fix it. You may have some application running that is clamping the sample rate to 44.1, making impossible for StudioOne to select a new sample rate. StudioOne is able to take care of this mismatch for you, but I cannot say whether it will impact the sound quality, or require more CPU at times.

To preempt what may be causing this, have you gone through and done all the basic tweaks on your PC? I know one of those things is to turn off ‘windows sounds’, you know those annoying little sounds that play whenever windows wants to tell you how good it is?


i7 3770,ASUS P8Z68-V-LE RME Multiface x2,RME ADI2,Lucid 2496. Casio PX-3,Yamaha V50,Korg 05,Roland SH-01,Korg Nanopad2,Behringer BCF,BCR2000(studio).
i7 4770, Asus Z87-C, M-Audio delta66,RME ADI2,Vox TonelabLE (spdif input), A&HZED12FX, M-Audio Keystation61ES (home).
Soundworkshop Series30(rackmounted in groups of 8), Dynaudio BM15 speakers.
Win10 64,S1Pro,Soundforge10, CD Arch5,Reason10,Recycle, Waves, Drumcore 3, Korg legacy digital and analogue,
Arturia Vintage Collection, NI Komplete10,Alicia’s Keys,Vintage compressors,Premium tube series.

https://soundcloud.com/andrew-emery

  • User avatar
  • henrydaniel
  • Posts: 1
  • Offline

On my start up I’m getting a
«failed to open analog connector message
(5- AudioBox USB)!

Then it says
«Please make sure that the rates of your recording and playback devices match.»

Can anyone help me with that

  • User avatar
  • matthewgorman
  • Community Admin & Forum Moderator
  • Posts: 7468
  • Offline

henrydaniel wroteOn my start up I’m getting a
«failed to open analog connector message
(5- AudioBox USB)!

Then it says
«Please make sure that the rates of your recording and playback devices match.»

Can anyone help me with that

I suggest a support ticket. I am not familiar with the first message. There may be more going on than we know.


Matt

Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon
Lenovo Thinkpad E520, Windows 7 64bit, 8 GB RAM, Intel i5 Processor

S1Pro V5

  • User avatar
  • williammonroe1
  • Posts: 2
  • Offline

I was getting the same message. My sound card was at 48 and S1 was at 44.1. Here’s what I did on Windows 10 to correct.
1. Selected Change Sound Card Settings
2. On the «Playback» tab I double-clicked on the output device (Windows sound)
3. On the next popup I went to the Advanced tab
4. This tab has a dropdown where you can change the playback sample rate setting.

This seems to have gotten rid of the message. I hope this helps.

  • User avatar
  • jsljustin
  • Posts: 122
  • Offline

I don’t know, but there seems to be something buggy with all this.

I often will get a messaged saying the sample rates don’t match, when starting a new song / project, and then often when reopening a song that had this error message first time. But the weirdest thing is I get something like:

«Sample rates don’t match. Sample rate set = 0.0KHz…»

Which is bizarre, as I have everything everywhere set to 44.1KHz. I don’t use any other sample rate for anything, ever.

This is just to me a bug that is an annoyance more than anything. I get the pop-up error message from time to time, but it doesn’t interfere with the sample rates in my projects / songs at all.

I think I even raised this as a bug with Studio One support but got no help on it, so I just have to ignore it and carry on.

  • User avatar
  • matthewgorman
  • Community Admin & Forum Moderator
  • Posts: 7468
  • Offline

Just an FYI. If you are on a PC, and you use your interface as the soundcard, turn off Windows event sounds. Those sounds are at 48.0 sample rate, and will change the sample rate of the soundcard when they are played.


Matt

Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon
Lenovo Thinkpad E520, Windows 7 64bit, 8 GB RAM, Intel i5 Processor

S1Pro V5

  • User avatar
  • jsljustin
  • Posts: 122
  • Offline

matthewgorman wroteturn off Windows event sounds.

This is good advice, and is good advice also because we don’t want a windows event triggering a sound right in the middle of recording, or during mixing in our DAW, for example.

I do turn off Windows sounds always, when setting up my PC for DAW use. But I wonder in Windows 10, as you said, the default sound sample rate is 48KHz.. maybe this could be causing problems?

  • User avatar
  • matthewgorman
  • Community Admin & Forum Moderator
  • Posts: 7468
  • Offline

It could be Justin. One of the many little annoying things that can happen. Also watching a movie on the pc would change the sample rate. FWIW, I don’t think its just a Win 10 thing. I have had this happen on 7 also, and it probably goes back further than that.


Matt

Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon
Lenovo Thinkpad E520, Windows 7 64bit, 8 GB RAM, Intel i5 Processor

S1Pro V5

  • User avatar
  • josephlitherland
  • Posts: 5
  • Offline

I get this message too; even on a fresh install of Windows 10. I have my sound interface and the windows sound driver set to 48, but Studio One insists the Windows Sound is at 44.

User avatar

by scottyo7 on
Fri Jul 05, 2019 11:15 am

  • User avatar
  • scottyo7
  • Posts: 2680
  • Offline

See above — have you tried what Ranger Sam said? :roll:

There are a few steps there to methodically go through but after that you should be able to open S1 and be good. ;)


Please add your Signature/Info to your Profile here.
-S1 Pro 5.5.2. Win11 Home 21H2. Behringer UMC404HD. Melodyne Studio 5.2.0.006.
-MSI 12th Gen i7, 16GB, 1GB SSD x2, 7200rpm 2TB HD, NVIDIA RTX 3060.
-EZD3 & EZD2. Scuffham S-Gear 2.97. iZotope Ozone 5.
-Akai MPK249. 6 Guitars. 2 Line 6 POD’s & an E-bow. ;)
-Fluid Audio ‘FX8’ Monitors. Dual 28″ Displays. Rode NT1. SM58. Original Faderport.

-Just Me
-Previous Band: 2GUYZINABASEMENT


Who is online

Users browsing this forum: No registered users and 11 guests

Понравилась статья? Поделить с друзьями:
  • Error attribute name not allowed on element meta at this point
  • Error attempting to extrude with no tool selected
  • Error attempt to read or write outside of partition entering rescue mode
  • Error attempt to read or write outside of disk hd0 entering rescue mode
  • Error attempt to read or write outside of disk cd0